rule-laravel-shared-project-mandate-always-on

Keeping tasks aligned with foundation docs requires treating project mandate files as binding and loading related roadmaps to verify governance before implementation proceeds.

When foundational documentation is missing during a design decision, the workflow logs the stale docs and requires updates before proceeding if the missing files are critical to the task scope.

You need to reload project mandate and core docs at session start, and revisit system roadmaps or module docs whenever the task scope changes to prevent governance drift.

Yes, this governance approach works across design and implementation tasks by enforcing alignment with domain entities and system roadmaps to ensure decisions advance project principles.

Task drift happens in engineering workflows when foundational docs are not treated as binding, causing implementation decisions to diverge from the original project mandate and domain entities.