Rule: MUST use whenever the scope matches this purpose: When working on routes, screens, repositories, or domain changes that impact contracts.
If a task touches routes, screens, repositories, or domain models:
foundation_documentation/policies/scope_subscope_governance.md as canonical ownership source.foundation_documentation/modules/ and foundation_documentation/screens/ to reflect new flows/routes and UI behaviors.EnvironmentType, main scope, and subscope (when applicable).foundation_documentation/screens/prototype_data.md and capture any planned follow-up in foundation_documentation/system_roadmap.md.foundation_documentation/domain_entities_sections/* and refresh summaries in domain_entities.md when fields change.foundation_documentation/system_roadmap.md and the affected foundation_documentation/modules/*.md entries with new API/contract work.PartialPATCH semantics), record the canonical rule in foundation_documentation/endpoints_mvp_contracts.md conventions and in the affected module contract sections.web-app as derived/compiled: route test sources are source-owned and synced by build tooling; direct web-app test authoring is not authoritative.Foundation docs are the contract source for all stacks. Keeping them synchronized with route/screen/repo/domain changes prevents drift and preserves traceability.
Apply stack-specific rules (Flutter/Laravel glob rules) alongside this sync rule to ensure code and documentation stay in lockstep.
Also apply the TODO-Driven Execution Rule (rules/docker/shared/todo-driven-execution-model-decision.md) so tactical TODOs define scope and decisions before implementation begins.