Glossary
What each word means here, and which domain owns it. Read the glossary.
BTS Platform
How the platform is built, from the whole system down to a column, read from the code where it can be and written by hand where it cannot.
Zoom in
Section titled “Zoom in”Each level is a page with a map of what it holds, and every box on a map opens the level beneath it.
PlatformThe whole system as one box: the people who use it and the providers it relies on.
RuntimeThe deployment units, the stores they share, the providers each calls and the domains it runs.
InfrastructureThe runtime as AWS resources: DNS, CloudFront, load balancers, ECS, the stores and the queues.
DomainsEvery domain and process, and what each depends on: calls through a port, events, and rows it names.
A domainIts modules and their aggregates, and the domains each module calls, is called by, or hears from.
An aggregateThe tables written under one lock, their columns, the events they publish and the requirements they hold.
Every tableAll tables, by domain and aggregate, with the ones outside an aggregate and why.
How it works
Section titled “How it works”Multi-tenancyHow a request is held to one Account, from its host to the rows Postgres shows it.
IdempotencyHow a retried request, a redelivered event and a repeated callback each do their work once.
Rate limitingThe budget a request is charged against, and what happens when it is spent.
Access and rolesPermissions, the roles that hold them, and how operators, staff, keys and agents get them.
Call it
Section titled “Call it”Admin GraphQLWhat operators, integrations and agents call, by domain, with examples. Each operation is also an MCP tool.
Public GraphQLWhat an Account's sites call, by persisted operation, and who may call each field.
WebhooksEvery event an endpoint can ask for, its envelope and its payload, and what is built of delivery.
Provider hooksThe REST routes providers call on the hooks unit, from its OpenAPI document.
Tech stack
What it is built with, and why each was picked. See the stack.
Principles
Why the rules are the shape they are. Read the principles.
Decisions
The rules that stand today, by area, each citing its record. Read the digest.
Code
Every package’s README and SPEC, rendered where they live. Start at the repository README.