chorus/chorus-memory.plugin.src/commands/chorus-triage.md at d366ca40329ab8b10391585ff2e8d2f09db333eb

Files

T

jason d366ca4032 Phase 1: mechanical echo→chorus rename with back-compat shims

Identity rename, no behavior change (CHORUS-PLAN.md Phase 1):
- Plugin echo-memory → chorus-memory: manifest (v2.0.0-alpha.1), skill dir,
  16 scripts (chorus.py, chorus_config.py, …), EchoError → ChorusError,
  /chorus-* commands, hook paths, docs, scaffold seeds, eval harness,
  build.py. Docs endpoint → chorusapi.mpm.to.
- Env ECHO_* → CHORUS_*; config → ~/.claude/chorus-memory/config.json;
  state dir → ~/.chorus-memory/; marker → _agent/chorus-vault.md.

Back-compat shims (one major version):
- chorus_config aliases legacy ECHO_* env at import; reads a legacy
  echo-memory config.json when no CHORUS config exists (writes never
  land there); doctor/config report the legacy source.
- State dir honors an existing ~/.echo-memory when the new dir is absent
  (offline queue not stranded).
- Marker dual-probe in load/doctor/bootstrap/lint/sweep/migrate: a
  pre-fork _agent/echo-vault.md counts as bootstrapped; bootstrap repair
  won't write a second marker; routing gains agent-marker-legacy (GET).

Verified: 25/25 unit tests, scaffold + routing-sync checks, 4 mock e2e
suites, run_eval metrics unchanged, +6 shim smoke tests green.
Rebuilt chorus-memory.plugin (79 entries).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-21 13:35:51 -05:00

1.8 KiB

Raw Blame History

description

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

Use the chorus-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).

CHORUS="${CLAUDE_PLUGIN_ROOT}/skills/chorus-memory/scripts/chorus.py"
[ -f "$CHORUS" ] || CHORUS=$(ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/chorus.py 2>/dev/null | head -1)   # CoWork sandbox fallback
python3 "$CHORUS" triage --list --json
# Windows: use `python` or `py -3` if `python3` is not on PATH.

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.
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.
Preview, then apply with the operator's go-ahead:

python3 "$CHORUS" triage proposals.json             # dry-run: classify + preview, writes nothing
python3 "$CHORUS" 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.

1.8 KiB Raw Blame History

1.8 KiB

Raw Blame History