hive.note-taking

Maintain structured working notes in a persistent shared buffer that survives context pruning. Record key decisions, extracted values, and open questions incrementally at checkpoints rather than relying on full conversation history.

Working notes should contain key decisions with their rationale, intermediate results like URLs and IDs, open questions to verify, and blockers. They should not duplicate task queue data such as goals, steps, or error states already stored in the progress database.

Update notes after receiving information that changes your plan, before tool calls producing substantial output you will reference later, and when making non-obvious decisions whose reasoning would be lost if history is pruned.

The task queue tracks per-task goals, ordered steps, and SOP gates in a structured database. Working notes capture free-form context the database schema does not cover, such as decision rationale and extracted snippets.

Working notes should be updated incrementally, not rewritten from scratch each time. Incremental updates preserve accumulated context efficiently and reduce the risk of dropping earlier recorded information.