You approved the AI tools. Now own what they ship.

A production incident is traced to an architectural decision an AI agent made three sprints ago. No architect reviewed it. The PR passed all code quality gates. The design intent gate did not exist.

A regulatory audit asks for evidence that your security policies were applied to every code change over the past 12 months. You have test results. You have SAST reports. You have no record of which Lenses were evaluated per PR, which Steering directives were checked, what was found, or what decision was made. The auditor asks a follow-up.

A senior engineer leaves. The system state they held in their head — the boundaries they knew not to cross, the patterns they maintained without documenting them — leaves with them. You have no externalised architecture record. The next hire ships without that context.

Your AI tool adoption made your engineers faster and your architects blind. Velocity is up. Architecture visibility is down. You find this out when something breaks that no one on the team can reason about.

Every sprint, someone approves a corner cut to meet a release date. The PR merges with a comment: 'tech debt — revisit.' No owner. No stated justification. No documented risk. Six months later, when that decision causes an incident, the post-mortem cannot identify who made it or why.

Architecture conformance rate per sprint

The percentage of PRs in each sprint that violated your design intent — crossed a Steering-defined boundary, violated a Lens directive, introduced an undocumented dependency, deviated from an established pattern.

Currently: unknown. No Lens-based CDA gate exists to produce a conformance rate.

Steering violation discovery latency

The elapsed time between a design violation being introduced and it being detected. In CI/CD pipelines with no design gate, detection happens at incident review — if at all.

Currently: weeks or never.

Architect-to-PR ratio

One architect against 50+ AI-generated PRs per week, each containing structural decisions the agent made without architectural context. Manual review at this volume is not a process. It is theatre.

Currently: unsustainable and deteriorating.

Architecture health trend

Is the system getting cleaner or dirtier sprint over sprint? Are violations increasing or decreasing? Is drift accelerating? Without a Lens-based CDA gate producing sprint-over-sprint conformance data, there is no data source for this question.

Currently: gut feel.

CDA gate on every PR

Architecture conformance rate becomes a tracked metric. Every sprint produces a number. The first time you see it, the number will be uncomfortable. That discomfort is diagnostic information you did not previously have.

Every violation is caught before merge

Design violation discovery latency collapses from weeks to minutes. The violation is flagged at the PR, before it enters the codebase, before it compounds into an incident.

Architect called only when CDA finds drift

The architect-to-PR ratio problem is solved structurally. The system handles the pattern-matching. The architect handles the exceptions — the genuine design decisions that require judgment, not the 47 PRs that were compliant.

Architecture Ledger gives continuous system state

Architecture health trend becomes real data. The Ledger maintains the live baseline of your system. Sprint-over-sprint conformance data tells you whether the system is getting cleaner or dirtier — without waiting for an incident to find out.

Intentional debt becomes a named, owned record

When an architect approves a CDA finding rather than blocking it, the approval is a formal debt acceptance record in the Architecture Ledger: named approver, timestamp, specific Steering artifact violated, stated justification, known risk, resolution commitment. The 'tech debt — revisit' comment becomes a traceable decision. The post-mortem has an answer.