rule-docker-shared-foundation-docs-sync-model-decision

To keep foundation documentation synced with scope changes, you update any touched contract surface like routes or domain models and apply a synchronization rule. This automatically refreshes module and screen docs to reflect new flows.

Preventing foundation docs from drifting during API contract updates requires synchronizing endpoints_mvp_contracts.md with any code changes. A canonical rule aligns these contract changes and records roadmap deltas before merges.

You need to update scope_subscope_governance.md when touching legacy scopes marked as Partial. This ensures explicit EnvironmentType and subscope declarations are migrated into the canonical module surface.

To notify downstream teams of roadmap deltas before merging, you apply a documentation synchronization rule. It records the roadmap changes and aligns API contracts before the code is officially merged.

Yes, updating system_roadmap.md for new UI behaviors requires explicit main scope and subscope declarations. The synchronization process refreshes screen documentation to ensure these new flows are properly captured.

Foundation documentation becomes outdated because modifying repos or screens often bypasses canonical ownership policies. Applying a contract synchronization rule enforces alignment by automatically updating the related module and screen surfaces.