Short answer: check the flag at the start of each agent decision, then emit one structured event containing the evaluated key, subject, result, and correlation identifiers. For a property-management agent, that event is more useful than a later log saying an escalation was enabled. It lets you reconstruct which behavior the agent actually saw while handling a resident message, maintenance request, or lease question.

The least complex design is a small Node.js adapter around your existing flag evaluator. Keep evaluation separate from recording. The adapter should return the boolean the agent needs and write an audit event with the same trace and request context. Do not put the flag state only in a dashboard screenshot; a dashboard can show an aggregate while an incident needs one decision from one agent run.

The event is the evidence.

What does an enabled flag prove during an incident?

It proves only what was evaluated for that subject at that moment.…