~1 min read
Engineering ledgers·
These files sit at the top of docs/ and are maintained by path by the people (and tooling) doing the port. They are the evidence behind the user-facing pages; read them when you want to know why something is the way it is.
| Ledger | What it holds |
|---|---|
| DEPLOY | the deploy sequence with timings, the rehearsed teardown/redo, troubleshooting |
| ENV | every environment variable on both deployables, required vs optional, what unset means |
| CONTRACTS | packages/contracts protocol notes and changelog |
| INVENTORY | what the original codebase contained: routes, storage, env, dependencies, sizes |
| PARITY | the 64-route / 121-endpoint ledger: each item, its tests, its status |
| DRIFT | where the original's docs and code disagreed, and which one won |
| DECISIONS | numbered decisions, including the open ones that belong to the owner |
| PROVISIONED | what bootstrap-cloudflare.mjs created for the demo, so teardown can remove exactly that |
| TESTS | the test inventory across web, worker and examples |
| CLI | the CLI port: commands, modules, every removed tiny.technology reference with file:line, env vars, how it reaches the app vs the worker |
| EVIDENCE | things that were actually run against the live demo, with what came back — the CLI's init → login → enroll → use_device round-trip, sizes and timings |
| VERCEL_TEMPLATE | Vercel Templates submission requirements and status |