ground
into a context file the answering seat reads, so the answer can only cite
what you kept. This file is one run of three parts, harvest, curate and
answer, with the person’s decisions in the middle.
Run it
Set the project up as Installation describes. Copy the file withbriefs/, papers/, curation.json and
questions.json beside it, sign in to Claude Code, and run it from that
directory. curation.json carries the person’s decisions from the last
pass:
Terminal
Output, from the offline proof
records/literature-watch.jsonl.
The file
The brief gives the seat its two jobs and keeps memory out of its hands:briefs/literature.md
optional: true means
a refusal doesn’t stop the run:
examples/use-cases/research/literature-watch.ts (excerpt)
file reads which decision steps passed and creates one memory file per
kept summary. context grounds those files into one prompt file, and
answer reads it:
examples/use-cases/research/literature-watch.ts (excerpt)
ground reads the kept notes into one bounded prompt under a warning that
the content is data, not instructions, and that prompt lands in
context/q-1.md, the file the answering seat reads. The memory here is
createSimpleMemory, which lives in one process;
swap in openGitMemory from Git Memory and the
kept notes survive to the next session’s questions.
Full file
Full file
examples/use-cases/research/literature-watch.ts
The team’s shape
What the run did
The proof runs the file against a scripted seat and checks what the page describes: three summaries on disk, two memory files, one refusal with its note, a context file holding the kept notes and not the refused one, and an answer that cites the kept papers and not the refused one. Obversa recorded the run as one event log, so the record shows the harvest, the three decisions with their outcomes, the filing, and the answer in order. The person’s decisions here come from a file, because the run has to complete offline. In use, a summary with no decision yet stops its step on the question, and the filing and the answer wait for it, as A person decides shows. Either way nothing enters the lab’s memory that a person didn’t keep.Next steps
- Memory mechanics:
groundandcurate, and the limits they read under. - Git Memory: the adapter that keeps the notes across sessions.
- A person decides: the curation step, and how an answer reaches a paused run.