Decantr — AI Frontend Governance for AI-edited codebases

# Decantr > Agent-neutral UI change control for codebases edited by AI. Decantr observes project-owned authority, prepares compact change context, verifies the resulting diff, and reports typed local evidence. ## Release Status - Current published stable: Decantr 3.9.4. - Active direction: Decantr 3.10 UI Change Control Proof. - 3.10 is not released and is not value-proven. - 3.9.4 publication used a sole-maintainer waiver. Do not claim human finding precision/recall, human release qualification, adoption proof, or measured frontier-model improvement. ## Published 3.9.4 Loop 1. Observe: `decantr scan` is a read-only selected-app inspection. 2. Attach once: `decantr adopt --yes` writes Decantr governance artifacts after review. 3. Prepare: `decantr task <route> "<change>"` prepares compact, graph-backed route context. 4. Verify: `decantr verify` checks the diff and available evidence. 5. Report: Project Health, JSON, Evidence Bundle, and CI artifacts carry the result. In monorepos, pass the same `--project <app>` to every app-scoped command. A successful 3.9.4 scan means the scanner ran; it does not prove that the selected routes, components, styling, or implementation source are correct. ## 3.10 Authority Model Routes are one evidence source, not the product ontology. The approved UI surfaces are routes, layouts, components, stories, overlays, flows, packages, and runtime states. Readiness axes are independent: selected-app authority, production-surface authority, topology completeness, implementation taskability, component inventory quality, styling authority, and runtime evidence. The 3.10 primary result is `ready`, `limited`, `blocked`, or `unsupported`. Numeric confidence and aggregate fit labels must not conceal an unresolved axis. Decantr 3.9.4 task context remains primarily route-backed. Do not claim that non-route UI-surface task context has shipped until a 3.10 release does so. ## Product Boundary Active 3.10 investment: `@decantr/verifier`, fra