Document Type Taxonomy · SYS-020
OBS
Observation
Documented pattern, finding, or behavioral tendency observed during operations. Operator sign-off only — no council vote required unless promoted to STD.
34+ entries · Governance category
STD
Standard
Codified rule governing DDL operations, architecture, or output quality. Council vote (LOCK / REVISE / REJECT) required before ratification.
~12 entries · Governance category
PRO
Protocol
Repeatable procedure governing a specific workflow or interaction pattern. Step-by-step process, not an enforceable rule.
~8 entries · Operational category
SYS
System
Full system definition — architecture, schema, governance layer. Each SYS entry corresponds to one of the 44 DDL systems.
44 systems · Reference category
ADR
Architecture Decision Record
Immovable architecture decision. Council review required. Once ratified, changes require a new ADR with explicit supersession. Feeds dex_decisions.
1 ratified · See Decisions Registry
REC
Recommendation
Non-binding guidance. Not an enforceable rule. May be promoted to STD when pattern recurs across systems.
~4 entries · Advisory
Registry · All Entries
| ID | Entry | Category | Status | Governance |
|---|---|---|---|---|
| OBS-01 | Governance at Creation No system built without embedded governance at initial architecture stage | Governance | OPERATOR | Operator sign-off |
| OBS-02 | Layered Separation Protocol Separation of data, logic, and presentation layers enforced at build time | Governance | OPERATOR | Operator sign-off |
| OBS-03 | Structural Resilience Bias Build for extensibility first; performance optimization is a second pass | Governance | OPERATOR | Operator sign-off |
| OBS-04 | Explicit Trace Mapping Every output must trace to a source; untraceable outputs are not governed outputs | Governance | OPERATOR | Operator sign-off |
| OBS-05 | Embedded Guardrail Enforcement Controls embedded in system architecture, not applied post-build as overlays | Governance | OPERATOR | Operator sign-off |
| OBS-06 | Pattern Governance Lifecycle Observed pattern → Documented → Promoted to STD → Governed → Automated | Governance | OPERATOR | Operator sign-off |
| OBS-07 | Instance vs Invariant Distinction System must distinguish between what changes per instance vs what never changes | Governance | OPERATOR | Operator sign-off |
| OBS-08 | External System Decontamination Protocol External data must be cleaned and typed before entering the governed corpus | Governance | OPERATOR | Operator sign-off |
| OBS-09 | VACANT Confirmed gap in the numbering sequence. Available for future assignment. | — | VACANT | — |
| OBS-10 | Deterministic Sample Traceability Every sample must produce identical results from identical inputs — no ambient randomness | Governance | OPERATOR | Operator sign-off |
| OBS-11 | Continuous Reconciliation During Transform Data transformation validates against source at every stage, not only at output | Governance | OPERATOR | Operator sign-off |
| OBS-12 | Density Over Volume Analysis Concentrated high-signal data outperforms large low-signal datasets in every context | Governance | OPERATOR | Operator sign-off |
| OBS-13 | Controlled Write Layer Over Immutable Data Raw source data is never modified; all writes go through a governed write layer | Governance | OPERATOR | Operator sign-off |
| OBS-14 | Historical Anchoring of Variable Inputs Version headers on all derivative files — source date locked at creation, not recalculated | Governance | OPERATOR | Operator sign-off |
| OBS-15 | Execution Environment Declaration Every automated process declares its execution environment in its output header | Governance | OPERATOR | Operator sign-off |
| OBS-16 | Intent Preservation During Structural Upgrade When architecture changes, original intent must be explicitly documented and preserved | Governance | OPERATOR | Operator sign-off |
| OBS-17 | Promoted → PRO-17 This OBS was promoted to a Protocol entry. See PRO-17. | — | PROMOTED | — |
| OBS-18 | Promoted → PRO-18 This OBS was promoted to a Protocol entry. See PRO-18. | — | PROMOTED | — |
| OBS-19 | Single Control Point Filtering All filter logic flows through one governed control point — no distributed filter logic | Governance | OPERATOR | Operator sign-off |
| OBS-20 | Involuntary Governance Fingerprint: when a system enforces governance before the operator consciously chose to govern it | Governance | OPERATOR | Operator sign-off |
| OBS-21 | Progressive Disclosure Architecture Surface exposes only what the current context requires; depth is always available but never forced | Governance | COUNCIL LOCKED | 8 / 9 seats |
| OBS-22 | Domain-Agnostic Pattern Application The architecture does not change between domains. The data does. | Governance | COUNCIL LOCKED | Unanimous |
| OBS-23 | Boot Protocol / Prompt Envelope Governance Every AI session begins from a governed prompt envelope — no cold-start context | AI Governance | COUNCIL LOCKED | 5 / 9 seats |
| OBS-24 | Audience-Surface Separation The surface (what is shown) and the audience (who sees it) are governed independently | Governance | COUNCIL LOCKED | 5 / 9 seats |
| OBS-25+ | OBS-25 through OBS-34+ ~10+ entries confirmed in the master index. Bodies and governance status unverified pending audit session. | AUDIT NEEDED | AUDIT NEEDED | Unverified |
| OBS-34 | Surface Calibration ≠ Deep Calibration A model that looks calibrated on the surface may be fundamentally miscalibrated at depth | AI Governance | COUNCIL LOCKED | Council-locked |
| STD-FACT-001 | Universal Fact Table Standard 34 columns · 5 zones · Star schema grain · Excel template + dashboard wiring | Architecture | RATIFIED | Council-reviewed |
| STD-VAULT-002 | Knowledge Vault Intake Classification 20 artifact types · 7 categories · Canon, Foundation, and Archive path markers | Governance | RATIFIED | Council-reviewed |
| STD-CORPUS-001 | Corpus Ingestion Standard 23 extension types · Tier classification rules · Canon vs Archive routing criteria | Corpus | AUDIT NEEDED | Unverified |
| STD-CORPUS-002 | Collection Authority Model Superseded by ADR-CORPUS-001. Governance moved to ADR system. | Corpus | SUPERSEDED | See ADR-CORPUS-001 |
| STD-NAMING-001 | DDL Naming Conventions File naming · Route naming · Component naming · Collection naming across all systems | Architecture | AUDIT NEEDED | Unverified |
| PRO-CANONPRESS-001 | CanonPress Publication System Six series · CR- prefix format · Verdict protocol · Synthesis instructions for DJ | Publication | RATIFIED | Council-reviewed |
| PRO-VAULT-001 | Knowledge Vault Intake Protocol Drop folder workflow · Single file ingest · Provenance tagging · dex_dave gating | Operational | DRAFT | Pending ratification |
| PRO-FLYER-001 | Pricing Flyer Prompt Template Generic PM prompt for VC-ready HTML pricing flyers · Four-section structure · CottageHumble spec | Product | OPERATOR | Operator sign-off |
| PRO-TIPS-001 | Software Tips & Tricks Council Prompt OneNote · Excel · Word · Visio · CMD · PowerShell · Adobe site wing content protocol | Content | DRAFT | Pending build |
| SYS-020 | Document Template Registry 20 document types across 7 categories · Site template mapping · CODEX / CHRONICLE / ATLAS / LEDGER / CONSOLE / DOSSIER | Governance | RATIFIED | v1.0 · 2026-03-03 |
| SYS-019 | DexVerse Knowledge Graph SQLite · ACE governance wrapper · SHA-256 content hashing · 13-test invariant harness | Infrastructure | PHASE 1 LIVE | Built session |
Audit Plan · Next Session
What the audit session will cover
SCOPE
— Open all template/protocol folders from the archive
— Enumerate every OBS-XX entry with a body
— Confirm OBS-25 through OBS-34+ body status
— Identify which are fully written vs just named
— Assign governance status to each (LOCK / OPERATOR / DRAFT)
— Flag duplicates and collapsed entries
— Identify STDs that were written but not registered
— Enumerate every OBS-XX entry with a body
— Confirm OBS-25 through OBS-34+ body status
— Identify which are fully written vs just named
— Assign governance status to each (LOCK / OPERATOR / DRAFT)
— Flag duplicates and collapsed entries
— Identify STDs that were written but not registered
DELIVERABLES
— This page updated with verified counts and status
— AUDIT NEEDED entries resolved or formally deferred
— OBS-25 through OBS-34+ bodies confirmed or flagged
— STD-CORPUS-001 and STD-NAMING-001 verified
— New entries added from folders not yet in registry
— dex_decisions ingestion list finalized for standards
— AUDIT NEEDED entries resolved or formally deferred
— OBS-25 through OBS-34+ bodies confirmed or flagged
— STD-CORPUS-001 and STD-NAMING-001 verified
— New entries added from folders not yet in registry
— dex_decisions ingestion list finalized for standards
Navigate the Vault
DECISIONS REGISTRY
ADRs & Architecture Locks
The immovable decisions. ADR-CORPUS-001 is the first. Standards feed dex_decisions.
View Decisions →
THE CORPUS
566,804 Chunks
These standards live in dex_canon. Once dex_decisions is built, they move there too.
Explore the Corpus →
THE METHOD
Chaos → Structured → Automated
These standards are the Structured phase made visible. The methodology, documented.
Understand the Method →
COMMANDS
Ingest the Registry
dex-ingest.py --collection dex_decisions. These entries are the content that earns the weight.
Go to Commands →