TKT Space — Product documentation
This site is the source-of-truth description of the product as it exists today — its entities, the rules they obey, and the flows users move through.
If you’re looking for how to change the product, you want the spec workflow instead — see _workflow/specs/ (in the repo) and the /new-ticket, /build slash commands described in _workflow/docs/PIPELINE.md.
What’s here
- Domain — every business entity, grouped by bounded context. Start here when you need to understand what a thing is.
- Flows — actor-driven journeys across surfaces. Start here when you need to understand what a thing does.
- Glossary — alphabetical term index with one-sentence definitions, linking to full entity pages.
How to use
| If you are | Read |
|---|---|
| Onboarding to the codebase | Domain first, then a couple of flows |
| Planning a new feature | Relevant entity docs + related flows + linked specs |
| Fixing a bug | The entity whose invariants are violated + the flow that triggers it |
| Auditing what we built | Glossary for breadth, then drill into specific entities |
How this site is maintained
The .mdx files under content/ are the source of truth. They are kept in sync with tktspace-backend by the docs-writer agent, which runs:
- after every
/build(write mode) — updates docs touched by the implementation - periodically (audit mode) — sweeps for drift, missing skeletons, orphan files
See _workflow/docs/README.md for the full maintenance protocol.