Skip to content

Glossary

Term Meaning More
entry one item of the library (a skill, rule, script, agent, hook, fact or lesson) with its own trigger, counters and status entries
draft an entry made from a description only; visible, never loaded create a skill
provisional an entry that hasn’t proven itself yet; loads only where its predicate matches, and is counted there entries
kept an entry that survived 4 matched sessions with no recurrence and no harm; loads natively. Never called verified counters
retired · dormant · stale archived statuses; never loaded, never deleted entries
pinned a flag: the entry is never replaced or retired automatically day to day
redirect a turn in which you steered the agent: a negation, a revert, a reprompt, an interrupt, or a mark the loop
correction · preference · scope the classifier’s labels for a redirect: done wrong · not how you like it · you changed your mind correct the classifier
takeover input that reaches the agent while it is still running (an interrupt) harness capabilities
flag the mark a session gets at shutdown when it carried a redirect, a tool-error cluster, a takeover or a mark; only flagged sessions are reflected on the loop
reflection the between-sessions step that classifies, proposes, lints and stages; at most 3 model calls the loop
predicate (trigger) the deterministic repo, file types and task words that decide where an entry loads and which sessions count predicates
matched a session in which the entry was loaded and its predicate hit; the denominator of every decision counters
recurrence the redirect class that motivated an entry happened again while it was loaded counters
harm a new tool-error cluster, a takeover, or a disable while an entry was loaded counters
canary a provisional entry still being counted; no new reflection runs for its predicate meanwhile counters
branch a repo or project; entries are staged per branch. shared holds entries kept in two or more the evidence boundary
domain a dotted subject path such as web.frontend; an entry loads only in sessions of its domain or a sub-domain domains
ledger ~/.rematch/ledger.sqlite: current state of sessions, entries, counters, proposals and receipts file locations
journal the ledger’s append-only record of every write, with the ledger’s own clock; what the lake exports the lake
lake the journal and closed sessions as write-once Parquet files under ~/.rematch/lake/; history, never read by a session the lake
profile a git repo at ~/.rematch/profile/ holding your omp setup, linked into every machine that syncs it the profile
digest the session-start summary of what was staged, kept or retired, approvals waiting (one item per entry: scripts, hook, subagent and prompt text), and entries ready to ship day to day
verifier a mechanical pass/fail check (tests, script, parity, receipt) that picks winners in batch mode batch with a verifier
anchor replay one re-run of a kept skill’s task with its replacement loaded, before the replacement goes ahead batch with a verifier
surface one of the eight parts of a harness rematch can change the eight surfaces