Architecture pointers
The framework itself — the fourteen invariants, the six layers, the lens model, profile axes, capability classes, the twin axis, the trust model — is documented on the main site. These docs do not duplicate it; they point at it and map it onto the running deployment you operate.
The framework, where it is written down
Section titled “The framework, where it is written down”- Framework overview — architecture and the six layers L0-L5, the fourteen invariants, the lens model, profile axes, capability classes S0-S3, the twin axis, resilience and the degradation ladder, the trust model.
- Framework structure — the seams between components.
- Standards map — every layer as an existing international standard or published open system; the framework adds no proprietary layer.
- Trust model.
- The specification parts: index — framework, profiles, events/identity/transforms, tiers and trust, conformance.
Invariants you meet as an operator
Section titled “Invariants you meet as an operator”The invariants surface operationally. A few examples, with where you bump into them in these docs:
| Invariant | Where it shows up |
|---|---|
| Enumeration resistance (I12) | the log exposes no listing surface; the gateway answers identical 404 bytes for unknown and unresolvable ids |
| Append-only event sourcing | every service journal; backup and restore |
| State-machine legitimacy (I6) | the issuer rejects lifecycle events that do not follow the machine |
| Graded trust (I9) | the projector’s per-element trust markers and selection gates |
| No-load-bearing-proprietary layer | the whole manifest — a deployment is data, rendered into open processes’ environments |
The numbered invariants are enumerated on the framework page — the authoritative list, not this table.
The running deployment map
Section titled “The running deployment map”What the pilot actually runs, service by service, and which framework seam each occupies:
| Service | Port (reference) | Tier/seam | Role |
|---|---|---|---|
| registry | 8390 | register | ISO 19135 items, discovery (C3/C4/C5), units, EXPRESS models, cross-register mappings |
| trust | 8391 | trust | SIGNATIF trust graph, lists, master list, revocations |
| log | 8392 | transparency | RFC 6962 commitments, receipts, tree heads |
| issuer | 8393 | issuance | passport lifecycle, typed events, Tier-A packs, verdicts |
| projector | 8394 | projection | lens views (EU/JP), presentation renders |
| gateway | 8395 | interop | UNTP triad + EN 18222 renders, UNTP ingest |
| archive | 8396 | Tier-C | OAIS notarized snapshots, log-anchored |
| console | 8389 | operations | the manifest surface |
| registry (JP peer) | 8399 | federation | the national-peer node — see running a national peer |
The tiers (A: the offline pack; B: the online passport; C: the notarized archive) are defined in the framework’s tiers and trust specification part; operationally, Tier A is what the CLI verifies offline, Tier B is what the issuer serves, Tier C is what the archive notarizes and anchors.