Boundaries and map

Use this map to find the product that owns a behavior before changing configuration or code. Base Registry Engine (BReg) owns governed registry records.

Question	Owner
Who stores and mutates governed registry records?	Base Registry Engine
Who evaluates a bounded evidence requirement and signs the answer?	Registry Evidence
Who renders static registry metadata?	Registry Manifest
Who serves a curated provider index?	Registry Discovery
Who coordinates accountable human review?	Registry Casework
Who provides shared security and operational primitives?	Registry Platform

Trust boundaries

Boundary	Invariant
BReg write boundary	Only compiled model operations and authorized profiles can mutate PostgreSQL records.
Evidence source boundary	Every request target, method, path, credential, timeout, and response bound comes from reviewed configuration.
Evidence assertion boundary	Only declared concepts and value forms enter the signed assertion.
Manifest publication boundary	Output is descriptive static metadata and grants no runtime authority.
Discovery selection boundary	A selection is inert until an application validates and accepts it locally.
Casework decision boundary	Casework records review; the source system retains mutation authority.

No shared root activates the products atomically. Operators record and recover each product revision separately.

Next

• Architecture
• DPI safeguards alignment
• Security overview