Tenant-shaped recall hold payload
Gated writeIntegrations
One approved recall action, clear system boundaries.
RecallOps shows what each integration can do today, what evidence supports it, and what remains gated before any real tenant write or regulator submission.
Normalized action
Human approval comes first. System-specific actions branch after.
The same recall scope becomes SAP, Oracle, regulator, and audit artifacts without pretending every branch has the same live status.
Human-approved recall actionSAP Oracle Regulators Band
Oracle-shaped hold contract
Gated writeJurisdiction-shaped filing pack
Submission gatedAgent-room coordination proof
Captured proofIntegrationCapabilityEvidenceBoundary
CAPTUREDBand
Five-agent Band room proof is captured and labeled.The deterministic BAT-4421 packet references captured room, participant, handoff, hold, and notice IDs without presenting them as a new provider run.
capturedLIVESAP
SAP API Hub sandbox read is verified.The public proof endpoint checks the deployed sandbox path without claiming a customer tenant write.
liveDRY RUNOracle
Oracle recall-hold payload is generated from the same action.The site shows the normalized contract and keeps live tenant writes behind authorization.
No tenant writeLIVEERP receiver
Transport contract receipts are verified.RecallOps records redacted SAP and Oracle receiver receipts, separate from customer tenant authorization.
liveDRY RUNRegulator filing
Multi-jurisdiction filing packets are prepared from source evidence.CPSC, EU Safety Gate, and regional authority payloads are generated from the same source packet while live external submission stays gated.
No tenant writeGATEDHuman e-signature
Approval receipts bind the named signer to source hashes.The e-signature endpoint requires a verified approval key and seals source evidence, room run, filing pack, signature meaning, and signer identity.
Requires authorizationGATEDTenant write
Administrative authorization is required.Live writes stay disabled unless a real tenant endpoint and admin key are configured.
Requires authorizationGATEDPartner AI
Provider calls are ready behind spend controls.AI/ML API and Featherless are invoked explicitly; the proof bundle discloses used count, response hashes, and cooldown state.
Requires authorizationVerify
Inspect the receipts behind each claim.
Start with the audit packet for the full proof chain, or open the live SAP sandbox and enterprise dry-run endpoints directly.