options: type: guide version: 1.0.0 birth: ‘2026-02-01’ token_size: 2179¶
ADR Index¶
Active Architecture¶
governance¶
- ADR-26035
Architecture Knowledge Base Taxonomy
Adopt a three-category Architecture Knowledge Base taxonomy aligned with ISO 42010, formalized as a directory structure and machine-readable configuration.
- ADR-26042
Adopts a composable block frontmatter schema as the universal standard for all governed documents. Defines 3 block types (identity, discovery, lifecycle) that compose additively per document type. Requires every file with frontmatter to self-identify via options.type so validation scripts load the correct spoke config. Eliminates directory-based type inference, fixes inconsistent date semantics, and replaces flat required-fields lists with additive block inheritance. Hub config (.vadocs/conf.json) defines field registry, block composition, and 10-type taxonomy; spoke configs (.vadocs/types/.conf.json) add type-specific required fields, allowed statuses, and severity values.
untagged¶
- ADR-26001
- Use of Python and OOP for Git Hook Scripts
- ADR-26002
- Adoption of the Pre-commit Framework
- ADR-26013
- Just-in-Time Prompt Transformation
- ADR-26014
- Semantic Notebook Pairing Strategy
- ADR-26016
- Metadata-Driven Architectural Records Lifecycle
- ADR-26023
- MyST-Aligned Frontmatter Standard
- ADR-26024
- Structured Commit Bodies for Automated CHANGELOG Generation
- ADR-26026
- Dedicated Research Monorepo for Volatile Experimental Projects
- ADR-26027
- Model Taxonomy: Reasoning-Class vs Agentic-Class Selection Heuristic
- ADR-26028
- Tool-Agnostic Phase 0: Intent Synthesis
- ADR-26029
- pyproject.toml as Tool Configuration Hub
- ADR-26037
- Smallest Viable Architecture (SVA) Constraint Framework
- ADR-26038
- Context Engineering as Core Design Principle
- ADR-26040
- Podman Kube YAML as Deployment Standard
- ADR-26045
- AI-Native Development — Code as Primary Documentation
- ADR-26049
- Unified Manifest for External Repository Management
Evolutionary Proposals¶
untagged¶
- ADR-26009
- Adoption of Ansible for Idempotent Configuration Management
- ADR-26010
- Adoption of Molecule for Automated Ansible Role Validation
- ADR-26012
- Extraction of Documentation Validation Engine
- ADR-26015
- Mandatory Sync-Guard & Diff Suppression
- ADR-26017
- ADR Format Validation Workflow
- ADR-26020
- Hub-and-Spoke Ecosystem Documentation Architecture
- ADR-26021
- Content Lifecycle Policy for RAG-Consumed Repositories
- ADR-26022
- Standardization of Public Documentation Hosting on GitHub Pages
- ADR-26025
- RFC→ADR Workflow Formalization
- ADR-26030
- Stateless JIT Context Injection for Agentic Git Workflows
- ADR-26032
- Tiered Cognitive Memory: Procedural Skills vs. Declarative RAG
- ADR-26033
- Virtual Monorepo via Package-Driven Dependency Management
- ADR-26036
- Config File Location and Naming Conventions
- ADR-26039
- pgvector as Ecosystem Database Standard
- ADR-26041
- Client-Side Logic with Server-Side Retrieval
- ADR-26043
- Ecosystem Package Boundary
- ADR-26044
- Skills as Progressive Disclosure Units
- ADR-26046
- External Product Repos as Research Directories
- ADR-26047
- Integrate Heuer Intelligence Tradecraft into AI System Methodology
- ADR-26048
- Formalize Weighted Response Confidence (WRC) as Ecosystem Evaluation Metric
- ADR-26054
- JSON as Governance Config Format
Rejected¶
untagged¶
- ADR-26003
- Adoption of
gitlintfor Tiered Workflow Enforcement - ADR-26004
- Implementation of Agentic RAG for Autonomous Research
- ADR-26005
- Formalization of Aider as the Primary Agentic Orchestrator
- ADR-26031
- Prefixed Namespace System for Architectural Records
- ADR-26034
- Agentic OS Paradigm: Skills as Composable Applications
Superseded¶
untagged¶
- ADR-26006
- Requirement for Agentic-Class Models for the Architect Phase
- ADR-26007
- Formalization of Phase 0: Intent Synthesis (Requirements Engineering)
- ADR-26008
- Selection of Reasoning-Class Models for Abstract Synthesis (Phase 0)
- ADR-26011
- Formalization of the Mandatory Script Suite Workflow
- ADR-26018
- Universal YAML Frontmatter Adoption for Machine-Readable Documentation
- ADR-26019
- Mirroring YAML Metadata to Document Body for Human Verification