A live integrated capture ran the revoked-consent review pack through Quadro,
published the four-agent handoff to Band, then called Featherless AI and AI/ML API
as post-decision verifier lanes.
Document Set02 revoked consent
Quadro OutcomeSAY_NO
Band Events4
Partner Verifiers2 passed
Decision Packet
Quadro stopped the export because consent was revoked.
Gatestopped consent revoked
Recommendationdo not proceed without new consent
Riskhigh
Evidence items13
Input cohesionstabilized, then routed to blocker-focused review
Band publishtrue, with 4 handoff events
Partner errorsnone captured
Featherless AI Verifier
Passed
Model: Qwen/Qwen2.5-7B-Instruct
Usage: 1065 total tokens
Outcome: SAY_NO due to revoked consent.
Evidence: withdrawal note and export scope data.
Consent gate: stopped due to consent revoked.
Human next step: pause export and seek new written authorization.
AI/ML API Verifier
Passed
Model: gpt-4o-mini-2024-07-18
Usage: 656 total tokens
Outcome: export cannot proceed due to revoked consent.
Evidence: withdrawal note and privacy approval policy indicate consent was revoked.
Consent gate: route to privacy owner for written re-authorization.
Human next step: collect new written authorization before release.
Important Boundary
The partner models did not make the decision.
Quadro computed the decision first using its review chain, policy gates, consent state,
and evidence manifest. Featherless AI and AI/ML API were then used as independent
explanation lanes over the saved decision packet.
Capture Artifact
Saved integrated run
The captured run is stored in the local audit bundle as
audit/submission_demo_20260616T051948Z.json, with matching JSONL and SQLite traces.