Standards Framework
Standards Framework
Twenty active standards govern every document, commit, and structural decision in domus-captures. Each standard uses RFC 2119 normative language (MUST, SHOULD, MAY) and carries machine-parseable attributes for automated auditing.
Standards vs Patterns vs Codex
Three knowledge types serve distinct roles. Confusing them degrades the system.
| Type | Voice | Purpose | Example |
|---|---|---|---|
Standard |
Prescriptive ("MUST", "SHALL NOT") |
Governance — defines what compliance looks like |
STD-009: Directory Structure |
Pattern |
Descriptive ("I noticed", "This works because") |
Field knowledge — captures what practitioners learn |
Pattern: Verification-First Debugging |
Codex |
Referential ("Syntax:", "Usage:") |
Quick lookup — retrieves commands and syntax |
Codex: awk Field Extraction |
Domain Coverage
| Domain | Count | Scope |
|---|---|---|
Operations |
6 |
Project lifecycle, case studies, deployments, monitoring, runbooks, navigation |
Documentation |
11 |
Naming, structure, attributes, cross-references, worklogs, sessions, patterns, codex, examples, templates, quality |
Security |
1 |
Secrets handling and credential hygiene |
AI Interaction |
1 |
Claude Code session standards and CLAUDE.md governance |
Workflow |
1 |
Git commit discipline and CI/CD practices |
Standards Registry
| ID | Name | Domain |
|---|---|---|
STD-001 |
Project Structure |
Operations |
STD-002 |
File Naming Conventions |
Documentation |
STD-003 |
AsciiDoc Attribute Governance |
Documentation |
STD-004 |
Cross-Reference Syntax |
Documentation |
STD-005 |
Worklog System |
Documentation |
STD-006 |
Case Study Taxonomy |
Operations |
STD-007 |
Secrets Handling |
Security |
STD-008 |
Git Commit Discipline |
Workflow |
STD-009 |
Directory Structure |
Operations |
STD-010 |
Navigation Governance |
Operations |
STD-011 |
Session Documentation |
Documentation |
STD-012 |
Pattern Journal Format |
Documentation |
STD-013 |
Case Study Classification |
Operations |
STD-014 |
Deployment Records |
Operations |
STD-015 |
Template System |
Documentation |
STD-016 |
Codex Format |
Documentation |
STD-017 |
Examples Library |
Documentation |
STD-018 |
Quality Audit Process |
Documentation |
STD-019 |
CLAUDE.md Governance |
AI Interaction |
STD-020 |
Runbook Format |
Operations |
Lifecycle
Every standard follows a four-stage lifecycle:
-
Draft — Under development; not yet enforceable. Content may change without notice.
-
Active — Ratified and enforceable. All new content MUST comply; existing content SHOULD be migrated.
-
Superseded — Replaced by a newer standard. The superseding standard’s ID is recorded in the
:std-superseded-by:attribute. -
Retired — No longer applicable. Retained in the registry for historical reference.
All 20 current standards are Active.
Machine-Parseable Attributes
Every standard document carries metadata attributes that agents and audit scripts can grep:
:std-id: STD-009
:std-status: Active
:std-domain: Operations
:std-owner: EvanusModestusAutomated auditors parse these with:
grep -rh ':std-status:' docs/modules/ROOT/partials/standards/ | sort | uniq -cCLAUDE.md Relationship
Standards are the source of truth.
CLAUDE.md is the enforcement mechanism.
The relationship is unidirectional:
Standards (define) ──▶ CLAUDE.md (enforce) ──▶ Claude Code (comply)
When a standard changes, the corresponding CLAUDE.md section MUST be updated. When CLAUDE.md and a standard conflict, the standard wins. CLAUDE.md may add implementation detail (tool-specific flags, coaching rules) that standards do not cover, but it MUST NOT contradict any standard.
Quality Audit
As of 2026-04-06, the standards framework holds a 100% pass rate across 400 auditable criteria.
| Metric | Value | Date |
|---|---|---|
Standards audited |
20/20 |
2026-04-06 |
Criteria evaluated |
400 |
2026-04-06 |
Pass rate |
100% |
2026-04-06 |
Non-conformities |
0 |
2026-04-06 |