Repository navigation
duobrain v0.1.7
duobrain v0.1.7
Records are written to be found, and an agent finds them in one step. In the product repository, run:
npx duobrain@0.1.7 installAdded
-
find. One structured query (--queryin the user's words, plus--intent,--expand,
--entities,--exclude,--kinds,--limit, or--file <json>) looks through wiki notes,
tickets and session handoffs along two channels at once:- search matches words with BM25F (title and keywords weigh most, Korean is compared in
two-character pieces, English is lightly stemmed), then judges by rule: a superseded note drops
and its replacement rises, evidence for an open or named ticket rises, a summary folds in its
sources, and the list stops at the first steep score drop. At most a few cards come back, each
with why it matched, plusmatch: strong | weak | none. - browse lists every other record as one short line (title, status, date, short abstract),
newest first, at most 100, so the agent can pick by meaning what word matching missed.
--no-browseomits it.
No bodies are returned. Cards link notes and tickets both ways (
evidenceFor,evidence). - search matches words with BM25F (title and keywords weigh most, Korean is compared in
-
wiki-get --path wiki/<id>.mdandticket-get --ticket <id>open one record in full. -
Search metadata on notes. A wiki note may carry
abstract(one or two sentences) and
keywords(up to 12, in every language the team uses, with entities and the questions it
answers). Notes without them stay valid;note-addreportssearchMetadata.missing. -
Wiki in the briefing.
status --briefshows the evidence notes of my open tickets (up to 5)
and notes others recorded after my last handoff (up to 3), as cards without bodies.
Changed
wiki-listreturns cards without bodies.wiki-list --fullreturns every note as before.- The AI guide's lookup limit is now: briefing, one
findjudged across both channels, at most two
opened records (in a sub-agent when available), thenunknownand a ticket. Lookups are answered
in four lines with a quoted line from the record.
Compatibility
No new events and no migration. Engines on 0.1.6 ignore abstract and keywords, so partners can
update one at a time. wiki-search is unchanged.
Upgrading
node .duobrain/bin/duobrain.js update moves a vendored copy to v0.1.7; the partner pulls.
Verification
Unit tests cover the search metadata, both channels, Korean and English word forms, supersession,
ticket evidence, summary folding, the cutoff and none. A two-clone test drives find, wiki-get,
ticket-get, wiki-list and the briefing through the CLI.