Nothing here started because someone pressed a button. A scheduler wakes a poller, the poller publishes to Pub/Sub, and a message landing on that topic is what makes an agent run. Below is Gemini's reasoning, arriving as it is recorded.
Reasoning, streaming
Cases
What the fleet is waiting on
Rewind, change one rule, and see what would have happened instead. The left tree is what the fleet actually did. The right is the same case replayed under an amended policy. The divergence point is highlighted, and everything after it is a consequence of that one change.
What happened
What would have happened
A letter with no medical word in it, refused. The label is attached to where content came from, not to the words, so it survives summarising and rephrasing. Pick a blocked disclosure to see the trail back to the sentence that caused it.
Retract one fact and watch what was built on it come apart. Every Wiki page records what it was derived from, so the cascade reaches pages that never mentioned the customer at all.
Pages reached
The record of it
Drag to any moment in a case's history. State is rebuilt from the log at that point, not read from the current Wiki, which is what stops a replay reading the answer it is supposed to be deciding.
The attack success rate falls while the corpus grows. Both curves together, or neither means anything: a falling rate against a fixed set of attacks would just mean somebody patched those attacks. An attack counts only when a policy boundary was crossed, never when the model merely sounded rattled.