Skip to content

ACP: add optional ingress provenance receipts#1083

Merged
alexey-pelykh merged 1 commit intomainfrom
cherry-pick/e3df94365
Mar 12, 2026
Merged

ACP: add optional ingress provenance receipts#1083
alexey-pelykh merged 1 commit intomainfrom
cherry-pick/e3df94365

Conversation

@alexey-pelykh
Copy link
Copy Markdown

Cherry-pick of upstream openclaw/openclaw@e3df94365 (PR openclaw#40473, @mbelinky).

What: Adds optional ingress provenance receipts to ACP bridge. When enabled, the ACP translator injects systemInputProvenance metadata and/or a [Source Receipt] block into chat.send requests, allowing the gateway to track message origin for audit/security purposes. Gateway validates that only ACP bridge clients can set system provenance fields.

Adaptation: AUTO-PARTIAL — 6 conflicts resolved:

  • Import conflicts (4 files): kept fork's imports, added new provenance imports
  • chat.directive-tags.test.ts: large block of delivery routing tests (deleted in fork) discarded; only kept the 2 new provenance tests with openclawremoteclaw rebrand
  • Added lastDispatchCtx to test mockState + dispatch mock capture (needed for provenance assertions)
  • Rebranded: openclaw_acpremoteclaw_acp, bridge=openclaw-acpbridge=remoteclaw-acp, acpx openclawacpx remoteclaw, env vars OPENCLAW_*REMOTECLAW_*
  • CHANGELOG hunks discarded per fork convention

Cherry-picked-from: openclaw/openclaw@e3df94365
Part of #925

Merged via squash.

Prepared head SHA: b63e46d
Co-authored-by: mbelinky <[email protected]>
Co-authored-by: mbelinky <[email protected]>
Reviewed-by: @mbelinky
@alexey-pelykh alexey-pelykh added the cherry-pick Cherry-pick from upstream label Mar 12, 2026
@alexey-pelykh alexey-pelykh merged commit 3e16bb2 into main Mar 12, 2026
7 checks passed
@alexey-pelykh alexey-pelykh deleted the cherry-pick/e3df94365 branch March 12, 2026 03:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cherry-pick Cherry-pick from upstream

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants