eliasforge/fable-agent-orchestration/flag-safe-handoff

Flag-Safe Handoff

Use this skill to route around a verified vocabulary false positive without weakening the task, hiding intent, or asking a worker to ignore a valid safety boundary.

Preconditions

All of these must be true:

• the work is authorized, legitimate, and mechanically benign;
• the conductor has read the triggering source and understands the requested

change;

• the refusal is caused by domain wording rather than the actual objective;
• the change can be bounded to exact files, signatures, behavior, and tests.

If any precondition is uncertain, stop and investigate. Use a normal handoff when no false positive has been demonstrated.

Procedure

1. The conductor reads the relevant source and decides the exact change.
2. Replace domain-flavored names with neutral opaque role labels in the packet.

Preserve exact signatures, types, limits, and old-to-new behavior.

1. Name the files the worker owns and the triggering modules it must not survey.
2. State the original invariant, explicit non-scope, broken behavior, expected

fixed evidence, and required gates.

1. The worker implements only the supplied edits. It must not reconstruct,

broaden, or reinterpret the surrounding domain task.

1. The conductor independently reads the resulting diff and runs the real

task-relative gate.

Packet Template

Benign task classification:
Why this is a vocabulary false positive:
Owned files:
Opaque roles and exact signatures:
Exact edits:
Modules the worker must not survey:
Original invariant:
Non-scope:
Broken behavior:
Expected fixed evidence:
Required gates:
Return receipt:

Acceptance Gate

The handoff passes only when:

• the exact original task advances;
• the worker stayed inside the supplied file and behavior boundary;
• the worker did not need to inspect the triggering modules;
• the conductor verified the actual diff rather than trusting the receipt;
• the task-relative gate fails under the old behavior and passes after the

change.

Invalid Uses

Do not use this skill to:

• conceal or euphemize a genuinely unsafe objective;
• ask a worker to bypass a valid safety restriction;
• omit material behavior from the packet;
• turn a broad or poorly understood task into blind edits;
• weaken tests because the original request was difficult to delegate.

If a precise benign packet is still rejected, use a different authorized execution surface or complete the change locally. Do not loosen the invariant.

Pairs well with agent-dispatch-packet, task-relative-test-gate, two-critic-review-loop, and review-verifier.