One evidence card can beat a giant prompt.

Video caption

One evidence card can beat a giant prompt.

A vague warning only moves confusion downstream.

Trigger, claim, citation, expiry, action, acknowledgement.

A role agent can alert; a policy owner still decides.

#EricFieldNotes

Full written post / accessibility read

Teams try to solve agent memory by stuffing every incident, policy and design note into every prompt. That increases cost and distraction. A specialist agent can hold its own durable memory and inject one relevant, sourced exception when the worker reaches the decision.

Imagine an auth change that affects a tenant with an immediate-revocation contract. 'Be careful with tenants' is useless. The worker needs the exact constraint, where it came from, who owns it, and the test that would fail if the patch violates it.

When a revocation diff appears, the security role sends a small packet: affected tenant, source contract, policy owner, freshness date and required denial probe. The supervisor records that the implementing agent accepted the packet and links the test result.

Use specialist agents to deliver verified context early. Keep the business rule under a named owner and the acceptance test in a protected harness. Do this because proactive memory is useful only when its source, relevance and effect can be challenged.

#EricFieldNotes

Four-beat scene transcript

1. One evidence card can beat a giant prompt.

Teams try to solve agent memory by stuffing every incident, policy and design note into every prompt. That increases cost and distraction. A specialist agent can hold its own durable memory and inject one relevant, sourced exception when the worker reaches the decision.

Visual: The worker needs the constraint at the right moment.

2. The card must be actionable.

Imagine an auth change that affects a tenant with an immediate-revocation contract. 'Be careful with tenants' is useless. The worker needs the exact constraint, where it came from, who owns it, and the test that would fail if the patch violates it.

Visual: A vague warning only moves confusion downstream.

3. Design the handoff packet.

When a revocation diff appears, the security role sends a small packet: affected tenant, source contract, policy owner, freshness date and required denial probe. The supervisor records that the implementing agent accepted the packet and links the test result.

Visual: Trigger, claim, citation, expiry, action, acknowledgement.

4. Inject facts, not authority.

Use specialist agents to deliver verified context early. Keep the business rule under a named owner and the acceptance test in a protected harness. Do this because proactive memory is useful only when its source, relevance and effect can be challenged.

Visual: A role agent can alert; a policy owner still decides.

Research and claim limits

• OpenAI Agents SDK sessions (S53)
• LangGraph persistence (S54)

The examples identified as illustrative or simulated are design probes, not reported incidents. Vendor specifications do not establish workload performance.