context-guard

You can protect critical session context from pruning by applying a guard protocol that preserves active plans, safety files, pending operations, and user intent anchors during state compaction. This ensures planning state survives the pruning pipeline.

Context governance during state compaction works by enumerating and resolving protected items against a default pattern registry, blocking the removal of active plans and safety buffers. It ensures only safe removals occur while allowing project-specific template overrides.

To configure the guard protocol, set up and run the context guard before pruning begins. You can use the default protected-pattern registry or apply project-specific template overrides to ensure your decision logs and planning artifacts survive.

Yes, you can override the default protected-pattern registry using a template registry designed for project-specific configurations. This allows you to customize exactly which intent anchors and safety files are guarded during FlowDeck session compaction.

Over-protecting context during state compaction limits the effectiveness of the pruning pipeline by preserving unnecessary state. The guard protocol includes anti-pattern guidance to prevent over-protection and ensure only genuinely critical planning artifacts and safety buffers remain.