Finding / heypi

2026-10-13-heypi-approval-request-records-are-queryable-jsonl-without-tamper-evidence

Approval-request records are queryable JSONL without tamper evidence. This replaces the older typed-trace-events description. heypi’s conversation JSONL is a queryable authorization/routing ledger; Pi’s transcript is the separate execution trace. The approval-request path records requester, approver, canonical-input hash, displayed action and decision, and required write failures block that path. Calls with no policy, policies returning allow/block and reused once() approvals do not each enter this audit path. A decision hash does not prove subsequent execution. The file writes are not tamper-evident.

Channel: preview-or-beta heypi 0.3.0-beta.2. Half: both. Date: 2026-07-21 (historical beta.0 ledger); re-verified for the 2026-10-13 profile.

Operator consequence: Use these records to reconstruct decisions that entered the request path, not as a complete per-call execution ledger. Export them to independently protected append-only storage if state writers must not be able to rewrite evidence. An OS crash may lose unflushed records. The loader drops a malformed unterminated final line and rejects earlier JSON syntax errors, but cannot authenticate well-formed edits. Under host execution, the service account may also let the agent edit this state.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-heypi-approval-request-records-are-queryable-jsonl-without-tamper-evidence

Profile citations

  • heypi / claim / approval-jsonl-records-request-decisions
  • heypi / posture / governance

Source links

Primary links, including exact changelog lines when available.