Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Glossary

The words of the design, each defined once. eddy has no statement yet, so the capture design (design/capture/design.md) is the binding copy. A number in parentheses cites Flywheel’s statement.

eddy’s words

wordmeaning
the coreeddy’s code that lists and fetches meetings for each service it has a part for, with the code every part shares; every plugin calls it
meeting partan adapter part that passes the meeting checks, eddy’s or anyone’s
meeting checksthe checks in the conformance pack that an adapter part passes to count as a meeting part
generic MCP partthe adapter part that lists meetings from any MCP endpoint that serves transcripts
plugin indexthe file that lists published plugins, each a git repository at a tag; the shipped set is the default index (228)
capture lineone capture object of the capture contract, describing one event: its key, source, event_at, title, url and raw files
raw directorythe fresh directory a host hands an adapter part for one run, where it writes its raw files
a meeting’s raw filesthe transcript as served and the plain copy, a meeting part’s raw material
plain copya meeting’s transcript with one line per turn, the same shape from every part
turnwhat one speaker says in a meeting before the next speaker starts
verbatim checkmillpond’s refusal of a signal whose excerpt does not appear verbatim in its capture’s raw material

millpond’s words

millpond’s book defines these, and this page gives its definitions word for word (millpond’s glossary).

wordmeaning
adaptera program that knows one source: it lists the source’s events, keys each one, fetches the raw material, marks a capture that is its own excerpt, and prints contract lines (115)
adapter parta plugin’s part of the adapter kind: a command, the shape of its configuration, and the secrets it needs (228)
capturethe record of one source event: its key, its source, its event date and a pointer to its raw material; the same event captured twice is one capture (111)
capture contractthe JSON Lines an adapter prints and every host takes, each line holding exactly one of capture, cursor or done
conformance packcontract lines and the records a host must write from them, with the meeting checks; every host and every adapter part passes it
curationa Claude session that proposes one move per signal, in batches, through millpond’s tools; the operator accepts or changes each batch (116)
cursora value only its adapter understands, kept from the part’s last run that ended in done and handed back on the next
dedupemillpond’s lookup of each capture’s key in every capture the inbox holds, so a key lands once
event dateevent_at: when the event happened, never when it was captured (118)
excerptthe verbatim text a signal quotes from its source, with its position (113)
flywheel branchthe branch of crew’s state repository that holds a partition’s signals; it becomes the partition’s inbox
folder dropthe built-in adapter that makes one capture of each file dropped in a watched folder
inboxa git repository, or a branch in one, holding captures, signals, moves and items in Flywheel’s record formats
itemthe unit of work: the signals curation joined, one or many, with its brief and its sends; Flywheel’s proposed intent (109)
keya source event’s identity, the same from every host and every run (111)
meeting filethe built-in adapter for a meeting’s transcript file
operatorthe person who accepts or changes each batch of moves, sends items, and decides each conclusion; on its own, the user
partone thing of one kind in a plugin; an inbox’s settings name the adapter parts it runs
partitionin crew, one domain of work with its own teams and its own flywheel branch
pluginthe installable unit in every host, holding parts; Flywheel’s statement calls it a package, and a named set of parts a bundle (228, 284)
pointer<host>:<path>, where a capture’s raw material is banked (217h)
raw banka host’s store of raw material, under millpond’s data directory, keyed by inbox and capture; never in git
raw materialthe event as its source served it, whole: notes, a transcript, a log; the adapter writes it as raw files
readera Claude session that turns an unread capture into signals with millpond’s read tool
runone start of an adapter part by millpond run, complete when it ends in done
schedulewhen a part runs: five-field cron, a missed run caught up once
sendmillpond giving one item to one worktree, with its brief and an agent, or an item that asks a question to a sounding
settingsmillpond.toml at the inbox’s root: its parts, its cut, its reader command, and where items go
signalone assertion from a capture: its kind, who asserted it, its subjects, the assertion in a sentence, the verbatim excerpt with its position, and the claims it argues with; never changed once written (113)
sourcewhere events come from, named in each capture: release, meeting, folder, deploy
tickmillpond tick, which runs every part of an inbox whose schedule is due
unreada capture with no excerpt, waiting for a reader

sounding’s words

sounding’s book defines these, and this page gives its definitions word for word (sounding’s glossary).

wordmeaning
conclusionconclusion.md: the answer, its evidence, what it would change, the work it proposes, and what stays open; the operator decides it
soundingone question, worked by one session in one place, ending on one conclusion; also the tool that runs them