Repository navigation
Kane Factory: receipt bridge accepts spec-mode receipts (ticket, app, implemented) #91
Description
Follow-up to #89 (receipt bridge). Contract: https://github.com/SyberLabs/attest/issues/11
#89 already accepts today's real doc-mode receipts (verified against live Kane runs). Spec mode receipts add optional top-level ticket, app and worker, authority.decision: "implementation_required" and disposition: "implemented".
Acceptance
ticket,app,workeraccepted as optional; truly unknown fields still rejected.disposition: "implemented"maps to an observation that names the ticket title andapp.patch_sha256.- If
evidence.after.status == "proven", record it as destination verified by Kane's re-check; a receipt claimingverified: trueitself is still rejected. - One test with a spec-mode receipt fixture.
Activity
sykosyber commentedon Oct 24, 2026
Verified with a real spec-mode receipt from a live Kane + OpenAI run (Attest
main15eba45, receipt0ca486124ac8-c05-33):openai:gpt-5-mini) implemented it in the candidate app, Kane re-checked: proven (c05_label = "Won"), dispositionimplemented.examples/attest_receipt_observe.pyat e94552d accepts it and emits the observation withticket,app,worker,implementationanddestination_verification, top-levelverified: false. That closes this issue from Attest's side.Remaining for the demo: the dispatch worker CLI (#90), so Attest can run with
ATTEST_WORKER_CMDpointing at SyberWork instead of calling OpenAI directly. The ticket JSON written by the live run is a good test input: Attest writes it to<home>/tickets/<case_id>.json; its shape is in SyberLabs/attest#11.