spec-kitty-charter-doctrine

To turn a project charter into executable policy, you can generate structured, action-scoped governance context by extracting directives and doctrine references from the text. This activates policy constraints for specify, plan, implement, and review workflows without dumping the full doctrine catalog at once.

Action-scoped governance context is a subset of policy loaded per workflow action, such as specify, plan, implement, or review. It uses bootstrap, compact, or missing modes to constrain agent behavior dynamically during execution based on the specific task being performed.

You load the right doctrine policy by using the runtime to sync charter context and applying action-indexed doctrine scoping. This ensures deterministic extraction and staleness handling so agents receive only the relevant directives and tactics for their current step.

Yes, you can manage agent role profiles using a project charter by applying weighted matching against task context. The charter governance system resolves role-scoped behavior and connects mission execution surfaces to doctrine artifacts through MissionStepContracts and DelegatesTo links.

The best way to keep derived governance files deterministic after charter edits is through charter lifecycle management. You can interview, generate, extract via sync, and re-sync after edits while maintaining consistent hash handling and staleness checks across all derived policy files.

Yes, Spec Kitty supports programmatic doctrine access through a DoctrineService layer. This provides a doctrine-as-code interface that includes directives, tactics, paradigms, styleguides, toolguides, procedures, agent profiles, and step contracts for structured constraints integration.