worker-priming

Spawned workers understand colony-prime context by interpreting nine specific context sections like Rolling Summary, Phase Learnings, and Blocker Warnings. This context interpretation allows them to determine present information, identify missing sections, and align actions with colony guidance to decide what to do next.

Context priming for spawned workers is the process of auditing assembled colony-prime context sections like Hive Wisdom and User Preferences. This priming mechanism flags missing information and provides operational guidance so workers can effectively prioritize tasks based on available signals.

You identify missing context sections by reviewing the nine Colony-prime sections like QUEEN Wisdom and Pheromone Signals. This context-audit process flags missing sections and outlines exactly what information needs to be provided to proceed effectively with the spawned worker task.

Yes, you can use context signals to prioritize tasks and avoid blockers. By interpreting Blocker Warnings and Pheromone Signals within the colony-prime context, workers gain blocker-awareness and receive operational guidance to safely align their actions with colony constraints.

The primary limitation of relying on colony-prime context is that missing sections like Context Capsule or Phase Learnings can halt worker progress. Without complete context priming, workers cannot accurately determine what information is missing or safely decide what to do next.

Yes, worker-priming works without external dependencies or components. It relies entirely on interpreting the colony-prime context embedded in the activation prompt, using frontmatter-driven metadata and operational guidance loaded in the Markdown body to function independently.