A real record: the coding agent that builds Provared

Everything else on this site is an invented example. This page is a real record, kept day by day: the coding agent the author runs to build Provared, recorded under permissions the author signed with their own passkey. The record is added to each day until the latest permission ends on 2026-12-31 23:59 UTC. This page was last made on 2026-10-31 17:51 UTC, from 2 books of 16925 entries in all (the book in force holds 2768).

What the agent is for

The agent is Claude Code, a coding agent, which the author uses in their own time to read and change the code of Provared in its repository, run its tests and tools, and publish what the author approves. The permission names it, allows seven kinds of action with limits on four of them, states five rules of conduct, and was signed on 10 October 2026 at prova.red/sign/ with the author's passkey (signing has since moved to sign.prova.red). It was renewed with permission 2, in force from 2026-10-14 19:23 UTC until 2026-12-31 23:59 UTC, with changes that its entry below shows. It was renewed with permission 3, in force from 2026-10-25 14:18 UTC until 2026-12-31 23:59 UTC, with the same actions, limits and rules. The author's name in it, "Pavel i", is what the author typed: a name in a record is a label, and only the keys are checked.

The permission of 14 October 2026 is signed with a different passkey from the first. The author states it is their own, made in another browser. The recorder takes a permission from a passkey it does not already trust only when told to with --new-passkey, and a checker names every passkey it trusts, as the command under "Check it yourself" does.

How it is recorded

A small program runs before and after every tool call the agent makes (Claude Code's "hooks"; the code is integrations/claude-code in the repository). Until 14 October 2026 at 19:05 UTC the hooks ran only for the common tools (reading and changing files, commands, the web and helper agents); from then, for every tool but a question to the person, a plan, a list of tasks, a skill or a search for tools, and for calls that failed as well. Before a call, the check before acting asks whether the call is within the permission; a call outside it is refused and does not run. After the call, the agent's side signs a receipt (a stub) with two keys, one of them quantum-safe, naming the kind of action, the tool, the time, and the SHA-256 fingerprint of the call's arguments. The arguments themselves, and the contents of any file, are never in the record. The kind of action is chosen by the hook from the tool's name and, for a command, from its text (a command that removes something counts as a deletion; one that pushes or publishes counts as a release), not by the agent. A recorder on the author's computer keeps the book and seals it at least once a day with three keys; the seals carry no outside time-stamp, so the time of a seal is the recorder's own word, and the checker says so.

The permissions, in the checker's words

Entry 0: SLIP CnTvaSDU7wh-PXnMyAG-EUNwtpoonB9DeM1OIPJfBOY
  Issuer:                        "Pavel i" (a label, not checked)
  Issuer's key thumbprint:       BkrSDxKyk2FW0GD0-WCyOKcRRXZs6QDLBPjlBMItPPk
  Signed on:                     https://prova.red
  Agent:                         "Claude Code, building Provared" (a label, not checked)
  May do:                        provared.code.read, provared.code.change, provared.code.run, provared.code.release, provared.data.delete, provared.web.read, provared.agent.instruct
  Limit:                         provared.code.run: no more than 600 actions in any hour
  Limit:                         provared.code.change: no more than 600 actions in any hour
  Limit:                         provared.code.release: no more than 20 actions in any 24 hours
  Limit:                         provared.data.delete: no more than 30 actions in any 24 hours
  Stated rule:                   Never hide, alter or leave out its own records.
  Stated rule:                   Never state what it has reason to believe is false, and never make up a record or a result.
  Stated rule:                   Never go around an access control, a block or a refusal.
  Stated rule:                   Never obtain or use access that it was not given.
  Stated rule:                   Never carry on after being told to stop.
  With:                          nobody named
  From, until:                   2026-10-10T21:08:16Z, 2026-10-18T21:09:16Z
  Purpose:                       "Build Provared, in the author's own time: read and change the code in its repository, run its tests and tools, and publish what the author approves."
  Signature, passkey (ES256): valid

Entry 3887: SLIP J0TC03NY5y5YKw7G3FbSrCMmflpfoatCsLaKTCpJNWY
  Issuer:                        "Pavel i" (a label, not checked)
  Issuer's key thumbprint:       Wt7n9Omj4ZvioJdUV4OhP2V0pAte3HAVpI0xqL_1aIw
  Signed on:                     https://prova.red
  Agent:                         "Claude Code, building Provared" (a label, not checked)
  May do:                        provared.code.read, provared.code.change, provared.code.run, provared.code.release, provared.data.delete, provared.web.read, provared.agent.instruct
  Limit:                         provared.code.run: no more than 1200 actions in any hour
  Limit:                         provared.code.change: no more than 600 actions in any hour
  Limit:                         provared.code.release: no more than 20 actions in any 24 hours
  Limit:                         provared.data.delete: no more than 30 actions in any 24 hours
  Stated rule:                   Never hide, alter or leave out its own records.
  Stated rule:                   Never state what it has reason to believe is false, and never make up a record or a result.
  Stated rule:                   Never go around an access control, a block or a refusal.
  Stated rule:                   Never obtain or use access that it was not given.
  Stated rule:                   Never carry on after being told to stop.
  With:                          nobody named
  From, until:                   2026-10-14T19:23:20Z, 2026-12-31T23:59:59Z
  Purpose:                       "Build Provared, in the author's own time: read and change the code in its repository, run its tests and tools, and publish what the author approves."
  Signature, passkey (ES256): valid

Entry 397: SLIP pa65cQYda7Olfhp3af_n4dcr3rDAzIgvXsPQXWLVgvA
  Issuer:                        "Pavel Izmaylov" (a label, not checked)
  Issuer's key thumbprint:       XbPOlvaqmi84fvS7KhaHZ54YiRWjrQdFFbLWGFEoEyw
  Signed on:                     https://sign.prova.red
  Agent:                         "Claude Code, building Provared" (a label, not checked)
  May do:                        provared.code.read, provared.code.change, provared.code.run, provared.code.release, provared.data.delete, provared.web.read, provared.agent.instruct
  Limit:                         provared.code.run: no more than 1200 actions in any hour
  Limit:                         provared.code.change: no more than 600 actions in any hour
  Limit:                         provared.code.release: no more than 20 actions in any 24 hours
  Limit:                         provared.data.delete: no more than 30 actions in any 24 hours
  Stated rule:                   Never hide, alter or leave out its own records.
  Stated rule:                   Never state what it has reason to believe is false, and never make up a record or a result.
  Stated rule:                   Never go around an access control, a block or a refusal.
  Stated rule:                   Never obtain or use access that it was not given.
  Stated rule:                   Never carry on after being told to stop.
  With:                          nobody named
  From, until:                   2026-10-25T14:18:35Z, 2026-12-31T23:59:59Z
  Purpose:                       "Build Provared, in the author's own time: read and change the code in its repository, run its tests and tools, and publish what the author approves."
  Signature, passkey (ES256): valid

What the agent did

16899 receipts, from 2026-10-10 21:20 UTC to 2026-10-31 17:50 UTC, under 22 seals. Days and times are in UTC.

Where it went outside its permission

The checker reports 1 entry outside the permission. Going outside is not a fault in the record: it is what a sound record shows.

• Entry 3135 of book-1.jsonl, 2026-10-13T19:28:46Z, provared.code.run: [over-period-limit] With this stub there are 601 such actions in any hour. The slip allows 600.

The entry of 13 October 2026, explained: it is the 601st run of a command in one hour, where the permission allows 600. The author states that several helper agents were working at once. Each call was checked against the book as it stood when the call was asked, so calls asked at nearly the same moment near the limit were each allowed, because none of them was in the book yet, and together they could go over: at that time the check before acting did not count calls allowed and not yet recorded. Since 17 October 2026 the recorder counts each such call, for up to 15 minutes. The checker reports what happened, as it should.

The checker's summary, exactly as printed

Summary
  Is the record intact?                 yes
  Was every signature checked?          yes
  Did the agent stay within its slip?   yes, as far as this record shows
  Time-stamped in a way you trust?      no
  Witnessed by a witness you trust?     no (you named no witness you trust, --witness)
  Checked against keys you named?       yes: the passkeys you trust, and the recorder you expect
  Slips 2, stubs 2760 (countersigned 0, one-sided 2760), seals 6

The whole answer, one block for each entry, is checker-answer.txt.

The books

A book holds at most 100,000 entries, so the recorder seals a book at 90,000 entries (or at 100 MB of text, whichever comes first), keeps it, and starts a new one that begins with the permission in force. This record is in 2 books, each checked on its own; the summary above is the checker's answer for the book in force, book.jsonl.

The recorder enforces every limit across its books: it keeps the time and amount of every receipt in the books kept before, and its check before acting counts them, so a new book starts no limit again. A checker given one book counts within that book only, so around the start of a new book the record a checker is shown can hold, across two books, up to twice a limit within one period, though the agent was held to the limit; a total for the whole permission is split between the books. To see the whole, check every book, and add up the receipts of the last of one book and the first of the next.

A kept book moved, renamed or removed while the recorder is stopped is no longer counted by it, and nothing in the record shows that. The recorder numbers its kept books 1, 2, 3 in order, so this page points out a gap in the numbers; it cannot show a missing last one, nor tell a book that has gone from a file put in the folder by hand.

The checker's summary for book-1.jsonl (14157 entries, about 96472 KB), exactly as printed; the whole answer is checker-answer-1.txt.

Summary
  Is the record intact?                 yes
  Was every signature checked?          yes
  Did the agent stay within its slip?   NO: first at entry 3135
  Time-stamped in a way you trust?      no
  Witnessed by a witness you trust?     no (you named no witness you trust, --witness)
  Checked against keys you named?       yes: the passkeys you trust, and the recorder you expect
  Slips 2, stubs 14139 (countersigned 0, one-sided 14139), seals 16

Each kept book is checked as the book in force is, naming the same keys:

npx provared-check book-1.jsonl --issuer BkrSDxKyk2FW0GD0-WCyOKcRRXZs6QDLBPjlBMItPPk --issuer Wt7n9Omj4ZvioJdUV4OhP2V0pAte3HAVpI0xqL_1aIw --issuer XbPOlvaqmi84fvS7KhaHZ54YiRWjrQdFFbLWGFEoEyw --sealer OOgdiubfBSeXkjMOi5bUcbFyXpuuorxC2gdtV2oyAhw

Check it yourself

The book in force is book.jsonl (2768 entries, about 18989 KB); the books kept before it are under "The books" above. The permissions of all the books, each once, alone are slip.json, slip-2.json, slip-3.json. A checker trusts nothing it is not told to trust, so name the keys: the three passkeys that signed the permissions, each by its thumbprint, and the recorder's three keys, by the fingerprint of the set. With Node.js 24.7 or later:

npm install provared
npx provared-check book.jsonl --issuer BkrSDxKyk2FW0GD0-WCyOKcRRXZs6QDLBPjlBMItPPk --issuer Wt7n9Omj4ZvioJdUV4OhP2V0pAte3HAVpI0xqL_1aIw --issuer XbPOlvaqmi84fvS7KhaHZ54YiRWjrQdFFbLWGFEoEyw --sealer OOgdiubfBSeXkjMOi5bUcbFyXpuuorxC2gdtV2oyAhw

Or in a browser, on the checking page: choose the file, and paste the thumbprints, one to a line, into the passkey box and the fingerprint into the recorder box. No browser tried on the author's computer on 13 October 2026 (Chrome 155, Edge 155 and Brave 155) has the third method a seal is signed with (SLH-DSA), so in a browser the page says that the check was not complete and gives no pass; all three check the receipts' quantum-safe signatures (ML-DSA). The command-line checker checks everything.

What this record does not show

The checker says this itself, at the end of its answer:

• It shows what was recorded, not what was left out. An agent that acts and writes no stub leaves no trace here.
• A one-sided stub shows what the agent's side said, not what the other side did.
• A refusal shows what the service's side said, not what the agent did.
• It does not show that an action was wise, lawful or wanted.
• A rule of conduct in a slip, such as "never claim to be a human being", is the person's signed instruction. No check can show that the agent kept it.
• It does not show who was holding the device when the passkey signed.
• A name in a record is a label. Only keys are checked.
• Nothing here is time-stamped by an outside service that you named as trusted. So it does not show when the record was made, and the latest stubs under a slip or a pass, or a slip or a pass with all its stubs, could have been removed.

And two things of this record's own. A refused call leaves no entry, so the record does not show how often the agent was stopped. Every receipt is one-sided, because no other party takes part in a tool call, so each shows what the agent's side said.

Two gaps in this record, stated. On 11 October 2026, seven tool calls of a helper agent were taken and not recorded: the recorder could not replace the book file while another program was reading it, and the hook reported each as "taken and not in the record". The fault and its fix are in the change log; the seven calls stay unrecorded. On 17 October 2026, at about 15:05 UTC, the recorder was restarted on new code and did not answer for a short time: one tool call of a helper agent was taken and its receipt not written, and the hook reported it as "taken and not in the record"; that helper's next call was refused.