SYS_REF // 05
Architecture Registry
How the product works.
A layered registry of the modules that compose ProductOS. Each entry declares its purpose, dependencies, inputs, outputs, connected modules, and notes, presented as a systems document.
01 — Identity
Manifest Layer
Holds the canonical product identity and positioning that every other layer reads from.
Dependencies
Record Store
Inputs
Product identity, Positioning statements, Status declarations
Outputs
Canonical product manifest, Identity references
Connected Modules
Registry Layer · Evidence Layer
Relationships
Sits at the root of the dossier. Every other layer references the Manifest Layer for canonical identity, ensuring a single edit propagates everywhere.
Notes
Editing identity here is the single source of truth — downstream references update automatically.
02 — Cataloging
Registry Layer
Catalogs features, use cases, and modules as structured, related records.
Dependencies
Manifest Layer · Record Store
Inputs
Feature definitions, Industry tags, Relationship declarations
Outputs
Structured registries, Relationship edges
Connected Modules
Graph Layer · Manifest Layer
Relationships
Hosts the feature, use case, and architecture registries. Feeds the Graph Layer with the relationship edges it visualizes.
Notes
The registries here are what buyers edit most often when adapting the template.
03 — Relationships
Graph Layer
Computes how records relate so impact and dependency can be traced.
Dependencies
Registry Layer
Inputs
Relationship edges, Dependency declarations
Outputs
Navigable relationship graph, Impact traces
Connected Modules
Registry Layer
Relationships
Computes how records connect. Powers cross-references throughout the dossier and the impact analysis surfaced during reviews.
Notes
Derived layer — it stores no source data of its own, only computed relationships.
04 — Validation
Evidence Layer
Attaches proof — case studies, metrics, testimonials — to the claims they support.
Dependencies
Registry Layer
Inputs
Case studies, Metrics, Testimonials
Outputs
Filed evidence records, Claim-to-proof traces
Connected Modules
Registry Layer · Retrieval Layer
Relationships
Attaches evidence to the features and use cases it substantiates, making every claim in the dossier traceable to its support.
Notes
Evidence with no linked claim is flagged for review rather than discarded.
05 — Access
Retrieval Layer
Indexes the whole dossier so any record can be found through one search.
Dependencies
Registry Layer · Evidence Layer · Record Store
Inputs
Search queries, Index requests
Outputs
Ranked archival records, Provenance metadata
Connected Modules
Registry Layer · Evidence Layer
Relationships
Indexes every record for global search and serves the documentation reading column. Treats the entire dossier as one searchable archive.
Notes
Rebuilds its index on write, so search reflects edits immediately.
06 — Persistence
Record Store
Durably persists every record and the full history of its revisions.
Dependencies
None — foundational layer
Inputs
All record writes, Revisions
Outputs
Durable records, Revision history
Connected Modules
Manifest Layer · Registry Layer · Retrieval Layer
Relationships
The foundational persistence layer. Preserves every revision so the dossier retains a complete and auditable memory of its own history.
Notes
Foundational layer with no dependencies; everything else is built on top of it.