Skip to main content
These pages and the repository are the same files. An agent reads them from docs/internal/; you read them rendered here. When the two disagree, the repository wins — so a documentation change is part of the code change, never a follow-up.

Foundations

The rules that do not change without an amendment: the constitution, seven standards and twenty-two architecture decisions.

Modules

Five bounded contexts, each with a PRD, a living technical spec and its feature specs — the unit we actually deliver.

Execution

Task specs an agent works from, runbooks a human follows when something breaks, and the diagram specifications.

Design registry

Every closed decision with its DEC-* id, and the questions still open.

Legal

Working drafts of the data-protection package. Unreviewed — a lawyer signs off before any of it leaves this site.

Glossary

The vocabulary this documentation assumes: tenant, contact, member, marketable contact.

Where the work stands

The zero in that third row is the whole picture. Rule R-S1 says no code merges for a feature whose spec is not approved, and nothing is approved yet, so the specifications are not waiting on more writing. They are waiting on decisions.

What is blocked on the owner

1

Validate the founding constitution

Particularly Part 2, the six port categories — every line there is inferred, and TS-002 defines adapters against it. Confirming or correcting six lines now is cheap; doing it after the adapters exist is not.
2

Review amendment A1 line by line

It adds two port categories to a closed list, which is exactly the kind of change the constitution requires a human to make.
3

Answer group A of the open questions

52 questions, each with a recommendation. Answering them moves 37 specifications toward approved.
4

Sign off the fifteen loyalty documents in review

They sit at 0.2.0. Approval is what makes them 1.0.0 and unblocks the first slice.

How a decision reaches the code

Every link in that chain is checked in CI. A feature spec citing a DEC-* that does not exist fails the build; a table in a module spec that no feature spec claims is reported as uncovered. The mechanics are in the specification system.
This site is a mirror of a private repository and is not indexed. The Spanish version is a faithful translation of the same files: English is authoritative for engineering documents, Spanish for the legal package and the design registry.