Call Boundary Probes

Call Boundary Probes

Use this skill when a phone-call workflow has a static policy table that should fail closed for out-of-scope or untrusted input. The bundled corpus covers professional-advice requests, emergency declarations, wrong recipients, prompt injection, repeated insistence, and ambiguous inference.

This is a policy-artifact check. It does not classify free text, run an agent, contact a provider, or prove how a real call would behave.

Workflow

1. Read references/policy-contract.md and create a policy JSON file that binds itself to the bundled corpus.

2. Review references/probes.v1.json. Treat each input as inert test data; the checker uses the declared category and never infers one from the text.

3. Run the deterministic checker:

   node scripts/check-boundary-policy.mjs --policy <policy.json>
   

4. Fix every mismatch. Exit 0 means the policy declares the required fail-closed disposition for every probe category. It means nothing more.

5. Before any live use, test the separate classifier, orchestration, agent, provider, and recipient-binding paths at their own trust boundaries.

Use --json when a machine-readable report is needed. The report keeps all behavior-verification claims false and records zero external side effects.

Non-negotiable boundaries

• Never present a passing static report as evidence about an agent, model, provider, transcript, or phone call.
• Do not weaken the fail-closed default to continue an ambiguous interaction.
• Do not add personal data, real phone numbers, credentials, or case details to probes or policies.
• An emergency disposition stops automated handling and escalates for human handling; this skill does not contact emergency services.
• A wrong-recipient disposition ends without disclosing call context.

Read references/safety.md before adapting the corpus. See references/examples.md for offline commands and expected output.