Inspectable EET-1 record · 7 September 2026
One file-write run, with its evidence limits.
The execution log reports local permit verification, acquisition of a live execution commit and a completed 72-byte write. A separately collected observer record matches the target within the reported permit window.
{
"action_id": "act_1788793369608_4566b2d5",
"action_type": "write_file",
"execution_audience": "codex_local_v1",
"approved_at": "2026-09-07T15:02:49.608052Z",
"observed_at": "2026-09-07T15:02:51.958115+00:00",
"expires_at": "2026-09-07T15:03:49.608052Z",
"bytes_written": 72
}
Preview combines selected fields from the execution and observer records. The download preserves the original records and supplies an offline Python consistency checker.
Verification boundary: These are first-party records. The raw signed permit is absent, so the reported signature verification cannot be independently reproduced from this bundle. Target-and-time matching does not identify the writer or exclude another process creating the same target. The observer does not record file contents; a later supplied target copy matches the expected 72 bytes.
The original result reports Layer 3 as attributed. Our reproducible check establishes record consistency, not independent cryptographic proof of the complete execution chain. This record is not the negative-test matrix and does not establish enforcement over alternate execution paths.