Reference Library
The Reference Library is where you capture the governance content that guides architectural choices: policies, standards, frameworks, decisions, blueprints, and patterns. ArchNGN treats these as first-class, searchable architecture guidance records.
You reach it from the Repository as the Reference Library tab.
What It Holds
Section titled “What It Holds”| Type | Description |
|---|---|
| Policy | A high-level rule or intent that must be followed (e.g., “Data Privacy Policy”). |
| Standard | A precise, mandatory constraint or approved technology (e.g., “PostgreSQL 14”). |
| Framework | A control set from a compliance regime, typically added by applying a Framework. |
| Decision | A recorded architectural choice or direction (e.g., “Use React for the frontend”). |
| Blueprint | A reference design or target architecture. |
| Pattern | A reusable solution to a common architectural problem (e.g., “Circuit Breaker”). |
Working with Guidance
Section titled “Working with Guidance”- Create and edit: Add an item, set its type, description, and source, and mark it as approved when it has been ratified.
- Attach source material: Upload the source document that backs a policy, standard, or decision so the full text travels with the record.
- Search and filter: Find items by name, type, source, or approval state across the active workspace.
- Approval status: Distinguish ratified guidance from drafts still under review. Approval state is reflected in the Explorer Context view, where guidance nodes are coloured by whether they are endorsed.
Where Guidance Comes From
Section titled “Where Guidance Comes From”- Manual: Captured directly as you ratify policies and standards.
- Frameworks: Applying a Framework instantiates its control catalog here as guidance.
- Workstreams: Deviation detection can propose new Architecture Decisions for review (see Workstreams).
Why It Matters
Section titled “Why It Matters”Workstreams use the approved guidance in the Reference Library as grounding context. Designs are generated and reviewed against the governance content you have captured here, so keeping it current is what makes ArchNGN’s guardrails meaningful.
Related
Section titled “Related”- Metamodel: the schema for objects; governance guidance is managed here rather than as object categories.
- Frameworks: compliance packages that populate the library and drive conformance reporting.
- Workstreams: AI workflows that design and review against your standards.
- Repository: the broader view that hosts the Reference Library tab.