Records stay home
Registry Stack keeps record ownership explicit. Base Registry Engine (BReg) stores records only when it is the institution’s governed system of record. Registry Evidence reads a fixed authoritative source to derive a bounded answer and does not become another record store.
Registry Evidence boundary
Section titled “Registry Evidence boundary”A caller supplies a request matching a predefined requirement. Registry Evidence authenticates and authorizes the caller before source access, executes only the reviewed source request, derives the declared concepts, signs the assertion, and writes keyed audit records. It does not persist the selector, source response, or assertion as an application database.
The source remains responsible for correctness and currentness. Registry Evidence proves which configured requirement and source response produced an assertion, not that the underlying fact was legally or substantively correct.
Base Registry Engine boundary
Section titled “Base Registry Engine boundary”BReg is different because it is the registry. It owns its PostgreSQL records, model, authorization, history, audit, changes, and events. Applications read and write them through BReg’s governed API. Another Registry Stack product does not automatically publish or copy those records.
What crosses a boundary
Section titled “What crosses a boundary”Only the documented product contract crosses a boundary: an authorized BReg response, a signed Evidence assertion, or static Manifest metadata. Credentials, source diagnostics, undeclared fields, and internal storage do not become portable outputs.