Approval identity is explicit.
Approval receipts bind signer, reason, scope, source hash, room hash, and filing hash. Public approval remains gated unless the configured identity path authorizes it.
Security
Proof first. No unsupported compliance theater.
RecallOps avoids fake certifications and vague slogans. It shows identity gates, hashing, redaction, provider status, and tenant-write boundaries directly.
DETERMINISTICpacket digest
a4a2fd3565b7d625...cb02ba893f487c04Packets and receipts are digest-verifiable.
Source evidence, recall room output, filing pack, approval receipt, and final packet expose values that can be compared independently.
Tenant writes are not implied.
SAP and Oracle actions remain dry-run or gated until customer endpoints and administrative authorization are configured.
Optional AI providers are disclosed.
Partner-AI paths run behind spend controls and response hashes. Deterministic parsing remains the public proof source of truth.
Captured Band IDs, deterministic packet verification, source packet verification, SAP sandbox read verification, approval receipt hashing, ERP receiver receipts, and dry-run enterprise payloads.
Real customer ERP writes, production identity policy, tenant endpoint configuration, data-processing review, and regulator submission.
Status language
The label is part of the control.
Created against the currently deployed external service.
Recorded from an earlier real external interaction.
Reproduced locally from sealed demo data.
Payload generated but not written to a tenant.
Action requires authenticated human or admin authorization.
Demonstration-only behavior.