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

Files

T

jason f2bfd70dd4 Phase 5: group-voice docs, onboarding runbook, CHORUS icon — v2.0.0-rc.1

The final phase of CHORUS-PLAN.md. Code- and doc-complete for group use;
rc pends live deployment at chorusapi.mpm.to.

- Repo README rewritten for CHORUS: group model (schema 5), concurrency
  posture, configuration, baked-build onboarding, layout, testing, 2.0
  version history (ECHO history referenced at the fork tag).
- Operator→member voice sweep across SKILL.md (incl. the trigger
  description, now group-aware), all references, 8 command docs, plugin
  README; member preferences / semantic layer / triage guidance describe
  the group model.
- docs/ONBOARDING.md: member runbook — vault stand-up, per-member config,
  bake, deliver, self-onboarding first load, norms, offboarding.
- docs/USAGE.md rewritten as the member usage guide.
- New icon: chorus-icon.svg + 1024/512/64 PNGs (three voices, one center).
- Removed ECHO-era assets (icons, spec PDF, perf briefs); ECHO planning
  docs retired to docs/history/. All preserved at echo-fork-point.
- eval/README documents test_multimember.py. Manifest -> 2.0.0-rc.1;
  rebuilt chorus-memory.plugin.

Verified: routing-sync, 25/25 unit, scaffold, 5 mock e2e suites,
run_eval metrics green.

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

2026-07-21 15:41:58 -05:00

1.9 KiB

Raw Permalink 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 member 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 (a preference about the capturing member goes to their own _agent/members/<member>/preferences.md::Observations via direct PATCH); project idea → project with --status incubating; durable fact → semantic; person fact → person.
Preview, then apply with the member'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 member 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.9 KiB Raw Permalink Blame History

1.9 KiB

Raw Permalink Blame History