pheromone-visibility

To make pheromone signals visible, enable visibility tracing for all operations during builds and continues. This prevents silent signaling by showing creation, reinforcement, expiration, and auto-emission events in real time.

Pheromone operations happen silently when visibility tracing is not enabled. Applying visibility controls ensures every signal change is reported as a real-time user-visible output, satisfying consistent signal-change reporting across the colony system.

Yes, you can adjust signal-change reporting verbosity for debugging. Configurable verbosity allows you to select the level of detail from compact to detailed, ensuring you capture the exact pheromone actions needed for auditing.

The best way to audit pheromone creation and expiration events is to use configurable visibility controls. They provide a clear end-of-cycle summary of all pheromone changes, ensuring consistent reporting of every signal action.

No dependencies are required to trace the auto-emission of signals in real time. The visibility controls apply directly to builds and continues across colony workflows without needing external components or modules.