tC Admin is a planned hosted web application for Bible translation team leaders and project managers. It will help managers oversee writable Door43 repositories, maintain valid Scripture Burrito metadata, understand repository health and coverage, upload files safely, and prepare selective releases without publishing unfinished work.
The application is being built in shared/ (the operation catalog as schemas), worker/ (the Cloudflare Worker), and web/ (the Vite and React app the Worker serves), under the module map in the architecture. npm ci && npm run check runs every check; npm run dev builds the web app and runs the Worker locally against QA Door43 with the values in .env (see .env.example).
AGENTS.md is the entry point for anyone, human or agent, working in this repository: the document tower, the rules, how to work an issue.
Read downward for why, upward for how.
- Vision: why this exists
- Product specification: what it must do, with acceptance scenarios S1 to S7
- Domain model and glossary: the concepts, their states, and their identifiers
- Invariants: what must never break, numbered and tested
- Operation catalog: everything the system can do, with plan, apply, receipt, and typed errors
- Architecture: the layers and where code goes
- Architecture decisions: why this way
- Evidence register: what is verified about Door43 and what is still open, with owners
- Roadmap: milestones and epics
- Traceability: how every issue connects to the above
prototypes/door43-mcp: prompt-first Door43 MCP field-kit proof of concept, not a tC Admin deliverable
The read-only portfolio prototype that was in prototypes/tc-admin was retired by #7; its Door43 client, sign-in, and tests moved to worker/, and it remains in the Git history.