Architecture reference
Component boundaries and data flow, described so that each boundary can be tested independently rather than reasoned about informally.
Boundaries as testable claims
A boundary that exists only in a diagram tends to erode. Each boundary described here corresponds to something a test can check: a package that must not import another, a surface that must not hold a credential, or a record that must not be mutated after it is written.
Boundary rules
| Presentation | Reads published metadata only; no private interface |
|---|---|
| Outcome computation | No presentation dependency; deterministic given inputs |
| Ledger | Append-only; balances derive from entries |
| Round lifecycle | Unknown outcomes are held for reconciliation |
| Released artefacts | Referenced by content digest |
This repository in the diagram
The site you are reading is the presentation edge and nothing more. It is a static build with no server component, so it has no route through which a private interface could be reached even if one were configured.
That constraint is what allows this repository to be reviewed on a lighter footing than the components that compute or record outcomes.