Files
Jason Stedwell be3fd36ebf ver 1.5.0 — six-improvement pass: retention, routing, self-firing memory
1. capture-update keeps the whole body (was truncating to first line)
2. frontmatter completeness: kind-default status + kind-seeded tags at
   capture, fm create-or-replace, incomplete-frontmatter lint, sweep
   backfill (one data source: KIND_STATUS/KIND_REQUIRED_FM)
3. pre-write duplicate gate (exit 76, --merge-into/--force)
4. recall corpus + ranking: sessions/journal indexed (down-weighted),
   BM25 x freshness x status fusion, recall --json, index schema 2
5. session hooks: SessionStart auto-load, Stop reflection nudge
6. one-tap triage verb with processing-log audit; --json on read verbs

+22 mock end-to-end tests; all suites green. Docs current (README,
CHANGELOG, SKILL.md, commands, references, MAINTENANCE, eval README).
Drops tracked .DS_Store (gitignored); retires README-gretchen.md
(moved to gitignored dist/); adds the field report that drove item 2.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-03 12:57:52 -05:00

1.8 KiB

description
description
Triage the ECHO inbox — route aging captures to their canonical homes and log the moves

Use the echo-memory skill to run one-tap Inbox Triage via the triage verb (it reuses the reflect pipeline: classify against the entity index → preview → apply via capture, and writes the audit log for you).

ECHO="${CLAUDE_PLUGIN_ROOT}/skills/echo-memory/scripts/echo.py"
[ -f "$ECHO" ] || ECHO=$(ls /sessions/*/mnt/.remote-plugins/*/skills/echo-memory/scripts/echo.py 2>/dev/null | head -1)   # CoWork sandbox fallback
python3 "$ECHO" triage --list --json
# Windows: use `python` or `py -3` if `python3` is not on PATH.
  1. List — the JSON gives each capture as {line, date, text, age_days}. Surface the aging ones (≥ ~7 days) to the operator and ask which to route.
  2. Propose — for accepted items, write a proposals JSON with the Write tool (reflect schema: {"title","kind","body",...} plus "line": the original inbox line, echoed into the audit log). Route per the map: preference/pattern → semantic (or a direct PATCH to operator-preferences.md::Observations); project idea → project with --status incubating; durable fact → semantic; person fact → person.
  3. Preview, then apply with the operator's go-ahead:
python3 "$ECHO" triage proposals.json             # dry-run: classify + preview, writes nothing
python3 "$ECHO" triage proposals.json --apply     # route via capture + log each move

--apply records every move in inbox/processing-log/YYYY-MM-DD.md (- <original> → <destination>) automatically. Do not delete the original captures unless the operator explicitly asks — the processing log is the audit trail. A proposal that stops at the duplicate gate (exit note in the summary) should be re-proposed with the existing entity's title.