Build Notes
The architecture follows one rule: automation becomes useful only when its context, risk and result can still be reviewed later.
Alpha 0.3.0 runs the interface and API in one local process on 127.0.0.1. Workspace, goals, evidence, actions, receipts and audit live in SQLite. The browser gets a short-lived session but never the durable API token. That keeps the first reliable product path small enough to understand.
The server calculates risk from the concrete operation type and payload. The interface therefore cannot make a critical action look smaller by renaming it. A read-only check and a local draft use different contracts even when both start inside the same workspace.
An R2 approval stores the hash of the displayed payload and expires after a limited period. Changed content invalidates the earlier decision. This prevents broad approvals from being reused for another action or a different target path.
Receipts are insert-only and linked to the audit. After interruption or restart, the agent checks whether an execution is still valid. Expired or ambiguous states lose their approval. Recovery becomes part of safety rather than a manual cleanup task.
The next step is not general write access. Each external path needs its own scope, backup, restore, approval, technical post-check and receipt. Only narrow reversible changes qualify. Until then, the alpha execution remains a local draft review with externalWrites 0.
A technical decision for graduated autonomy and traceable ownership.
Founding Partner