# Architecture of Proof (AoP)
> High-fidelity systems architecture for the age of probabilistic AI.

This index is optimized for AI agents and LLMs. Raw markdown versions of all posts are available via the `.md` extension on their URLs.

## Core Concepts & Vocabulary
- **Control Tiers Matrix**: Four-stage governance hierarchy defining autonomous agent boundaries from Tier 1 (Observe Only) to Tier 4 (Full Autonomy within Guardrails) with hard-coded circuit breakers.
- **Evidence Budget**: Dedicated allocation of compute, storage, and telemetry earmarked to produce replayable audit artifacts, cryptographic signatures, and causal logs for every autonomous decision.
- **Architectural Invariance Coefficient (AIC)**: Metric quantifying whether end-to-end system behavior remains provably identical when underlying model weights, prompts, or embedding models shift.
- **Marginal Frontier Alpha (MFA)**: Net operational and economic yield of upgrading to next-generation frontier weights after deducting token tariffs, latency penalties, and migration overhead.
- **Attention Dilution Tax**: Non-linear degradation in agent reasoning and precision that occurs when expanding context windows with unstructured tokens rather than structured, isolated chunks.
- **Marginal Accuracy per Token (MAPT)**: Optimization metric comparing accuracy gains against context window expansion and inference token expense.
- **Deterministic State Graph**: Finite-state execution substrate restricting probabilistic agent actions to mathematically validated state transitions.
- **Accumulated Context Graph**: Structured entity-relationship topology maintaining conversational and factual state across agent execution sessions without token leakage.
- **Cost per Successful Resolution (CPSR)**: True economic metric of agent execution incorporating retry overhead, verification passes, and human escalation costs.
- **Causal Trace**: Forensic black-box flight recorder capturing the exact step-by-step logical path from data ingestion to final output.
- **Composite Accountability**: Governance structure where every component—rules, models, and humans—carries a verifiable contract and local metrics.
- **Decision Traceability**: Logging the exact reasoning path, retrieved evidence, and verification checkpoints of every AI-influenced decision separately from raw outputs.
- **Continuous Verification**: Active validation in production ensuring contracts are kept, converting failures into updated deterministic requirements.
- **Accountability Debt**: Accumulation of AI capabilities without corresponding ownership contracts, decision traces, and autonomy boundaries.

## Key Resources & Navigation
- **Core Framework Map**: https://architectureofproof.com/framework
- **Technical Glossary**: https://architectureofproof.com/glossary
- **Full Archive (Chronological & Searchable)**: https://architectureofproof.com/archive
- **Maturity Score Calculator**: https://architectureofproof.com/maturity-score
- **XML Sitemap**: https://architectureofproof.com/sitemap.xml

## Recent Briefs (10 Most Recent)
Title | URL | Summary | Markdown Mirror
--------------------------------------------------------------------------------
**CORE FRAMEWORK** | https://architectureofproof.com/framework | The Architecture of Proof is a 4-phase AI governance lifecycle for building high-fidelity systems that orchestrate rules, models, and humans into verifiable, causal outcomes. | https://architectureofproof.com/framework.md
Capability vs. Reliability: Why the AI Products That Win Are Boring | https://architectureofproof.com/capability-vs-reliability | Enterprise AI deployable value is a function of potential workflow value minus expected failure cost, control cost, and change-management cost, subject to residual risk remaining within the organization's tolerance. Reliability reduces failure cost and is a necessary condition for deployment in high-consequence contexts—but it is not the binding constraint in most failed deployments. Adoption failure, integration mismatch, workflow economics, and accountability gaps bind first as often as tail error rates do. The products that earn multi-year enterprise contracts solve the complete equation, not just its risk term. | https://architectureofproof.com/capability-vs-reliability.md
The Telemetry-to-Eval Flywheel, Part 2: Architectural Isolation, Prioritization, and Boundary Mapping | https://architectureofproof.com/telemetry-to-eval-failure-diagnosis-boundaries | When operational friction surfaces in production AI, immediately adding prompt patches or model judges creates brittle test bloat. Transforming verified incidents into durable product assets requires running the Failure Diagnosis Matrix to isolate deterministic logic first, filtering candidates through qualitative promotion gates, and mapping multi-dimensional failure boundaries into standardized evaluation specification cards. | https://architectureofproof.com/telemetry-to-eval-failure-diagnosis-boundaries.md
The Telemetry-to-Eval Flywheel, Part 3: Tiered CI/CD Portfolios, Anti-Gaming, and the Minimum Viable Loop | https://architectureofproof.com/telemetry-to-eval-tiered-portfolios-governance | Scaling enterprise AI requires embedding evaluated invariants into a tiered testing portfolio that balances commit velocity against stochastic carrying costs. By structuring release gates across six operational tiers, insulating against telemetry gaming, tracking five governance diagnostics, and establishing a Minimum Viable Flywheel, organizations convert production incidents into compounding, auditable product defensibility. | https://architectureofproof.com/telemetry-to-eval-tiered-portfolios-governance.md
The Telemetry-to-Eval Flywheel, Part 1: Signal Discovery, Feasibility, and Enterprise Data Contracts | https://architectureofproof.com/telemetry-to-eval-flywheel | Production AI systems inevitably drift from offline benchmarks as enterprise users submit ambiguous, high-entropy inputs. Transforming operational telemetry into durable evaluation assets requires filtering workflows through an Observability Feasibility Gate, pairing behavioral signals with hazard analysis in an Assurance Triad, enforcing Telemetry Data Contracts, and decoding prompt thrashing and clipboard survival into testable failure hypotheses. | https://architectureofproof.com/telemetry-to-eval-flywheel.md
How to Build a Governed AI Evaluation System: Constrained Optimization and Four-Layer Triangulation | https://architectureofproof.com/ai-eval-governance-architecture | Optimizing an AI system for an isolated metric inevitably causes the system to manipulate the test. Building a production-grade evaluation system requires replacing composite scoring with constrained optimization, validating performance across a four-layer triangulation engine, separating assurance from product discovery, and gating deployments through a four-stage continuous integration pipeline. | https://architectureofproof.com/ai-eval-governance-architecture.md
Goodhart’s Law in Generative AI: When Better Evals Produce Worse Products | https://architectureofproof.com/goodharts-law-generative-ai | When an AI team optimizes for a single evaluation metric in isolation, the product learns to manipulate the test. Dashboard scores rise while real-world usefulness collapses into verbosity, defensive refusals, or sycophancy. Preventing metric gaming requires pairing every primary target with non-negotiable counter-metrics and cross-validating performance across independent signals. | https://architectureofproof.com/goodharts-law-generative-ai.md
Tracking Advances Across the Frontier: Models, Agents, Evals, and Graph Architectures in Product Portfolio Strategy | https://architectureofproof.com/frontier-models-agents-evals-portfolio-strategy | Enterprise product value does not accrue to teams that chase frontier model releases; it accrues to architectures that survive them. By decoupling task execution into calibrated authority tiers, grounding relational entities in explicit knowledge topologies, and anchoring governance in proprietary evaluation suites, portfolio leaders insulate enterprise workflows from model deprecation cycles while capturing genuine frontier breakthroughs. | https://architectureofproof.com/frontier-models-agents-evals-portfolio-strategy.md
The Unit Economics of a Retrieved Chunk: Designing the Enterprise Retrieval Budget | https://architectureofproof.com/unit-economics-retrieved-chunk | Retrieval-Augmented Generation is commonly treated as search infrastructure. In enterprise production, it is an evidence allocation problem under uncertainty. The product question is not how many chunks a system can afford to retrieve, but what Evidence Budget maximizes the expected value of a verified resolution under real-world cost, latency, and liability constraints. Under-retrieving context starves models of critical governing exceptions; over-retrieving inflates variable token bills, adds latency, and increases the risk of attention dilution. This guide establishes the cost decomposition, context frontier concepts, structured pre-filtering sequences, router risk controls, cold-start evaluation protocols, and a three-scenario financial model required to govern context as a scarce product investment. | https://architectureofproof.com/unit-economics-retrieved-chunk.md
Underwriting the Return on an AI Platform | https://architectureofproof.com/ai-platform-financial-return | The most common reason an AI platform business case fails CFO review is not a bad model, but the wrong baseline. Measuring platform value against squads doing nothing, rather than the best realistic local alternative, inflates the ROI by design. This post derives incremental platform value across five benefit terms, presents three-scenario phased cash flows over a 3-year horizon, and resolves the kill rule vs. patient capital tension through real-options logic. | https://architectureofproof.com/ai-platform-financial-return.md
What to Build, Buy, and Federate in an Enterprise AI Platform | https://architectureofproof.com/ai-platform-build-buy-federate | Once multiple squads confirm genuine workflow demand, the product manager faces the architecture ownership question. The default answer of building an end-to-end platform is almost always too broad. The right boundary separates commodity infrastructure (buy it) from domain intelligence (build and own it), then federates ownership across three tiers so the platform team never becomes a cognitive bottleneck on specialized domain decisions. | https://architectureofproof.com/ai-platform-build-buy-federate.md

## Full Content Mirror
For detailed synthesis or full site crawling, see the complete index at https://architectureofproof.com/llms-full.txt which contains all published briefs and their summaries.