One pack format. Every tool reads it the same.
DATA is the shop's entity ledger: define a schema, author in a real editor, validate every reference, then codegen TypeScript and C# from one source. The goblin your web tool sees is the goblin Unity sees.
“Nothing broken gets sealed. Nothing unsealed gets through. That ref would have broken your build at 2 a.m. — it didn't.” Cari
01 · The problem
Every tool needs to know what a goblin is. Left alone, every tool invents its own. Twelve tools, twelve goblins, and a month later nobody knows which one is real.
→ · The answer
One self-describing pack, sealed only after every reference checks, handed to each tool in its own language. The same goblin, guaranteed, on every side of the wall.
02 · What it does
One pack format every tool reads the same way — checked before it ships.
One pack format for the whole wall
Guildcraft, JAM, ASSET, NODE all read the same self-describing pack. No parallel JSON piles.
Validate before ship
Structural and referential checks; a broken ref fails at the bench, not in the build.
Same data, your language
Codegen TypeScript and C# from one validated source; Unity picks it up as a package.
A real editor, not a spreadsheet
Schema-driven form + JSON on a locked local port; the schema tells you what may go in.
Versions you can point at
Sisters fetch a known revision instead of inventing storage.
Behind the gate
The hosted surface opens with your GATE session. Same key as everything.
03 · How it connects
Where DATAforge sits on the wall.
Every tool draws heat and session through GATE and hangs on the Hall. These are its hand-offs.
04 · Tended by
Cari
Cari carries the packs across the wall, and nothing broken gets in one.
Cari carries — sealed cases between the shores of the wall, every one checked before the lid closes. The quiet post you notice only on the day it saves you.
Her rule: Nothing broken gets sealed. Nothing unsealed gets through.
05 · Roadmap
Where DATAforge goes from here.
- 01
Wired by NODE
Validate, publish, fetch as graph steps so packs move without a human copying files.
- 02
Entities from the board
WIKI's entities become sealed packs; ASSET's identities read them; ANVIL's slices load them.
- 03
WIKI entities → packs
- 04
ASSET identities read packs
- 05
Hall health/stats on shared state
- 06
NODE DataPack.Validate / Publish / Fetch edges
06 · Get started
One pack format. Every tool reads it the same.
You get a sealed pack your Unity project and your web tool agree on. One Gate sign-in opens it and every other tool on the wall.