rule-docker-shared-project-mandate-always-on

To enforce project mandate alignment, bind a rule to foundation_documentation/project_mandate.md at task start. This guarantees all governance, design, and implementation decisions remain grounded in foundational documentation and prevents drift across teams.

When foundational documentation is missing or stale, the rule logs the gaps and blocks progress. It prompts users to provide updates for critical core docs like domain_entities.md and system_roadmap.md before any further work proceeds.

Validate task decisions by loading core docs such as foundation_documentation/system_roadmap.md and domain_entities.md. The rule checks alignment with these foundational documents within shared Docker project contexts to ensure compliance.

Yes, a project_mandate.md file is required. The rule enforces a binding reference to foundation_documentation/project_mandate.md at the start of any task to ensure alignment and proper documentation governance.

Your task gets blocked because the documentation governance rule detects missing or stale foundational documents. It halts progress until you update the required core docs to ensure all decisions align with the project mandate.

Mandate alignment is the process of grounding all work decisions in the project mandate and foundational documentation. It prevents scope drift and misalignment across teams by requiring binding references to core governance docs.