What is a FallKard card?

A normal PNG that openly carries a real single-file build in two declared PNG text chunks, with a manifest and a sha256 seal. It renders as a picture anywhere; the Forge reads it back, verifies the seal and, only if you click, hatches the build in a sandbox. Nothing is hidden in the pixels.

What happens if a platform strips the card or turns it into a JPEG?

Every card prints the first 80 bits of its seal on its face as a 16-symbol code. The reader reads that code off the pixels, or you type it, and finds the card in your deck: the cards this device already holds. The build then comes from your deck and must match the full seal. A read that could be two cards is refused, never guessed.

What did the creatures of kard-evolve ship into the card format?

Read rule 0.2: a U is read as the V it was. A vision model reading small copies of cards saw V as U, a letter no code uses, so those reads were refused. Creatures evolving code-reading rules in kard-evolve found the fold from those misreads with nothing telling them to look. Sealed before it was measured, it held 5 of 5 rules: at 35% size the model's reads went from 57 to 64 of 64 right cards, with 0 wrong across 960 reads.

Fall World · the Forge

The card that IS the software

Put a working build inside a picture. It stays a picture — you can post it, save it, send it — and anyone who has it can open it and get the build back out.

Forge one

Type anything below. It gets compressed, sealed with a hash, and tucked inside a real PNG.

the build — any text, or paste a whole HTML file

Read one back

Drop the card you just downloaded — or any picture — and see what it is really carrying. Even a copy a platform stripped, or turned into a JPEG: if the card is in your deck, its printed seal finds it.

Drop a card or any picture here, or click to choose one

or type the code printed on the card — for a copy too small or blurred to read from its pixels

Your deck on this device is empty.

Fold one · forgeupgrade

A second cargo for the same forge. A structure is encoded as an origami crease pattern: a crown pole radiating out to a golden-angle ring of fold-points that the ground pole gathers in, twisting at κ = 0.618 as it collapses — and the center stays a hole the whole way, because a twist fold has no apex. Drag it between flat (possibility, creases latent) and folded (actual, collapsed). The fold motion is the teaching; the tier is earned from whether the pattern actually closes.

fold · t

fold-points

crown (transmits)

ground (weaves)

Build one · the studio

Not a cloud IDE — its sovereign opposite: you own the workshop and keep the outputs. Compose a build from estate organs, or have a model write one with your own key; test it live in a sealed frame; then mint it as a sovereign artifact — the card CONTAINS the working build, its tier is EARNED, and its lineage is Ed25519-signed and verifiable from the file alone. The bound, stated plainly: web-native, single-file, local-first builds only.

name it

have a model write it (your key, this browser, nowhere else)

The baby KCC · shared standard, sovereign state

This estate runs its own KCC ledger: the standard is KCC-MINT-001 (the same DNA as main KCC — same schema, same primes, same 510510); the state is its own, on this machine, loopback-first. Every mint above enters it. It bridges to main KCC by recognition, not merge — the R7 rule: same standard means they can talk, distinct state means they stay two things. Internal value and provenance only — the day this touches real money it is a separate, counselled build.

The seal you can read

Post a card and the platform may strip its build out, or turn it into a JPEG. The picture survives. So every card now prints the first 80 bits of its seal on its face, in a band anyone can read.

Two people holding the same card is what makes a stripped copy whole. The copy keeps the printed seal; whoever holds the card keeps the build. Drop the stripped copy here, the page reads the band off the pixels, finds the card in your deck, and re-checks the build against its full seal. The picture only says which card it is. What comes out is always your own copy, verified.

Made to be read back exactly. A sealed test had a vision model read 64 rendered texts blind (kar-pixel-cost). Every miss was one character, never a word: O read as 0, C as c, a curly quote straightened, an extra digit in a hex run, a long run miscounted. So the band uses Crockford base32, which has no I, L, O or U and is read case-blind. It prints in groups of four, so there are no long runs. Its blocky 5×7 letters all differ from each other in at least five dots. A read is matched to your deck by edit distance: a slip is corrected, and a read that could be two cards is refused, never guessed.

Nothing is hidden. The band is printed in plain sight, like a serial number, and carries only the seal. The build still rides in the named chunks, and the picture's own data is never used to smuggle anything.

Why it cannot be faked

The seal is a hash of the compressed build. Change one byte of what is inside and the seal stops matching, and this page tells you so. Nobody has to be trusted — the check is re-run in front of you, on your own machine.

It is still a real PNG. The build rides in the text chunks every PNG is allowed to carry, so a picture viewer shows a picture and ignores the rest. Nothing is hidden or smuggled — the chunks are named, and the whole point is that anybody can look.

Nothing leaves your browser. Compressing, hashing and reading all happen here. There is no server to send it to.

The fold teaches the structure, not its truth. A crease pattern that closes earns its tier by geometry — the medium physically cannot draw an apex at the center. Whether the structure folded into it is TRUE is a separate question the card never claims to settle.