Module jobs_notepad 

A job’s notepad: the durable key-value state a scheduled job keeps between its runs (docs/architecture/content-spec-status.md: status, written by the agent or an operator through the harness’s own verb, never by apply).

• Read — Hermes’s own store, cron/notepad.db (cron_notepad(job_id, key, value, updated_at)), opened SQLITE_OPEN_READ_ONLY like every other observed-tier reader. A profile is a full HERMES_HOME with its own.
• Write — hermes cron notepad <job> set|delete <key> [value], then the row re-read from that store. Hermes exits 0 whatever happened and prints a sentence, so the store, not the exit code or the sentence, is the answer.

Hermes is the only harness with a job notepad at the pin. OpenClaw has none; the orchestrator’s folder has none. Both refuse.

Structs

JobNotepad

What a notepad call answered.

JobNotepadEntry

One notepad entry as the harness’s store holds it.

JobNotepadRequest

One notepad request.

Functions

delete

Remove one key through hermes cron notepad <job> delete, then re-read it.

read

Read a job’s notepad (every key, or one) from the harness’s own store.

set

Write one key through hermes cron notepad <job> set, then re-read it.