DOZER

Public provenance

Claims with
ways back.

61 concise receipts. Each opens to exact current proof and specification correspondence; none asks you to read a 29,000-pixel ledger by default.

A real request. A supervised run.

Ask an agent. Play together.

From a request in Dozer Home to one NES emulator, a shared display and two independent phone controllers. This worked example includes the original prompt, actual supervision, recorded play and reproduction notes.

Recorded on a Linux desktop with one display emulator and two Android phone emulators, joined directly over Iroh. Controller touches were driven by the supervising operator.

Read the behavioral receipt →

  1. 01 · Original submitted request

    Read the request that started it

    Read the request that started it. The first three paragraphs of the original submitted request, retrieved from Home history. Read the full exact request below.
    The first three paragraphs of the original submitted request, retrieved from Home history. Read the full exact request below. desktop · desktop-window · desktop-x11 View evidence

  2. 02 · Real agent progress

    Keep the handoff visible

    Keep the handoff visible. Home tool progress and the supervising operator’s handoff instruction, captured during the actual run.
    Home tool progress and the supervising operator’s handoff instruction, captured during the actual run. desktop · desktop-window · desktop-x11 View evidence

  3. 03 · Supervision and notes

    Supervise the working project

    Supervise the working project. The project agent updates its notes after supervised Stop, rejoin and teardown checks. The source capture shows reported checks; the recording and retained observations supply the play evidence.
    The project agent updates its notes after supervised Stop, rejoin and teardown checks. The source capture shows reported checks; the recording and retained observations supply the play evidence. desktop · desktop-window · desktop-x11 View evidence

  4. 04 · Display emulator

    One emulator on the shared display

    One emulator on the shared display. Super Tilt Bro runs in one JSNES instance. Both phone emulators control distinct player ports in this same game.
    Super Tilt Bro runs in one JSNES instance. Both phone emulators control distinct player ports in this same game. android · android-television · android-device View evidence

  5. 05 · Player one phone emulator

    Hold direction and action together

    Hold direction and action together. Player one’s landscape touch controls support simultaneous direction and action, release, and local Stop.
    Player one’s landscape touch controls support simultaneous direction and action, release, and local Stop. android · android-phone-landscape · android-device View evidence

  6. 06 · Player two phone emulator

    Give the other phone its own player

    Give the other phone its own player. Player two has its own accepted role and held controls. Both phones were exercised independently and concurrently.
    Player two has its own accepted role and held controls. Both phones were exercised independently and concurrently. android · android-phone-landscape · android-device View evidence

Watch the actual run

75 continuous seconds of play, recorded at about 20 frames per second. Both player inputs were tested independently and together. Stop cleared held input in about three seconds; rejoining kept the player role and returned the game to its title screen. This recording does not show a completed round.

Read the exact request · Reproduce the setup and controls

claim/continuity

Leave a session running and return to its project context from another Dozer client.

Open complete receipt 2 proofs · 5 spec links

Proof

  • journey frameReturn to a running sessionframe/work-sessions
  • focused testSession history and project-owned active inventory are restored from the machine.proof/session-continuity

Specification correspondence

  • capability/session/historyCurrent schema v1 specification identity
  • requirement/session/concurrent/background-sessions-keep-workingCurrent schema v1 specification identity
  • requirement/session/history/clients-of-one-machine-converge-on-one-session-catalogCurrent schema v1 specification identity
  • requirement/session/history/a-session-loads-back-with-its-historyCurrent schema v1 specification identity
  • requirement/workspace/projects/active-session-inventory-is-project-ownedCurrent schema v1 specification identity

claim/machine

Choose one base machine and see its machine-owned work converge across clients.

Open complete receipt 2 proofs · 3 spec links

Proof

  • journey frameStart from the selected machineframe/machine-overview
  • focused testClients converge on the selected machine's session catalogue.proof/machine-convergence

Specification correspondence

  • capability/machine/base-machine-selectionCurrent schema v1 specification identity
  • requirement/machine/ownership-boundary/every-machine-owned-surface-uses-the-selected-machineCurrent schema v1 specification identity
  • requirement/session/history/clients-of-one-machine-converge-on-one-session-catalogCurrent schema v1 specification identity

claim/presentation

Present an application deliberately to an authorized surface without turning that transport into the product API.

Open complete receipt 2 proofs · 2 spec links

Proof

  • journey framePresent an application deliberatelyframe/machine-hosted
  • protocol guaranteePresentation intent and inventory cross a typed, independently versioned machine protocol.proof/presentation-contract

Specification correspondence

  • requirement/remote/presentation-surfaces/a-receiver-exposes-a-surface-deliberatelyCurrent schema v1 specification identity
  • requirement/remote/presentation-surfaces/surface-inventory-and-presentation-intent-are-machine-ownedCurrent schema v1 specification identity

claim/navigation

Move through projects, sessions, machines, and settings with one native hierarchy.

Open complete receipt 2 proofs · 2 spec links

Proof

  • journey frameSettings opens on Profileframe/settings-overview
  • focused testThe reachable navigation graph and declared hierarchy are checked exhaustively.proof/navigation-closure

Specification correspondence

  • requirement/shell/navigation-ia/back-up-addresses-and-restoration-share-the-declared-hierarchyCurrent schema v1 specification identity
  • requirement/shell/navigation-ia/the-shell-receives-one-typed-navigation-treeCurrent schema v1 specification identity

automation.cli-control

Inspect and control product state from a command line

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • capability/machine/controlCurrent schema v1 specification identity

automation.event-subscriptions

Subscribe programmatically to product and agent lifecycle events

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • capability/observe/traceCurrent schema v1 specification identity

automation.socket-api

Control a running instance through a structured local API

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • capability/machine/controlCurrent schema v1 specification identity

extensions.agent-hooks

Connect supported coding agents through official lifecycle integrations

Open complete receipt 1 proofs · 44 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • requirement/agent/pi/a-blocking-dialog-is-answered-or-refused-never-ignoredCurrent schema v1 specification identity
  • requirement/agent/pi/a-bot-bound-to-a-memory-profile-opens-its-one-ongoing-chatCurrent schema v1 specification identity
  • requirement/agent/pi/a-bound-chat-offers-no-fork-or-duplicateCurrent schema v1 specification identity
  • requirement/agent/pi/a-bound-chat-reports-memory-instead-of-compactionCurrent schema v1 specification identity
  • requirement/agent/pi/a-compaction-is-reported-by-what-came-of-itCurrent schema v1 specification identity
  • requirement/agent/pi/a-machine-signed-in-after-it-started-can-answerCurrent schema v1 specification identity
  • requirement/agent/pi/a-person-can-compact-a-chat-or-stop-a-retryCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-chat-knows-its-projectCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-chat-s-cost-and-fullness-are-shownCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-session-is-told-what-dozer-isCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-that-dies-ends-its-turnCurrent schema v1 specification identity
  • requirement/agent/pi/a-profile-held-by-one-chat-is-refused-to-another-by-nameCurrent schema v1 specification identity
  • requirement/agent/pi/a-profile-s-remembering-models-are-written-not-defaultedCurrent schema v1 specification identity
  • requirement/agent/pi/a-prompt-pi-absorbs-ends-its-deliveryCurrent schema v1 specification identity
  • requirement/agent/pi/a-recorded-turn-replays-faithfullyCurrent schema v1 specification identity
  • requirement/agent/pi/a-request-that-goes-unanswered-gives-up-and-says-soCurrent schema v1 specification identity
  • requirement/agent/pi/a-stopped-agent-is-reported-with-what-it-saidCurrent schema v1 specification identity
  • requirement/agent/pi/a-task-s-pi-run-keeps-its-session-where-the-machine-owns-itCurrent schema v1 specification identity
  • requirement/agent/pi/a-tool-call-keeps-the-name-of-what-it-touchedCurrent schema v1 specification identity
  • requirement/agent/pi/a-tool-result-reaches-a-client-boundedCurrent schema v1 specification identity
  • requirement/agent/pi/a-turn-ends-when-pi-has-settled-not-when-a-run-finishesCurrent schema v1 specification identity
  • requirement/agent/pi/an-image-is-not-read-as-textCurrent schema v1 specification identity
  • requirement/agent/pi/dozer-knows-which-pi-it-is-talking-toCurrent schema v1 specification identity
  • requirement/agent/pi/extension-artifact-namespaces-do-not-obstruct-canonical-pi-historyCurrent schema v1 specification identity
  • requirement/agent/pi/new-user-turns-preserve-ongoing-optchat-child-work-and-turn-isolationCurrent schema v1 specification identity
  • requirement/agent/pi/nothing-is-inventedCurrent schema v1 specification identity
  • requirement/agent/pi/optchat-subagents-run-one-level-deep-and-report-in-the-transcriptCurrent schema v1 specification identity
  • requirement/agent/pi/pi-asks-before-it-runs-a-tool-dozer-gatesCurrent schema v1 specification identity
  • requirement/agent/pi/pi-is-the-agent-every-machine-runsCurrent schema v1 specification identity
  • requirement/agent/pi/retrying-and-compacting-are-shown-rather-than-hiddenCurrent schema v1 specification identity
  • requirement/agent/pi/sessions-can-be-listed-and-loaded-backCurrent schema v1 specification identity
  • requirement/agent/pi/signing-in-tells-every-surface-the-agent-can-now-answerCurrent schema v1 specification identity
  • requirement/agent/pi/steering-a-running-turn-is-not-sent-as-a-new-promptCurrent schema v1 specification identity
  • requirement/agent/pi/the-commands-pi-offers-are-in-the-composerCurrent schema v1 specification identity
  • requirement/agent/pi/the-launch-line-asks-for-nothing-it-was-not-givenCurrent schema v1 specification identity
  • requirement/agent/pi/the-model-in-use-is-the-one-pi-is-usingCurrent schema v1 specification identity
  • requirement/agent/pi/the-protocol-tolerates-what-it-does-not-modelCurrent schema v1 specification identity
  • requirement/agent/pi/the-supervisor-declares-itself-and-refuses-by-nameCurrent schema v1 specification identity
  • requirement/agent/pi/the-time-to-a-reply-s-first-event-is-measuredCurrent schema v1 specification identity
  • requirement/agent/pi/the-transcript-carries-only-what-belongs-in-itCurrent schema v1 specification identity
  • requirement/agent/pi/tool-calls-keep-their-identityCurrent schema v1 specification identity
  • requirement/agent/pi/tool-output-too-large-for-the-context-is-kept-out-of-itCurrent schema v1 specification identity
  • requirement/agent/pi/turns-are-reported-honestlyCurrent schema v1 specification identity
  • requirement/agent/pi/what-a-pi-extension-says-is-shown-rather-than-droppedCurrent schema v1 specification identity

extensions.plugin-runtime

Install third-party behavior into a documented product extension runtime

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • capability/platform/native-extensionsCurrent schema v1 specification identity

remote.host-access

Operate agent work running on another machine

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • requirement/remote/iroh-bridge/a-real-connection-authenticates-before-it-reads-anythingCurrent schema v1 specification identity

sharing.multi-user

Give another person separately authorized access to selected work

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testTyped bridge and core tests prove remote connections, supported adapters, and extension boundaries.proof/connections-and-extensions

Specification correspondence

  • capability/remote/guest-channelCurrent schema v1 specification identity

messaging.huddle-video

Share a screen or a camera into a huddle, machine to machine

Open complete receipt 1 proofs · 8 spec links

Proof

  • focused testReal-machine huddle signal, authorization and refusal of unauthorized media, against an explicitly selected disposable relay.proof/huddle-signal-between-machines

Specification correspondence

  • requirement/machine/live-media/a-device-encodes-with-the-silicon-it-hasCurrent schema v1 specification identity
  • requirement/machine/live-media/a-live-source-is-a-stream-not-a-sequence-of-stillsCurrent schema v1 specification identity
  • requirement/machine/live-media/a-stream-says-which-codec-it-is-and-a-receiver-decodes-it-or-says-why-notCurrent schema v1 specification identity
  • requirement/machine/live-media/a-watcher-can-tell-a-still-source-from-a-stopped-oneCurrent schema v1 specification identity
  • requirement/machine/live-media/carrying-a-stream-does-not-require-being-able-to-encode-oneCurrent schema v1 specification identity
  • requirement/machine/live-media/decoding-uses-hardware-where-the-platform-offers-itCurrent schema v1 specification identity
  • requirement/machine/live-media/encoded-frames-are-bounded-by-what-the-room-can-affordCurrent schema v1 specification identity

messaging.relay

Run the relay your channels live on, on your own machine

Open complete receipt 1 proofs · 22 spec links

Proof

  • focused testThe nostr client, its wire format and the channel operations run against a real Buzz relay this task stands up.proof/channels-on-a-real-relay

Specification correspondence

  • requirement/message/relay/a-fixture-standing-in-for-the-receiver-applies-the-receiver-s-ruleCurrent schema v1 specification identity
  • requirement/message/relay/a-git-request-against-the-relay-carries-a-credential-for-itselfCurrent schema v1 specification identity
  • requirement/message/relay/a-lease-cannot-ask-to-be-woken-for-somebody-elseCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-can-carry-another-machine-s-channelsCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-executes-the-leases-it-holdsCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-hosts-the-relay-it-serves-channels-fromCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-keeps-the-relay-it-hosts-runningCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-may-host-a-relay-and-hosting-one-grants-nothingCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-reports-what-hosting-a-relay-requiresCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-s-room-identity-persists-and-is-replaceableCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-says-what-leases-it-holds-and-what-it-has-queuedCurrent schema v1 specification identity
  • requirement/message/relay/a-machine-that-cannot-carry-channels-says-soCurrent schema v1 specification identity
  • requirement/message/relay/a-member-can-announce-a-repository-the-relay-hostsCurrent schema v1 specification identity
  • requirement/message/relay/a-member-can-ask-to-be-woken-without-disclosing-what-forCurrent schema v1 specification identity
  • requirement/message/relay/a-relay-s-object-store-shall-provide-compare-and-swapCurrent schema v1 specification identity
  • requirement/message/relay/a-scoped-read-proves-completeness-not-non-emptinessCurrent schema v1 specification identity
  • requirement/message/relay/a-watcher-picks-up-a-channel-made-after-it-connectedCurrent schema v1 specification identity
  • requirement/message/relay/an-undeliverable-wake-expires-rather-than-accumulatingCurrent schema v1 specification identity
  • requirement/message/relay/execution-cannot-widen-what-construction-narrowedCurrent schema v1 specification identity
  • requirement/message/relay/starting-a-relay-waits-for-it-to-serve-not-for-its-portCurrent schema v1 specification identity
  • requirement/message/relay/the-machine-s-channels-are-proven-against-the-relay-it-hostsCurrent schema v1 specification identity
  • requirement/message/relay/the-relay-s-dependency-floor-is-recorded-not-assumedCurrent schema v1 specification identity

security.isolated-work

Keep simultaneous tasks from changing one another's files and process state

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testFocused machine tests prove isolated task workspaces and durable parent-child delegation.proof/safe-delegation

Specification correspondence

  • capability/workspace/task-workspacesCurrent schema v1 specification identity

security.permission-decisions

Review and answer agent tool or execution permission requests

Open complete receipt 2 proofs · 2 spec links

Proof

  • focused testFocused machine tests prove isolated task workspaces and durable parent-child delegation.proof/safe-delegation
  • journey frameAnswer the decision from Androidframe/supervise-permission

Specification correspondence

  • requirement/agent/permissions/the-agent-s-own-options-are-offered-verbatimCurrent schema v1 specification identity
  • requirement/agent/permissions/every-request-is-identifiableCurrent schema v1 specification identity

security.secret-boundary

Keep credentials and remote authority inside a documented trust boundary

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testFocused machine tests prove isolated task workspaces and durable parent-child delegation.proof/safe-delegation

Specification correspondence

  • capability/agent/credentialsCurrent schema v1 specification identity

workspace.hierarchy

Organize active work into durable nested workspace, screen, pane, or window structures

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testFocused machine tests prove isolated task workspaces and durable parent-child delegation.proof/safe-delegation

Specification correspondence

  • capability/workspace/foldersCurrent schema v1 specification identity

workspace.multiple-projects

Keep and switch among several configured projects

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testFocused machine tests prove isolated task workspaces and durable parent-child delegation.proof/safe-delegation

Specification correspondence

  • requirement/workspace/projects/project-creation-and-inventory-run-on-the-machineCurrent schema v1 specification identity

workspace.worktree-isolation

Create or manage a separate repository worktree for a task

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testFocused machine tests prove isolated task workspaces and durable parent-child delegation.proof/safe-delegation
  • journey frameReview isolated delegated workframe/supervise-task

Specification correspondence

  • capability/workspace/task-workspacesCurrent schema v1 specification identity

automation.channel-workflows

Configure a workflow a channel can run, and watch it advance

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testThe nostr client, its wire format and the channel operations run against a real Buzz relay this task stands up.proof/channels-on-a-real-relay

Specification correspondence

  • capability/machine/channel-workflowsCurrent schema v1 specification identity

accessibility.semantic-ui

Use the primary interface with platform accessibility semantics and scalable text

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments

Specification correspondence

  • capability/shell/accessibilityCurrent schema v1 specification identity

appearance.themes

Adapt the interface's colors and appearance

Open complete receipt 1 proofs · 25 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments

Specification correspondence

  • requirement/shell/appearance/a-derived-variant-is-reproducible-legible-and-correctableCurrent schema v1 specification identity
  • requirement/shell/appearance/a-placeholder-is-text-and-clears-text-contrastCurrent schema v1 specification identity
  • requirement/shell/appearance/a-resolved-theme-becomes-a-deterministic-watch-appearanceCurrent schema v1 specification identity
  • requirement/shell/appearance/a-status-tone-never-resolves-through-a-theme-s-accent-rolesCurrent schema v1 specification identity
  • requirement/shell/appearance/a-theme-choice-demonstrates-the-appearance-it-will-applyCurrent schema v1 specification identity
  • requirement/shell/appearance/a-theme-may-carry-wallpapersCurrent schema v1 specification identity
  • requirement/shell/appearance/an-identity-colour-keeps-its-hue-and-solves-its-tone-per-schemeCurrent schema v1 specification identity
  • requirement/shell/appearance/an-omarchy-theme-family-has-an-authoritative-default-and-both-modesCurrent schema v1 specification identity
  • requirement/shell/appearance/app-settings-never-counteract-system-accessibilityCurrent schema v1 specification identity
  • requirement/shell/appearance/appearance-leads-with-a-theme-switcher-and-an-accent-is-a-mode-of-its-ownCurrent schema v1 specification identity
  • requirement/shell/appearance/appearance-says-when-the-backdrop-is-standing-downCurrent schema v1 specification identity
  • requirement/shell/appearance/authored-counterparts-merge-before-a-missing-mode-is-derivedCurrent schema v1 specification identity
  • requirement/shell/appearance/bad-preference-data-degrades-safelyCurrent schema v1 specification identity
  • requirement/shell/appearance/components-consume-the-resolved-appearance-rolesCurrent schema v1 specification identity
  • requirement/shell/appearance/dozer-s-own-themes-stay-reachableCurrent schema v1 specification identity
  • requirement/shell/appearance/editable-fields-use-an-opaque-expressive-treatmentCurrent schema v1 specification identity
  • requirement/shell/appearance/every-theme-stays-legibleCurrent schema v1 specification identity
  • requirement/shell/appearance/existing-palette-selections-survive-the-family-migrationCurrent schema v1 specification identity
  • requirement/shell/appearance/geist-is-dozer-s-interface-fontCurrent schema v1 specification identity
  • requirement/shell/appearance/graphite-is-a-bundled-theme-beside-dozer-s-ownCurrent schema v1 specification identity
  • requirement/shell/appearance/preferences-survive-reload-and-stay-scopedCurrent schema v1 specification identity
  • requirement/shell/appearance/selection-is-a-container-not-a-ringCurrent schema v1 specification identity
  • requirement/shell/appearance/status-meaning-is-consistent-across-shellsCurrent schema v1 specification identity
  • requirement/shell/appearance/the-backdrop-is-the-norm-and-the-reading-plane-is-arguedCurrent schema v1 specification identity
  • requirement/shell/appearance/type-is-a-role-scale-that-holds-for-every-interface-fontCurrent schema v1 specification identity

browser.embedded

Open a real web browser surface alongside active work

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments

Specification correspondence

  • capability/site/project-sitesCurrent schema v1 specification identity

input.keyboard-mouse

Operate the primary interface with keyboard and pointing input

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments

Specification correspondence

  • capability/shell/accessibilityCurrent schema v1 specification identity

presentation.declarative-gadgets

Let agents present declared interactive documents or application surfaces

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments
  • journey frameUse the application surface the agent preparedframe/supervise-gadget

Specification correspondence

  • capability/gadget/declarative-documentsCurrent schema v1 specification identity

terminal.interactive

Run fully interactive terminal processes inside the product

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments
  • journey frameInspect the full running environmentframe/supervise-terminal

Specification correspondence

  • capability/platform/terminalCurrent schema v1 specification identity

terminal.restore-layout

Restore terminal workspace structure after application restart

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments

Specification correspondence

  • capability/workspace/foldersCurrent schema v1 specification identity

terminal.split-panes

Arrange simultaneous terminal or browser surfaces in split panes

Open complete receipt 1 proofs · 61 spec links

Proof

  • focused testHost-rendered native-shell evidence covers project, terminal, presentation, and navigation states.proof/project-environments

Specification correspondence

  • requirement/shell/chat-surface/a-chat-loading-from-its-machine-shows-the-transcript-s-shapeCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-chat-s-own-actions-are-in-its-headerCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-chat-that-cannot-answer-offers-the-way-outCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-chat-whose-provider-is-signed-out-says-so-at-the-composerCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-decision-that-needs-the-person-is-one-card-in-the-composer-s-placeCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-draft-is-never-lostCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-draft-outlives-interruption-of-its-editorCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-draft-survives-the-chat-it-was-typed-into-being-createdCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-finished-turn-leaves-no-starting-receipt-behindCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-fresh-draft-has-one-initial-owner-and-no-conflictCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-message-s-hover-actions-take-no-room-in-the-transcriptCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-permission-card-offers-what-the-agent-asked-and-takes-one-answerCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-prompt-can-name-what-the-machine-already-holdsCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-question-an-extension-asks-is-a-decision-in-the-transcriptCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-reference-that-no-longer-resolves-refuses-the-sendCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-room-s-card-follows-the-request-that-made-itCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-screen-action-shows-what-the-agent-saw-and-didCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-send-the-machine-refuses-keeps-the-message-and-says-whyCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-settled-decision-sits-beside-the-message-that-raised-itCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-surface-waiting-on-nothing-says-soCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-terminal-session-can-grant-an-agent-s-environment-permissionCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-terminal-surface-answers-touchCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-terminal-surface-carries-every-key-to-the-processCurrent schema v1 specification identity
  • requirement/shell/chat-surface/a-terminal-surface-says-which-of-three-states-it-is-inCurrent schema v1 specification identity
  • requirement/shell/chat-surface/agent-forms-and-failures-preserve-contextCurrent schema v1 specification identity
  • requirement/shell/chat-surface/an-unreachable-machine-is-said-once-with-what-is-still-true-and-what-to-doCurrent schema v1 specification identity
  • requirement/shell/chat-surface/attention-remains-reachable-across-session-and-window-selectionCurrent schema v1 specification identity
  • requirement/shell/chat-surface/canonical-agent-histories-load-on-first-useCurrent schema v1 specification identity
  • requirement/shell/chat-surface/convene-editors-retain-scoped-input-until-exact-send-acceptanceCurrent schema v1 specification identity
  • requirement/shell/chat-surface/conversation-controls-stay-subordinate-to-reading-and-respondingCurrent schema v1 specification identity
  • requirement/shell/chat-surface/conversation-handoffs-name-both-bots-and-the-shared-workCurrent schema v1 specification identity
  • requirement/shell/chat-surface/decision-previews-identify-the-exact-work-they-authorizeCurrent schema v1 specification identity
  • requirement/shell/chat-surface/draft-save-failures-and-attachment-availability-are-honestCurrent schema v1 specification identity
  • requirement/shell/chat-surface/home-coordination-uses-the-normal-conversation-surfaceCurrent schema v1 specification identity
  • requirement/shell/chat-surface/multiplexed-windows-keep-working-independentlyCurrent schema v1 specification identity
  • requirement/shell/chat-surface/opening-and-dismissing-the-keyboard-is-layout-workCurrent schema v1 specification identity
  • requirement/shell/chat-surface/pre-session-draft-handoff-happens-exactly-onceCurrent schema v1 specification identity
  • requirement/shell/chat-surface/project-sessions-group-typed-live-windowsCurrent schema v1 specification identity
  • requirement/shell/chat-surface/queued-messages-are-chips-above-the-composerCurrent schema v1 specification identity
  • requirement/shell/chat-surface/queued-work-attachments-and-permissions-are-distinctCurrent schema v1 specification identity
  • requirement/shell/chat-surface/queues-and-permissions-use-deliberate-state-presentationCurrent schema v1 specification identity
  • requirement/shell/chat-surface/running-state-and-context-use-are-honestCurrent schema v1 specification identity
  • requirement/shell/chat-surface/saved-drafts-are-device-local-and-authority-scopedCurrent schema v1 specification identity
  • requirement/shell/chat-surface/settled-decisions-do-not-crowd-out-the-conversationCurrent schema v1 specification identity
  • requirement/shell/chat-surface/something-that-happened-in-a-chat-is-a-note-in-that-chatCurrent schema v1 specification identity
  • requirement/shell/chat-surface/startup-catalog-recovery-keeps-saved-chats-reachableCurrent schema v1 specification identity
  • requirement/shell/chat-surface/steering-is-typing-while-the-turn-is-goingCurrent schema v1 specification identity
  • requirement/shell/chat-surface/streaming-does-not-disturb-stable-surface-geometryCurrent schema v1 specification identity
  • requirement/shell/chat-surface/tail-following-has-one-conditional-ownerCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-composer-holds-what-a-running-turn-cannot-take-yetCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-composer-is-one-opaque-unitCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-first-enabled-send-consumes-the-restored-draftCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-keyboard-is-raised-once-per-requestCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-model-line-carries-the-chat-s-cost-and-fullness-quietlyCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-palette-finds-what-was-meant-and-keeps-its-placeCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-reading-position-outlives-leaving-the-chatCurrent schema v1 specification identity
  • requirement/shell/chat-surface/the-transcript-is-monotonic-and-identity-stableCurrent schema v1 specification identity
  • requirement/shell/chat-surface/transcript-and-composer-form-one-readable-edge-to-edge-surfaceCurrent schema v1 specification identity
  • requirement/shell/chat-surface/useful-results-retain-their-owner-and-freshnessCurrent schema v1 specification identity
  • requirement/shell/chat-surface/waiting-delivery-says-why-and-offers-what-unblocks-itCurrent schema v1 specification identity
  • requirement/shell/chat-surface/window-and-session-lifecycle-are-separate-actionsCurrent schema v1 specification identity

experience.multi-device-orchestration

Describe one shared experience and let Dozer arrange its project, television display, and two phone controllers

Open complete receipt 19 proofs · 8 spec links

Proof

  • journey frameStart from a focused Home dashboardframe/room-dashboard
  • journey frameAsk the app-level agent from its own Home sessionframe/room-home-session
  • journey frameSee project creation and handoff progressframe/room-progress
  • journey frameLet each receiver decide locallyframe/room-participation
  • journey frameOpen the completed handoffframe/room-ready
  • journey frameLand in the project that owns the workframe/room-project
  • journey frameShow the shared state across the roomframe/room-display
  • journey frameGive player one large local controlsframe/room-controller-one
  • journey frameKeep an identical phone in a distinct player roleframe/room-controller-two
  • journey frameKeep the remaining roles useful after one phone disconnectsframe/room-degraded
  • journey frameRecover the same participant and shared stateframe/room-recovered
  • focused testReal workerd and machine services prove shared revisions across display and controllers, current-state late join, identity-preserving recovery, restart reconciliation, and owned close.proof/multi-device-room-behavior
  • maintained exampleA reviewed live run on Dozer Dev: one display emulator and two phone emulators played one shared two-player game, each phone driving only the role it was assigned.proof/supervised-worked-game-example
  • journey frameRead the request that started itframe/worked-game-request
  • journey frameKeep the handoff visibleframe/worked-game-agent-progress
  • journey frameSupervise the working projectframe/worked-game-supervision
  • journey frameOne emulator on the shared displayframe/worked-game-display
  • journey frameHold direction and action togetherframe/worked-game-player-one
  • journey frameGive the other phone its own playerframe/worked-game-player-two

Specification correspondence

  • requirement/session/home/home-sessions-are-ordinary-sessionsCurrent schema v1 specification identity
  • requirement/session/home/cross-project-work-leaves-home-through-an-explicit-handoffCurrent schema v1 specification identity
  • requirement/agent/environment-control/project-agents-assemble-owned-multi-device-rooms-through-typed-actionsCurrent schema v1 specification identity
  • requirement/gadget/multi-device-rooms/a-room-binds-one-gadget-instance-to-named-participant-rolesCurrent schema v1 specification identity
  • requirement/gadget/multi-device-rooms/roles-and-profiles-reduce-one-shared-gadget-stateCurrent schema v1 specification identity
  • requirement/gadget/multi-device-rooms/a-room-recovers-and-closes-as-an-owned-composite-resourceCurrent schema v1 specification identity
  • requirement/remote/presentation-surfaces/a-device-accepts-a-project-and-role-participation-request-locallyCurrent schema v1 specification identity

repository.channel-forge

Work on a repository from the channel that talks about it

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testThe nostr client, its wire format and the channel operations run against a real Buzz relay this task stands up.proof/channels-on-a-real-relay

Specification correspondence

  • capability/workspace/channel-forgeCurrent schema v1 specification identity

repository.branch-context

See repository, branch, and working-directory context for active work

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity

Specification correspondence

  • requirement/workspace/projects/a-project-belongs-to-a-placeCurrent schema v1 specification identity

session.attachments

Attach files or images as durable agent context

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity

Specification correspondence

  • capability/session/attachmentsCurrent schema v1 specification identity

session.history

Browse and search durable past agent sessions

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity

Specification correspondence

  • capability/session/historyCurrent schema v1 specification identity

session.memory

Carry curated memory or instructions across sessions

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity

Specification correspondence

  • capability/agent/memoryCurrent schema v1 specification identity

session.process-continuity

Detach every interactive client while owned terminal processes keep running

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity
  • focused testSession history and project-owned active inventory are restored from the machine.proof/session-continuity

Specification correspondence

  • capability/session/concurrentCurrent schema v1 specification identity

session.resume-agent

Resume a recognized agent conversation after restart

Open complete receipt 1 proofs · 44 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity

Specification correspondence

  • requirement/agent/pi/a-blocking-dialog-is-answered-or-refused-never-ignoredCurrent schema v1 specification identity
  • requirement/agent/pi/a-bot-bound-to-a-memory-profile-opens-its-one-ongoing-chatCurrent schema v1 specification identity
  • requirement/agent/pi/a-bound-chat-offers-no-fork-or-duplicateCurrent schema v1 specification identity
  • requirement/agent/pi/a-bound-chat-reports-memory-instead-of-compactionCurrent schema v1 specification identity
  • requirement/agent/pi/a-compaction-is-reported-by-what-came-of-itCurrent schema v1 specification identity
  • requirement/agent/pi/a-machine-signed-in-after-it-started-can-answerCurrent schema v1 specification identity
  • requirement/agent/pi/a-person-can-compact-a-chat-or-stop-a-retryCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-chat-knows-its-projectCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-chat-s-cost-and-fullness-are-shownCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-session-is-told-what-dozer-isCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-that-dies-ends-its-turnCurrent schema v1 specification identity
  • requirement/agent/pi/a-profile-held-by-one-chat-is-refused-to-another-by-nameCurrent schema v1 specification identity
  • requirement/agent/pi/a-profile-s-remembering-models-are-written-not-defaultedCurrent schema v1 specification identity
  • requirement/agent/pi/a-prompt-pi-absorbs-ends-its-deliveryCurrent schema v1 specification identity
  • requirement/agent/pi/a-recorded-turn-replays-faithfullyCurrent schema v1 specification identity
  • requirement/agent/pi/a-request-that-goes-unanswered-gives-up-and-says-soCurrent schema v1 specification identity
  • requirement/agent/pi/a-stopped-agent-is-reported-with-what-it-saidCurrent schema v1 specification identity
  • requirement/agent/pi/a-task-s-pi-run-keeps-its-session-where-the-machine-owns-itCurrent schema v1 specification identity
  • requirement/agent/pi/a-tool-call-keeps-the-name-of-what-it-touchedCurrent schema v1 specification identity
  • requirement/agent/pi/a-tool-result-reaches-a-client-boundedCurrent schema v1 specification identity
  • requirement/agent/pi/a-turn-ends-when-pi-has-settled-not-when-a-run-finishesCurrent schema v1 specification identity
  • requirement/agent/pi/an-image-is-not-read-as-textCurrent schema v1 specification identity
  • requirement/agent/pi/dozer-knows-which-pi-it-is-talking-toCurrent schema v1 specification identity
  • requirement/agent/pi/extension-artifact-namespaces-do-not-obstruct-canonical-pi-historyCurrent schema v1 specification identity
  • requirement/agent/pi/new-user-turns-preserve-ongoing-optchat-child-work-and-turn-isolationCurrent schema v1 specification identity
  • requirement/agent/pi/nothing-is-inventedCurrent schema v1 specification identity
  • requirement/agent/pi/optchat-subagents-run-one-level-deep-and-report-in-the-transcriptCurrent schema v1 specification identity
  • requirement/agent/pi/pi-asks-before-it-runs-a-tool-dozer-gatesCurrent schema v1 specification identity
  • requirement/agent/pi/pi-is-the-agent-every-machine-runsCurrent schema v1 specification identity
  • requirement/agent/pi/retrying-and-compacting-are-shown-rather-than-hiddenCurrent schema v1 specification identity
  • requirement/agent/pi/sessions-can-be-listed-and-loaded-backCurrent schema v1 specification identity
  • requirement/agent/pi/signing-in-tells-every-surface-the-agent-can-now-answerCurrent schema v1 specification identity
  • requirement/agent/pi/steering-a-running-turn-is-not-sent-as-a-new-promptCurrent schema v1 specification identity
  • requirement/agent/pi/the-commands-pi-offers-are-in-the-composerCurrent schema v1 specification identity
  • requirement/agent/pi/the-launch-line-asks-for-nothing-it-was-not-givenCurrent schema v1 specification identity
  • requirement/agent/pi/the-model-in-use-is-the-one-pi-is-usingCurrent schema v1 specification identity
  • requirement/agent/pi/the-protocol-tolerates-what-it-does-not-modelCurrent schema v1 specification identity
  • requirement/agent/pi/the-supervisor-declares-itself-and-refuses-by-nameCurrent schema v1 specification identity
  • requirement/agent/pi/the-time-to-a-reply-s-first-event-is-measuredCurrent schema v1 specification identity
  • requirement/agent/pi/the-transcript-carries-only-what-belongs-in-itCurrent schema v1 specification identity
  • requirement/agent/pi/tool-calls-keep-their-identityCurrent schema v1 specification identity
  • requirement/agent/pi/tool-output-too-large-for-the-context-is-kept-out-of-itCurrent schema v1 specification identity
  • requirement/agent/pi/turns-are-reported-honestlyCurrent schema v1 specification identity
  • requirement/agent/pi/what-a-pi-extension-says-is-shown-rather-than-droppedCurrent schema v1 specification identity

session.transcript

Read a structured conversation transcript outside terminal scrollback

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testMachine tests prove durable sessions, project context, attachments, memory, and reconnection.proof/context-continuity

Specification correspondence

  • capability/session/transcript-markdownCurrent schema v1 specification identity

observability.diagnostics

Inspect logs, traces, or health evidence when the product misbehaves

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost lifecycle tests prove process continuity, replacement, recovery, and bounded diagnostics.proof/recovery

Specification correspondence

  • capability/observe/observation-logCurrent schema v1 specification identity

packaging.self-update

Install supported builds and receive product updates

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost lifecycle tests prove process continuity, replacement, recovery, and bounded diagnostics.proof/recovery

Specification correspondence

  • requirement/platform/packaging-ci/release-artifacts-are-self-contained-and-upgrade-safelyCurrent schema v1 specification identity

platforms.cross-platform-client

Use a first-party client on more than one desktop operating system

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost lifecycle tests prove process continuity, replacement, recovery, and bounded diagnostics.proof/recovery

Specification correspondence

  • capability/platform/core-shell-bridgeCurrent schema v1 specification identity

recovery.live-handoff

Replace a running server version while its terminal processes continue

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testHost lifecycle tests prove process continuity, replacement, recovery, and bounded diagnostics.proof/recovery

Specification correspondence

  • capability/machine/supervisorCurrent schema v1 specification identity

recovery.reconnect

Reconnect to running work without losing its authoritative state

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testHost lifecycle tests prove process continuity, replacement, recovery, and bounded diagnostics.proof/recovery
  • journey frameReturn to the same session contextframe/supervise-return

Specification correspondence

  • capability/machine/connectionCurrent schema v1 specification identity

agents.concurrent

Run and monitor several agent sessions at the same time

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision
  • journey frameStart a supported agent in its projectframe/supervise-start

Specification correspondence

  • capability/session/concurrentCurrent schema v1 specification identity

agents.coordination

Coordinate work or messages among agents

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision

Specification correspondence

  • capability/workspace/task-workspacesCurrent schema v1 specification identity

agents.detect-state

Recognize whether an agent is working, blocked, idle, or done

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision

Specification correspondence

  • capability/session/statusCurrent schema v1 specification identity

agents.request-attention

Find the agent session that needs a human decision

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision
  • journey frameSee which session needs youframe/supervise-attention

Specification correspondence

  • capability/session/statusCurrent schema v1 specification identity

mobile.companion

Monitor or continue agent work from a phone or wearable

Open complete receipt 2 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision
  • journey frameAnswer the decision from Androidframe/supervise-permission

Specification correspondence

  • requirement/remote/mobile-supervisor/remembered-machines-survive-being-added-to-and-switched-betweenCurrent schema v1 specification identity

navigation.active-work

Move directly among active projects, sessions, and attention items

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision

Specification correspondence

  • requirement/shell/navigation-ia/leading-navigation-prioritizes-work-in-the-current-scopeCurrent schema v1 specification identity

notifications.system

Receive a system notification when background work needs attention or completes

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testThe shared core and bridge contracts prove agent state, attention, permissions, and client convergence.proof/agent-supervision

Specification correspondence

  • capability/platform/notificationsCurrent schema v1 specification identity

messaging.channels

Talk in a channel with the people and agents who are in it

Open complete receipt 4 proofs · 34 spec links

Proof

  • journey frameAsk the agent in the channelframe/channel-conversation
  • journey frameSee the channels you are inframe/channel-list
  • journey frameFollow one threadframe/channel-thread
  • focused testThe nostr client, its wire format and the channel operations run against a real Buzz relay this task stands up.proof/channels-on-a-real-relay

Specification correspondence

  • requirement/shell/channel-surface/a-bot-s-reply-shows-its-work-the-way-a-chat-s-turn-doesCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-channel-can-be-shared-from-where-it-is-read-and-joined-from-the-listCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-channel-s-header-says-how-many-people-and-bots-are-in-itCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-channel-shows-member-avatars-in-messages-and-the-rosterCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-message-with-a-thread-says-so-under-itCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-person-can-pull-the-channel-list-to-read-it-againCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-person-can-read-a-channel-and-say-something-in-itCurrent schema v1 specification identity
  • requirement/shell/channel-surface/a-person-can-see-the-channels-they-are-inCurrent schema v1 specification identity
  • requirement/shell/channel-surface/an-open-conversation-follows-the-member-the-machine-signs-asCurrent schema v1 specification identity
  • requirement/shell/channel-surface/channel-creation-and-collaboration-remain-discoverable-in-scopeCurrent schema v1 specification identity
  • requirement/shell/channel-surface/channel-image-attachments-render-inline-over-the-relay-http-proxyCurrent schema v1 specification identity
  • requirement/shell/channel-surface/channel-messages-are-legible-over-the-backdropCurrent schema v1 specification identity
  • requirement/shell/channel-surface/conversation-drafts-survive-leaving-their-viewCurrent schema v1 specification identity
  • requirement/shell/channel-surface/conversation-failures-preserve-context-and-offer-the-relevant-recoveryCurrent schema v1 specification identity
  • requirement/shell/channel-surface/no-channel-surface-offers-to-refresh-machine-owned-stateCurrent schema v1 specification identity
  • requirement/shell/channel-surface/tapping-a-member-s-avatar-opens-their-profile-cardCurrent schema v1 specification identity
  • requirement/shell/channel-surface/the-channel-composer-attaches-a-picture-or-a-videoCurrent schema v1 specification identity
  • requirement/shell/channel-surface/the-channel-composer-is-readable-and-keyboard-safeCurrent schema v1 specification identity
  • requirement/shell/channel-surface/the-member-card-shows-presence-and-status-and-can-start-a-direct-messageCurrent schema v1 specification identity
  • requirement/shell/channel-surface/under-a-thread-the-channel-keeps-its-composer-collapsedCurrent schema v1 specification identity
  • requirement/message/channels/a-channel-a-person-is-watching-stays-currentCurrent schema v1 specification identity
  • requirement/message/channels/a-channel-belongs-to-a-project-or-to-nothingCurrent schema v1 specification identity
  • requirement/message/channels/a-channel-carries-messages-between-its-members-and-only-themCurrent schema v1 specification identity
  • requirement/message/channels/a-channel-shows-who-is-present-and-who-is-typingCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-mark-a-channel-unreadCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-mark-everything-read-at-onceCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-reach-their-channels-from-the-appCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-react-to-and-delete-messagesCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-say-something-in-a-channel-from-a-deviceCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-search-the-messages-they-may-readCurrent schema v1 specification identity
  • requirement/message/channels/a-member-s-read-position-follows-them-between-devicesCurrent schema v1 specification identity
  • requirement/message/channels/a-person-can-make-a-channel-and-add-members-to-itCurrent schema v1 specification identity
  • requirement/message/channels/a-reply-belongs-to-its-thread-on-the-relay-s-termsCurrent schema v1 specification identity
  • requirement/message/channels/opening-a-channel-reads-a-page-not-its-historyCurrent schema v1 specification identity

messaging.direct

Say something to one person, kept apart from the channels

Open complete receipt 1 proofs · 3 spec links

Proof

  • focused testThe nostr client, its wire format and the channel operations run against a real Buzz relay this task stands up.proof/channels-on-a-real-relay

Specification correspondence

  • requirement/message/channels/a-direct-message-is-named-by-who-is-in-itCurrent schema v1 specification identity
  • requirement/message/channels/a-member-can-say-something-to-one-personCurrent schema v1 specification identity
  • requirement/message/channels/direct-messages-are-kept-apart-from-channelsCurrent schema v1 specification identity

messaging.social

Post, follow, reply and read long-form on your machine's own relay

Open complete receipt 4 proofs · 6 spec links

Proof

  • journey frameWrite one, with a picture on itframe/feed-composing
  • journey frameOpen a note to its conversationframe/feed-conversation
  • journey frameRead what is posted hereframe/feed-open
  • focused testPosting, replying, quoting, following, searching and attaching are exercised against a relay the test stands up, and read back as the member that published them.proof/the-feed-on-a-real-relay

Specification correspondence

  • requirement/message/social/the-feed-is-a-screen-in-the-appCurrent schema v1 specification identity
  • requirement/message/social/a-note-opens-to-its-conversationCurrent schema v1 specification identity
  • requirement/message/social/passing-a-note-along-names-itCurrent schema v1 specification identity
  • requirement/message/social/the-surface-offers-what-this-relay-answers-and-says-what-it-does-notCurrent schema v1 specification identity
  • requirement/message/social/a-note-carries-media-and-the-device-never-dials-the-relayCurrent schema v1 specification identity
  • requirement/message/social/one-signing-policy-for-everything-the-feed-publishesCurrent schema v1 specification identity

messaging.agents-in-channels

Put an agent in a channel and address it like anyone else

Open complete receipt 2 proofs · 5 spec links

Proof

  • journey frameAsk the agent in the channelframe/channel-conversation
  • focused testThe nostr client, its wire format and the channel operations run against a real Buzz relay this task stands up.proof/channels-on-a-real-relay

Specification correspondence

  • requirement/message/channels/a-message-addressed-to-an-agent-becomes-its-turnCurrent schema v1 specification identity
  • requirement/message/channels/a-person-can-put-a-library-agent-in-a-channel-or-a-direct-messageCurrent schema v1 specification identity
  • requirement/message/channels/an-agent-carries-a-separate-conversation-per-channelCurrent schema v1 specification identity
  • requirement/message/channels/an-agent-is-a-member-of-a-channel-like-anyone-elseCurrent schema v1 specification identity
  • requirement/message/channels/an-agent-s-reply-is-published-under-its-own-identityCurrent schema v1 specification identity

bots.persistent

Keep several bots, each with its own name, purpose and continuing conversation

Open complete receipt 2 proofs · 3 spec links

Proof

  • journey frameAdd a bot with its own purposeframe/bots-add
  • focused testMachine tests prove each bot keeps a distinct machine-owned identity, its own continuing conversation, and explicit group context.proof/persistent-bots

Specification correspondence

  • requirement/agent/persistent-bots/persistent-bots-have-distinct-machine-owned-identitiesCurrent schema v1 specification identity
  • requirement/agent/persistent-bots/a-bot-carries-its-own-conversation-and-admitted-contextCurrent schema v1 specification identity
  • requirement/shell/navigation-ia/bots-is-a-primary-destination-with-its-own-continuing-navigationCurrent schema v1 specification identity

bots.convene

Convene bots into a group and choose exactly what context they share

Open complete receipt 1 proofs · 3 spec links

Proof

  • focused testMachine tests prove each bot keeps a distinct machine-owned identity, its own continuing conversation, and explicit group context.proof/persistent-bots

Specification correspondence

  • requirement/agent/persistent-bots/convene-selects-continuing-bots-before-creating-their-groupCurrent schema v1 specification identity
  • requirement/agent/persistent-bots/bringing-private-context-into-a-group-is-explicitCurrent schema v1 specification identity
  • requirement/agent/persistent-bots/collaboration-preserves-bot-identity-and-work-ownershipCurrent schema v1 specification identity

bots.browser-sign-in

Sign in to any website yourself in your bots' browser, then hand control back

Open complete receipt 4 proofs · 3 spec links

Proof

  • journey frameSign in while only you control itframe/bots-browser-private
  • journey frameHand control backframe/bots-browser-returned
  • journey frameOpen the bot's computerframe/bots-computer
  • focused testMachine tests prove human sign-in fences every agent screen path, control returns only under a new epoch, and the browser profile outlives a disconnect.proof/bots-share-a-browser

Specification correspondence

  • requirement/machine/agent-browser/human-website-sign-in-has-explicit-exclusive-ownershipCurrent schema v1 specification identity
  • requirement/machine/agent-browser/the-machine-owns-a-durable-admitted-browser-resourceCurrent schema v1 specification identity
  • requirement/agent/screen-control/browser-takeover-fences-every-agent-screen-pathCurrent schema v1 specification identity

bots.screen-approval

Approve each turn a bot may see or use a screen

Open complete receipt 1 proofs · 2 spec links

Proof

  • focused testMachine tests prove human sign-in fences every agent screen path, control returns only under a new epoch, and the browser profile outlives a disconnect.proof/bots-share-a-browser

Specification correspondence

  • requirement/agent/screen-control/every-screen-call-is-bounded-by-a-leaseCurrent schema v1 specification identity
  • requirement/agent/screen-control/a-screen-action-is-a-visible-outcome-in-the-conversationCurrent schema v1 specification identity

bots.vm-desktop

Give a bot a full desktop on one of your VMs, bound to the exact target you approved

Open complete receipt 1 proofs · 2 spec links

Proof

  • focused testMachine tests prove human sign-in fences every agent screen path, control returns only under a new epoch, and the browser profile outlives a disconnect.proof/bots-share-a-browser

Specification correspondence

  • requirement/agent/screen-control/bot-desktop-access-retains-an-exact-admitted-targetCurrent schema v1 specification identity
  • requirement/machine/agent-browser/desktop-entry-rechecks-its-exact-reviewed-member-endpointCurrent schema v1 specification identity

bots.share-output

Preview what a bot wrote and share it explicitly

Open complete receipt 1 proofs · 1 spec links

Proof

  • focused testMachine tests prove each bot keeps a distinct machine-owned identity, its own continuing conversation, and explicit group context.proof/persistent-bots

Specification correspondence

  • requirement/agent/persistent-bots/a-newly-written-bot-output-can-be-previewed-and-explicitly-sharedCurrent schema v1 specification identity

integration/pi

Run Pi-backed agent sessions while Dozer owns the durable project, session, and native-client experience around them.

Open complete receipt 1 proofs · 44 spec links

Proof

  • focused testFocused adapter tests establish the supported Pi relationship.proof/provider-adapters

Specification correspondence

  • requirement/agent/pi/a-blocking-dialog-is-answered-or-refused-never-ignoredCurrent schema v1 specification identity
  • requirement/agent/pi/a-bot-bound-to-a-memory-profile-opens-its-one-ongoing-chatCurrent schema v1 specification identity
  • requirement/agent/pi/a-bound-chat-offers-no-fork-or-duplicateCurrent schema v1 specification identity
  • requirement/agent/pi/a-bound-chat-reports-memory-instead-of-compactionCurrent schema v1 specification identity
  • requirement/agent/pi/a-compaction-is-reported-by-what-came-of-itCurrent schema v1 specification identity
  • requirement/agent/pi/a-machine-signed-in-after-it-started-can-answerCurrent schema v1 specification identity
  • requirement/agent/pi/a-person-can-compact-a-chat-or-stop-a-retryCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-chat-knows-its-projectCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-chat-s-cost-and-fullness-are-shownCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-session-is-told-what-dozer-isCurrent schema v1 specification identity
  • requirement/agent/pi/a-pi-that-dies-ends-its-turnCurrent schema v1 specification identity
  • requirement/agent/pi/a-profile-held-by-one-chat-is-refused-to-another-by-nameCurrent schema v1 specification identity
  • requirement/agent/pi/a-profile-s-remembering-models-are-written-not-defaultedCurrent schema v1 specification identity
  • requirement/agent/pi/a-prompt-pi-absorbs-ends-its-deliveryCurrent schema v1 specification identity
  • requirement/agent/pi/a-recorded-turn-replays-faithfullyCurrent schema v1 specification identity
  • requirement/agent/pi/a-request-that-goes-unanswered-gives-up-and-says-soCurrent schema v1 specification identity
  • requirement/agent/pi/a-stopped-agent-is-reported-with-what-it-saidCurrent schema v1 specification identity
  • requirement/agent/pi/a-task-s-pi-run-keeps-its-session-where-the-machine-owns-itCurrent schema v1 specification identity
  • requirement/agent/pi/a-tool-call-keeps-the-name-of-what-it-touchedCurrent schema v1 specification identity
  • requirement/agent/pi/a-tool-result-reaches-a-client-boundedCurrent schema v1 specification identity
  • requirement/agent/pi/a-turn-ends-when-pi-has-settled-not-when-a-run-finishesCurrent schema v1 specification identity
  • requirement/agent/pi/an-image-is-not-read-as-textCurrent schema v1 specification identity
  • requirement/agent/pi/dozer-knows-which-pi-it-is-talking-toCurrent schema v1 specification identity
  • requirement/agent/pi/extension-artifact-namespaces-do-not-obstruct-canonical-pi-historyCurrent schema v1 specification identity
  • requirement/agent/pi/new-user-turns-preserve-ongoing-optchat-child-work-and-turn-isolationCurrent schema v1 specification identity
  • requirement/agent/pi/nothing-is-inventedCurrent schema v1 specification identity
  • requirement/agent/pi/optchat-subagents-run-one-level-deep-and-report-in-the-transcriptCurrent schema v1 specification identity
  • requirement/agent/pi/pi-asks-before-it-runs-a-tool-dozer-gatesCurrent schema v1 specification identity
  • requirement/agent/pi/pi-is-the-agent-every-machine-runsCurrent schema v1 specification identity
  • requirement/agent/pi/retrying-and-compacting-are-shown-rather-than-hiddenCurrent schema v1 specification identity
  • requirement/agent/pi/sessions-can-be-listed-and-loaded-backCurrent schema v1 specification identity
  • requirement/agent/pi/signing-in-tells-every-surface-the-agent-can-now-answerCurrent schema v1 specification identity
  • requirement/agent/pi/steering-a-running-turn-is-not-sent-as-a-new-promptCurrent schema v1 specification identity
  • requirement/agent/pi/the-commands-pi-offers-are-in-the-composerCurrent schema v1 specification identity
  • requirement/agent/pi/the-launch-line-asks-for-nothing-it-was-not-givenCurrent schema v1 specification identity
  • requirement/agent/pi/the-model-in-use-is-the-one-pi-is-usingCurrent schema v1 specification identity
  • requirement/agent/pi/the-protocol-tolerates-what-it-does-not-modelCurrent schema v1 specification identity
  • requirement/agent/pi/the-supervisor-declares-itself-and-refuses-by-nameCurrent schema v1 specification identity
  • requirement/agent/pi/the-time-to-a-reply-s-first-event-is-measuredCurrent schema v1 specification identity
  • requirement/agent/pi/the-transcript-carries-only-what-belongs-in-itCurrent schema v1 specification identity
  • requirement/agent/pi/tool-calls-keep-their-identityCurrent schema v1 specification identity
  • requirement/agent/pi/tool-output-too-large-for-the-context-is-kept-out-of-itCurrent schema v1 specification identity
  • requirement/agent/pi/turns-are-reported-honestlyCurrent schema v1 specification identity
  • requirement/agent/pi/what-a-pi-extension-says-is-shown-rather-than-droppedCurrent schema v1 specification identity

Product capture

Selected product capture
Full-size approved product evidence.