vision-doc

To maintain OKRs and non-goals across quarters, establish a vision document with auditable versioning and ADR-backed governance. This ensures consistent alignment across teams by capturing rationale and governance decisions in history entries during quarterly updates.

ADR-driven governance for a vision document involves using Architecture Decision Records to capture rationale and governance decisions. It enforces auditable versioning and governance caps for OKRs and non-goals, ensuring alignment during bootstrap and quarterly updates.

Bootstrap a workspace vision file by writing the _vision/VISION.md document from a provided skeleton. You then create an initial history entry to establish the audit trail, satisfying requirements for auditable versioning and governance documentation.

Yes, you can derive project-level OKRs from a pre-dispatch vision slice. The process pulls the top 3 relevant OKRs from the workspace vision document to provide alignment context, ensuring read and write cycles maintain consistency across project scopes.

The best way to document governance decisions for non-goals is through an update flow with ADR documentation and history entries. This captures the rationale behind governance caps and changes, maintaining an auditable history across workspace and project scopes.

Yes, you need auditable versioning for agency vision updates to satisfy governance requirements. It tracks changes to active OKRs and non-goals by capturing rationale and decisions in ADR documentation and history entries across quarterly cycles.