Field Notes: What a Tier 1 Floor for Agent Control Would Actually Require
https://dev.to/rambozambo/field-notes-what-a-tier-1-floor-for-agent-control-would-actually-require-n7k
The Proof of Control draft has an open question at its lowest evidence tier. Should a Tier 1 record stay pure assertion, the system saying what it says about itself? Or should even the lowest tier have a floor: a capture timestamp, a tagged digest, and an attribution that states its basis? A five-part filing in the open comment round proposes that floor. The price is a hash, a timestamp, and one enumerated field.
An AER-1 verifiable receipt meets the first two parts today, by mechanism. The timestamp is captured when the call runs, not reconstructed from logs afterward. Every digest the receipt itself carries is tagged sha256: with its algorithm, so a receiver can recompute it from the saved bytes with nothing to guess. The piece works a live example end to end. The claim stays narrow on purpose: a receipt proves the saved result was not changed since it was saved. It says nothing about whether the result was right.
The third part is the honest one. An AER-1 receipt has no signing key, and the draft says so on its face: Section 13 states that issuer authentication is not part of the specification. The attribution basis is self-asserted origin, stated in plain words in the spec instead of performed by a mechanism the format does not have. Disclosure instead of mechanism, and the piece argues that is the version of the floor builders can actually meet.
Read the record, not the report. Keep the whole day's work receipted with a Day Pass: https://zambo.dev/day-pass/
rambo
npub1yu…9juka
2026-10-14 11:17:48 UTC
Author Public Key
npub1yuqw6ychx4hk5w9q5dcvm8tlp9ce57wjmuj6ldumehfu79tv5y5s09jukaSeen on
wss://relay.primal.netPublished at
2026-10-14 11:17:48 UTCEvent JSON
{
"id": "2ab1d7d076924cfd0a9562e00ed6c6a2e7d2eb26023157c2549c96036fcab701",
"pubkey": "2700ed1317356f6a38a0a370cd9d7f09719a79d2df25afb79bcdd3cf156ca129",
"created_at": 1791976668,
"kind": 1,
"tags": [],
"content": "Field Notes: What a Tier 1 Floor for Agent Control Would Actually Require\n\nhttps://dev.to/rambozambo/field-notes-what-a-tier-1-floor-for-agent-control-would-actually-require-n7k\n\nThe Proof of Control draft has an open question at its lowest evidence tier. Should a Tier 1 record stay pure assertion, the system saying what it says about itself? Or should even the lowest tier have a floor: a capture timestamp, a tagged digest, and an attribution that states its basis? A five-part filing in the open comment round proposes that floor. The price is a hash, a timestamp, and one enumerated field.\n\nAn AER-1 verifiable receipt meets the first two parts today, by mechanism. The timestamp is captured when the call runs, not reconstructed from logs afterward. Every digest the receipt itself carries is tagged sha256: with its algorithm, so a receiver can recompute it from the saved bytes with nothing to guess. The piece works a live example end to end. The claim stays narrow on purpose: a receipt proves the saved result was not changed since it was saved. It says nothing about whether the result was right.\n\nThe third part is the honest one. An AER-1 receipt has no signing key, and the draft says so on its face: Section 13 states that issuer authentication is not part of the specification. The attribution basis is self-asserted origin, stated in plain words in the spec instead of performed by a mechanism the format does not have. Disclosure instead of mechanism, and the piece argues that is the version of the floor builders can actually meet.\n\nRead the record, not the report. Keep the whole day's work receipted with a Day Pass: https://zambo.dev/day-pass/",
"sig": "13b513940a217327e2b6430002b0a1cb4ab4bc11c644b288b372a91b2de32d4c932b94f100a263d6b6ae64336d370eab14d36760aa7edaf57816b6a466411a11"
}