Verification Engine direction
Roadmap · after v1.0Drift Detection
In plain terms: spot when code drifts away from agreed architecture — and tell bad violations apart from approved evolution you meant to allow.
Bad drift
New direct DB access in API layer violates ADR-12 layering rule. No accepted baseline on record.
Accepted evolution
Pattern change approved in PR #2102 and recorded as accepted baseline pair. Alert suppressed.
- Graph vs contract/convention comparison — deterministic
- Accepted baseline pairs for intentional architecture changes
- Integration with PR checks and engineering scorecards
- edge_class and verification_status on fabric edges
Discuss your AI governance challenges
See the local-first decision-control plane — Context Lens, quality map, and human apply gates. v1.0 ships end of August 2026.