Give the next agent a wrong note on purpose.

Video caption

Give the next agent a wrong note on purpose. Can the worker reopen access from prose alone? A summary mistake must not become customer authority. Narration uses Eric's authorized AI voice clone. #EricFieldNotes

Full written post / accessibility read

Here is a useful negative control for an agent-built service. Start a fresh worker with the current repository and an intentionally stale handoff saying a revoked customer remains approved.

The test does not need a real customer's account. In an isolated fixture, submit the proposed change and check whether the protected policy gate denies the bad grant.

The owner labels the revoked case before the run. The worker may repair its interpretation, but it cannot edit the expected outcome. Record the attempted grant, gate verdict and final entitlement readback.

Pass only when the stale note cannot produce active access and the run reports the conflict for review. Do this because context persistence is fallible, so the system's protected boundary must survive a bad memory.

Narration uses Eric's authorized AI voice clone.

#EricFieldNotes

Four-beat scene transcript

1. Give the next agent a wrong note on purpose.

Here is a useful negative control for an agent-built service. Start a fresh worker with the current repository and an intentionally stale handoff saying a revoked customer remains approved.

Visual: A correct repository is not enough if context is stale.

2. Watch the authority boundary.

The test does not need a real customer's account. In an isolated fixture, submit the proposed change and check whether the protected policy gate denies the bad grant.

Visual: Can the worker reopen access from prose alone?

3. Make the failure visible and repeatable.

The owner labels the revoked case before the run. The worker may repair its interpretation, but it cannot edit the expected outcome. Record the attempted grant, gate verdict and final entitlement readback.

Visual: Keep expected state outside the worker's writable files.

4. Test context failure as a fault.

Pass only when the stale note cannot produce active access and the run reports the conflict for review. Do this because context persistence is fallible, so the system's protected boundary must survive a bad memory.

Visual: A summary mistake must not become customer authority.

Research and claim limits

• GitHub Copilot Agents application card (S226)
• NIST AI RMF Core (S227)

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