myanvoos

Labs are about to have agents doing real work — planning assays, calling compute, triaging data, ordering supplies. But a lab record only counts if it's attributable and tamper-evident; that's the entire job of an ELN, and increasingly a regulatory expectation. If agents act through a bolted-on copilot, their work is either invisible to the record or stranded in a system no auditor trusts. Daybook's bet is that the notebook itself should be the agent's native multi-player workspace, with the same integrity guarantees applied to machine and human work alike. With Daybook, the agent operates the same notebook a scientist does, through the same set of actions. The integration surface is an MCP server with 98 tools that map one-to-one onto what a person can do in the UI — draft and sign an experiment, launch and stream a compute run, record a measurement, draw down inventory, link entities, search, request review. No model runs inside the app; the connecting client (Claude Code, Claude Science, or a scheduled background agent) supplies the reasoning. Every write, whether it comes from a human click, a REST call, or an agent's tool call, passes through one shared operation layer and lands as an append-only, hash-chained audit record that names the actor — human, agent, or automation — along with the MCP client and the model behind it.