spec-kitty-constitution-doctrine

To establish a single source of truth for project governance, you define policies in a constitution.md file and derive deterministic YAML outputs. This approach ensures governance rules are consistently captured and enforced across the project lifecycle.

Automating policy capture involves running an interview-to-generation-to-sync workflow that extracts governance rules into governance.yaml and directives.yaml. This process contextualizes runtime actions like specifying and planning with auditable project policies.

You constrain runtime workflow actions by loading context-aware prompts derived from your governance doctrine during specify, plan, implement, and review phases. This provides auditable policy enforcement directly within the development workflow.

Yes, the governance workflow requires a constitution.md file as the single source of truth. From this markdown file, it deterministically extracts project policies into governance.yaml, directives.yaml, and metadata.yaml formats.

Yes, you can synchronize governance rules across projects using the sync feature within the constitution lifecycle. This ensures context-aware provisioning and consistent application of derived YAML policies during workflow execution.

Derivation needs doctrine references to provide context-aware constraints and auditable policy during runtime actions. They ensure the extracted governance.yaml and directives.yaml accurately reflect the core mission captured during interviews.