Scout files. Clerk only acts on what is on record.
An operational desk for incoming work. Scout monitors configured sources and records inbound asks into durable memory. Clerk verifies filed records and executes operator-confirmed actions.
When autonomous systems pass instructions through prompt buffers or conversational logs, context drifts and models hallucinate details that never existed in storage. Irreversible actions are taken on assumed premises rather than verified facts.
Tasks exist only in conversational context. The executing agent acts on transient text tokens with no durable audit trail and no verified entity records.
Inbound work is filed into persistent storage before execution is evaluated. If an entity was never filed into memory, Clerk flags it as not on record and halts execution.
Monitors operator-specified repositories and wallet addresses. When inbound asks are discovered, Scout writes person and request records into storage.
Scout has no signing authority, cannot execute transactions, and cannot mutate action decisions.
A live backlog projected directly from storage. Tasks appear as Scout files them and clear automatically once Clerk completes an action.
The queue maintains no secondary mutable tables. If memory partitions are reset, the queue reflects the change immediately.
Inspects filed records, verifies entity identities against memory, and applies explicit status stamps:
Proposes onchain transactions only when a verified wallet address exists, requiring explicit operator confirmation before broadcast.
The operator configures the GitHub repositories or Base wallet addresses to monitor. If no sources are specified, Scout remains idle.
Scout processes sources, identifies incoming asks, and records structured person and ask files into durable memory.
Clerk reads pending tasks directly from storage. If an entity is queried that was never filed, Clerk returns a verified not on record status.
For tasks with a bound wallet address, Clerk prepares the transaction. The transaction broadcasts to Base only upon operator confirmation.
Unfiled entities are never presumed on record
Sources are defined at runtime with no hardcoded seed data
Queue state and recall depend entirely on persistent memory
OnRecord provides structured role separation for incoming work. Rather than allowing a single agent to observe, decide, and execute autonomously in one prompt, the desk splits discovery from action across isolated memory partitions.
The system operates without preloaded fixtures, sample profiles, or mock transactions. All records originate from live operator sources.
The runtime configuration of repositories and wallet addresses monitored by Scout. If the Scene is empty, Scout files no tasks and the queue remains empty.
Clerk queries the memory partition for the requested entity. If the record does not exist in storage, Clerk stamps the request as not on record and refuses execution.
No. Scout is strictly limited to reading sources and filing records. It possesses no private keys and cannot sign transactions.
When an ask originates from a verified wallet source, Clerk can propose an onchain transaction on Base. Broadcast occurs only after the operator checks confirmation.
No. OnRecord ships with empty data templates. All records, tasks, and addresses are supplied directly by the operator at runtime.
Open OnRecord and configure your own repository or wallet source.
Open desk