Made the navigation collapse below the mobile breakpoint and preserved keyboard focus when the menu closes.
- Commit proof recorded
- Focused tests passed
- Desktop and 390px screenshots attached
- Independent review job resolved
WatchTower resolutions
An agent saying “done” is not a receipt.
WatchTower closes work with a resolution: what changed, the commit or explicit no-code proof, and the tests, screenshots, or review evidence the job required.
Evidence requirements follow the job. A documentation task and a UI change should not produce the same receipt.
Confidence versus evidence
Completion needs a shared definition.
A fluent summary is useful. It is not enough to close durable work.
QuestionSelf-reportReceipt
What changed?“Implemented successfully.”Bounded resolution summary.
Where is it?May be implied.Commit or explicit no-code proof.
Was it checked?“Looks good.”Named tests, screenshots, or review evidence.
Can another agent continue?Requires transcript archaeology.Resolution lives with the durable job.
Illustrative receipt
The last event should be useful tomorrow.
This public-safe example shows the shape of a resolution. It is illustrative, not a claim that a browser visitor ran an agent.
Four parts of a useful resolution
Proof without ceremony.
State the material change
A bounded explanation of what the worker changed, decided, or discovered.
Point to the work
A commit when code changed, or explicit no-code proof when the outcome is research, review, or configuration.
Name the evidence
Tests, browser checks, screenshots, or review findings selected for the job rather than added mechanically.
Preserve the handoff
The initiating agent can see dependencies, interventions, and the final resolution without reconstructing another transcript.
Do not optimize for agents running
Optimize for work returning with proof.
See Captain turn one request into durable jobs, verification, and a receipt back in the original session.