rule-docker-shared-session-lifecycle-model-decision

To automate docker session lifecycle governance, you can use a rule that anchors the active profile, enforces lifecycle transitions, and coordinates post-session review to prevent drift across docker-based environments.

A docker session lifecycle workflow logs session purpose, freezes work during instruction edits, and manages scope transitions. You need it to ensure protocol adherence and prevent drift when working across docker environments.

You enforce foundation governance by applying a session lifecycle rule that ensures governance is loaded for all routes, modules, and scopes before task implementation, anchoring the active profile first.

To resume work or handle blocked TODOs, you use a runtime-index derivation workflow to derive a derivative index before resuming the session, triggered when runtime predicates indicate blocked items.

No specific external dependencies are required to run this session lifecycle rule in docker environments, as it relies on internal workflows like Profile Selection and post-session review steps.

The best way to analyze new principles and update mandates after a docker session ends is by following dedicated post-session review steps triggered at session completion to ensure continuous protocol adherence.