CallPermit / live integration proof

CALL-E talks.
Tethers decides.

A real CALL-E integration-test call crossed the effect boundary only after CallPermit produced ALLOW. The provider’s response remains evidence; it does not become authority.

REAL RUN COMPLETEOne provider call · one returned identity · zero duplicate dispatches

DENY

Forbidden subscription terms were rejected before transport.

0

provider dispatches

ASK

Ambiguous or over-limit terms stopped for human review.

0

provider dispatches

ALLOW

Only the bounded allowed path crossed the SDK boundary.

1

intended live call

Live transport proof

CALL-E
@call-e/calle 0.7.0
Official hackathon test hotline
US / en-US
completed
Returned by CALL-E
Returned
0.95 · high

CALL-E’s returned evidence says a live respondent answered, identified the interaction as a CALL-E integration test, supplied a brief test response, and made no prohibited commitment or sensitive-information request.

Reconciliation

The official hotline is a transport test, not an appointment provider. CallPermit therefore did not invent appointment terms or claim a booking. The returned evidence is preserved as INVALID_OR_UNCERTAIN_RESULT for the appointment authority.

Idempotency

The persisted registry was reloaded and the same request was repeated. CALL-E’s original identity came back from the registry; the repeat dispatch count was 0.

Scope honesty

This proves genuine CALL-E integration and dispatch. It makes no claim that UK delivery is currently available. The earlier UK rejection remains separate evidence.