DOCS

Okay so, the docs.

One tab per thing. The app, how a dimension gets generated, the .chaos file byte by byte, how a roll works and why you can't cheat it, your own 3D stuff as .cheng, the registry, the wallpaper, where the files are, the commands. Plain talk plus the actual code that does each part, just the chunk, not the whole file. The design map and the flow doc are here too, as they are. If the words and the code disagree the code is right and I fix the words.

the app	Install it, the 4 steps, the tabs, the keys.
generation	256 bits in, a whole dimension out. Streams, the tier roll, what each tier unlocks, the order stuff rolls in.
.chaos	The 512 bytes. Layout, states, the 3 hashes, what verify actually checks.
the roll	Commit, ticket, seed, claim. App side and registry side. One a week.
.cheng	Your own model on the stage: import, clean, cut down, pack, draw.
the registry	The pages, how value is computed, the odds, what gets stored, what gets refused.
the wallpaper	The KDE plugin: what plays, the lobby, the pauses, the log.
files and settings	Where everything lives on your PC.
command line	Every flag.
design map	The why and the status, the file I keep next to the code.
data and logic flow	How each thing is done and who trusts what.

The short version

Chaos rolls a 3D dimension from a seed. 256 bits go in, out comes one shape with its skin, palette, satellites, debris, rings, particles and a backdrop. Same seed = same dimension on any PC. A preview roll is free, renders, you can keep it, it's worth nothing. A claimable roll needs a ticket from the registry (one a week per account) and once you claim it the seed is yours, sits in your vault with a value, you can list it, people can acquire it. The registry keeps the books and the only private key. The app renders and holds your files. The file itself is basically a receipt.