Exists now
- An independent application with its own release process.
- Reconstruction of work from agent activity.
- External testing on real sessions.
Daybook
Daybook reconstructs a readable working record from agent activity. It turns the traces a day already produced into a timeline you can inspect after the work has moved on.
The problem
The work happened. The timesheet still starts blank.
Agent-assisted work fragments a day across sessions, repositories, reviews, and small corrections. Reconstructing that record later means reopening tools and estimating where the hours went.
Daybook uses the activity already left behind to rebuild the sequence without asking for a running commentary during the work.
Intended user
People who need an honest account of an agent-heavy working day.
The useful output is a timeline that can support time reconstruction, a client record, or a personal review of what the day actually contained.
Current boundary
The application exists. External use is testing the boundary.
Testing matters more than assigning it a store position before another person has used it under pressure.
Still open
- The changes required by external testing.
- The supported public installation path.
- Whether the eventual release is paid, free, or open-core.
Availability
In testing. No public offer is listed here.
External testing is the current evidence gate. A supported download, price, or subscription promise will appear only after the useful release boundary is clear.
Public receipts
The external test report is not public yet.
Daybook is being exercised outside its own development environment. The first public receipt should state what was tested, what failed, and what changed because of it.
Writing
The work behind Daybook
Testing notes and release stories will be published on Sea Trials when they have a result worth keeping.