Skip to content

kore/rpc, cterm/symbolic, proof: client_label for per-claim RPC attribution - #4923

Closed
ehildenb wants to merge 1 commit into
developfrom
kore-rpc-client-label
Closed

kore/rpc, cterm/symbolic, proof: client_label for per-claim RPC attribution#4923
ehildenb wants to merge 1 commit into
developfrom
kore-rpc-client-label

Conversation

@ehildenb

@ehildenb ehildenb commented May 29, 2026

Copy link
Copy Markdown
Member

Stamp a caller-supplied label on every outgoing JSON-RPC request id ({client_label}-NNN) so booster's per-line {request: ...} context in kore.jsonl logs map back to the originating claim. This allows syncing the log that pyk is producing for a given claim with the ones that Haskell backend is producing.

Changes:

  • kore/rpc: JsonRpcClient and KoreClient accept a client_label kwarg and expose set_client_label().
  • cterm/symbolic: KoreClientServer forwards the label to its client.
  • proof/{reachability,implies}: Prover.init_proof auto-stamps the proof id as client_label.

Validation:

  • New unit tests cover label-stamping at each layer.
  • Default client_label is str(id(self)), so existing request-id shapes are preserved byte-for-byte for non-adopters.

…bel for per-claim RPC attribution

Stamp a caller-defined label on every outgoing JSON-RPC request id
(`{client_label}-NNN`) so that booster's per-line `{request: ...}` context
in kore.jsonl can be attributed back to the originating claim/proof.

- kore/rpc.JsonRpcClient / KoreClient: accept client_label; expose set_client_label.
- cterm/symbolic.KoreClientServer: forward client_label to KoreClient.
- proof/{reachability,implies}: Prover.init_proof auto-stamps client.set_client_label(proof.id).

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
(cherry picked from commit 87b1da7852efbdf5464cdcbd89e956aea1d281cb)
@deosa-arch
deosa-arch changed the base branch from master to develop May 29, 2026 03:44
@ehildenb ehildenb closed this May 29, 2026
@ehildenb
ehildenb deleted the kore-rpc-client-label branch May 29, 2026 04:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant