Group IPC Snapshots

Required Read

• Before protecting projection mounts, selecting native floating scheduling or writing or consuming group/task projections, accepted native dispatch metadata or cancellation results, including reminder prechecks and watcher readers, read skills/host-contracts/references/group-ipc-snapshots.md in full.
• Its full text and named sections bind as rule content. Missing or unreadable content stops the affected action until the plugin is repaired.
• Read explicitly when triggered; never @-import the reference.

Boundary

• Host registration and IPC source establish scope. Only the fixed host producer and actual host dispatch supply projection, capability, occurrence and dispatch metadata; caller input, inherited environment and copied source supply no provenance.
• Protect projection data against consuming-container writes through every alias before capability selection or effect readback.
• Keep only existing canonical outgoing and own-session input surfaces writable.
• Preserve visibility and repair isolation.
• Projections, capability declarations and dispatch metadata grant no identity, role, owner approval, write, migration, send, delivery or effect authority. Native capability metadata does not attest an arbitrary agent executable or replace the verified reader-first rollout.
• Require supported versions and fresh exact operation bindings. Never invent missing context, create a probe task for capability proof, convert retained reminder gates or replay an uncertain effect or cancellation.