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>

chorus-memory.plugin.src/skills/chorus-memory/references/api-reference.md

@@ -120,7 +120,7 @@ curl -s -X PUT \
 
 ```bash
 cat > /tmp/obs_patch.md << 'OBSEOF'
-The operator prefers concise status updates — lead with the decision.
+The member prefers concise status updates — lead with the decision.
 OBSEOF
 
 curl -s -X PATCH \
@@ -195,12 +195,12 @@ curl -s -X DELETE \
   "$CHORUS_BASE/vault/inbox/imports/old-note.md"
 ```
 
-Only on explicit operator request. Deletion is destructive.
+Only on explicit member request. Deletion is destructive.
 
 > **DELETE removes files only — never directories.** Deleting the last file in a folder
 > leaves the empty folder orphaned on disk; the REST listing then 404s (nothing left to
 > list), which falsely reads as "the tree is gone", but Obsidian's file explorer still
-> shows it. After removing a folder's last file, tell the operator the empty folder
+> shows it. After removing a folder's last file, tell the member the empty folder
 > needs manual deletion in Obsidian — do not claim the tree is gone from a 404 listing.
 > (Learned 2026-07-03 removing the retired `archive/` and `_agent/outputs/` trees.)
 

chorus-memory.plugin.src/skills/chorus-memory/references/bootstrap.md

@@ -35,7 +35,7 @@ curl -s -o /dev/null -w "%{http_code}" -H "$AUTH" "$BASE/vault/_agent/chorus-vau
 ```
 
 - **200** → bootstrapped. Read the marker's `schema_version`; if it is **less than** the plugin's current schema (4), run a migration pass (see *Migrations* below), otherwise proceed straight to the loading procedure in `SKILL.md`.
-- **404** → empty/unconfigured vault. Run **Fresh bootstrap** below. (If you expected an existing vault, confirm with the operator once that the REST API is pointed at the right vault before seeding.)
+- **404** → empty/unconfigured vault. Run **Fresh bootstrap** below. (If you expected an existing vault, confirm with the member once that the REST API is pointed at the right vault before seeding.)
 
 ---
 
@@ -137,7 +137,7 @@ Substitute `{{DATE}}`, then PUT `scaffold/chorus-vault.md` → `/vault/_agent/ch
 
 ### 6. First-run trace
 
-Create today's daily note from `journal/templates/daily-note-template.md` (resolve the `{{date:…}}` tokens to today), append a one-line `## Agent Log` entry noting the bootstrap, and write a session log in `_agent/sessions/YYYY-MM-DD-HHMM-bootstrap.md`. Tell the operator briefly what was created.
+Create today's daily note from `journal/templates/daily-note-template.md` (resolve the `{{date:…}}` tokens to today), append a one-line `## Agent Log` entry noting the bootstrap, and write a session log in `_agent/sessions/YYYY-MM-DD-HHMM-bootstrap.md`. Tell the member briefly what was created.
 
 ---
 
@@ -153,6 +153,6 @@ Run the same steps 1–5, but GET-probe each path first and **only create what i
 
 When the marker's `schema_version` is older than the plugin's, apply the migration steps for each intervening version, then PATCH the marker's `schema_version` frontmatter to the new value.
 
-- **0 → 1** (control-docs-in-plugin): the vault previously carried root control docs (`CLAUDE.md`, `BOOTSTRAP.md`, `STRUCTURE.md`, `index.md`). Back them up outside the vault, DELETE them, PUT the thin `scaffold/README.vault.md` over the old verbose `README.md`, write the `_agent/chorus-vault.md` marker, and scrub now-dangling `[[CLAUDE]]`/`[[BOOTSTRAP]]`/`[[STRUCTURE]]`/`[[index]]` links from the `## Related` sections of `operator-preferences.md` and `current-context.md` (leave historical session logs alone). Confirm with the operator before deleting.
-- **1 → 2** (reviews-folded-into-journal): the `reviews/` tree is retired. (a) For each note under `reviews/weekly/` and `reviews/monthly/`, MOVE it into `journal/weekly/` (rename `YYYY-Www-review.md` → `YYYY-Www.md`) and `journal/monthly/` respectively, preserving the earliest `created:`. (b) Move any `reviews/monthly/YYYY-MM-vault-health.md` to `_agent/health/`. (c) Move `reviews/quarterly|annual/` artifacts to `journal/quarterly|annual/`. (d) Update inbound `[[reviews/...]]` wikilinks in `## Related` sections to the new paths. (e) DELETE the now-empty `reviews/` tree. Confirm with the operator before deleting; leave historical session logs alone. *(This step covers any vault bootstrapped under schema 1.)*
+- **0 → 1** (control-docs-in-plugin): the vault previously carried root control docs (`CLAUDE.md`, `BOOTSTRAP.md`, `STRUCTURE.md`, `index.md`). Back them up outside the vault, DELETE them, PUT the thin `scaffold/README.vault.md` over the old verbose `README.md`, write the `_agent/chorus-vault.md` marker, and scrub now-dangling `[[CLAUDE]]`/`[[BOOTSTRAP]]`/`[[STRUCTURE]]`/`[[index]]` links from the `## Related` sections of `operator-preferences.md` and `current-context.md` (leave historical session logs alone). Confirm with the member before deleting.
+- **1 → 2** (reviews-folded-into-journal): the `reviews/` tree is retired. (a) For each note under `reviews/weekly/` and `reviews/monthly/`, MOVE it into `journal/weekly/` (rename `YYYY-Www-review.md` → `YYYY-Www.md`) and `journal/monthly/` respectively, preserving the earliest `created:`. (b) Move any `reviews/monthly/YYYY-MM-vault-health.md` to `_agent/health/`. (c) Move `reviews/quarterly|annual/` artifacts to `journal/quarterly|annual/`. (d) Update inbound `[[reviews/...]]` wikilinks in `## Related` sections to the new paths. (e) DELETE the now-empty `reviews/` tree. Confirm with the member before deleting; leave historical session logs alone. *(This step covers any vault bootstrapped under schema 1.)*
 - **2 → 3** (entity index + cross-linking): adds the `_agent/index/` folder for the machine-maintained entity registry. `migrate.py` creates the folder; the **data back-fill is `sweep.py`** — after migrating, run `python3 scripts/sweep.py --apply` to build `_agent/index/entities.json` from the notes already in the vault and to symmetrize existing `## Related` cross-links (it adds only the missing reciprocal direction, never invents links). `sweep.py` is idempotent and dry-run by default; re-run it any time `/chorus-health` reports index drift.

chorus-memory.plugin.src/skills/chorus-memory/references/operating-contract.md

@@ -20,7 +20,7 @@ You are an agent operating against an Obsidian vault that functions as a shared,
 
 - **Working** → `_agent/memory/working/` — transient, time-boxed.
 - **Episodic** → `_agent/memory/episodic/` — what happened, when.
-- **Semantic** → `_agent/memory/semantic/` — durable facts, patterns, preferences (`operator-preferences.md`).
+- **Semantic** → `_agent/memory/semantic/` — durable group facts and patterns (incl. `group-profile.md`); each member's preferences live in their own `_agent/members/<member>/preferences.md`.
 - **Context bundles** → `_agent/context/` — task-focused reading lists and active state.
 
 ## Safety rules

chorus-memory.plugin.src/skills/chorus-memory/references/routing-map.md

@@ -21,7 +21,7 @@ Views of the same truth: `scripts/routing.json` is the **machine-readable canoni
 | `inbox/imports/<slug>.md` | Raw external material dropped in wholesale (export, paste, dump) | The raw artifact, unedited | Holds un-triaged *bulk*, vs captures which hold single lines | PUT |
 | `inbox/processing-log/YYYY-MM-DD.md` | An inbox item is routed to its real home | One line: `<original> → <destination path>` | Audit trail of moves — never holds memory itself, only the record of routing | POST |
 
-Captures and imports are temporary by contract. Triage drains them into the homes below and logs the move; the original is left until the operator okays deletion.
+Captures and imports are temporary by contract. Triage drains them into the homes below and logs the move; the original is left until the member okays deletion.
 
 ## journal/ — the one append-only time-series stream
 
@@ -53,7 +53,7 @@ Lifecycle folders; `status:` frontmatter MUST equal the folder name (the linter
 
 | Path | Trigger | What lands | Distinct because | Method |
 |------|---------|------------|------------------|--------|
-| `areas/<domain>/<slug>.md` | Ongoing domain the operator maintains indefinitely (`<domain>`: business/personal/learning/systems) | Area note | No end state — the one thing that disqualifies it from `projects/` | PUT |
+| `areas/<domain>/<slug>.md` | Ongoing domain the member maintains indefinitely (`<domain>`: business/personal/learning/systems) | Area note | No end state — the one thing that disqualifies it from `projects/` | PUT |
 
 ## resources/ — reference material about the world
 
@@ -61,7 +61,7 @@ Lifecycle folders; `status:` frontmatter MUST equal the folder name (the linter
 |------|---------|------------|------------------|--------|
 | `resources/people/<name>.md` | A fact about a specific person | Person note (kebab-case slug) | Keyed to a person, not a topic or event | PUT / PATCH |
 | `resources/companies/<slug>.md` | A fact about an organization (client, vendor, partner, employer) | Company note (kebab-case slug) | Keyed to an organization, not an individual (`people/`) or an external source (`references/`) | PUT / PATCH |
-| `resources/concepts/<slug>.md` | A reusable concept/idea the operator wants on file | Concept note | An idea, vs a `reference` which is an external source | PUT |
+| `resources/concepts/<slug>.md` | A reusable concept/idea the member wants on file | Concept note | An idea, vs a `reference` which is an external source | PUT |
 | `resources/references/<slug>.md` | An external source/link worth keeping | Reference note | Points outward (a source), vs `concepts` (an idea) | PUT |
 | `resources/meetings/YYYY-MM-DD-<slug>.md` | Notes/recap tied to a specific meeting or call | Meeting note; mirror decisions to `decisions/by-date/`, commitments to the project | Event-anchored to a meeting, vs a project's ongoing thread | PUT |
 
@@ -90,7 +90,7 @@ Lifecycle folders; `status:` frontmatter MUST equal the folder name (the linter
 | `_agent/sessions/<member>/YYYY-MM-DD-HHMM-<slug>.md` | A substantive session ends (decisions/artifacts/commitments) | Session log (see template) | Per-session record, namespaced by member; the unit loading's heartbeat fallback scans | PUT |
 | `_agent/health/YYYY-MM-vault-health.md` | First substantive session of a month (Vault Health pass) | Health-audit findings | Agent self-maintenance about vault integrity — NOT a work narrative, so not in `journal/` | PUT |
 | `_agent/templates/` | Bootstrap only (seeded from plugin masters) | Canonical note templates | Holds templates, not memory; never a runtime routing target | PUT (seed) |
-| `_agent/skills/active/<slug>.md` | The operator authors/installs a skill and wants it catalogued | Skill capability entry | Catalogs a *capability*, vs `projects/` which tracks the *build effort* | PUT |
+| `_agent/skills/active/<slug>.md` | The member authors/installs a skill and wants it catalogued | Skill capability entry | Catalogs a *capability*, vs `projects/` which tracks the *build effort* | PUT |
 | `_agent/skills/archived/<slug>.md` | A catalogued skill is retired | Skill entry (moved from `active/`) | Terminal state of the skill catalog | PUT |
 | `_agent/locks/vault.lock` | Advisory multi-writer lock acquire/release | One line: `<owner> @ <ISO-timestamp>` | Concurrency coordination, not memory; managed only by `chorus.py lock/unlock` | PUT / DELETE |
 | `_agent/index/entities.json` | Rebuilt on every `capture` and on `sweep` | Slug→{path, kind, title, aliases, last_seen} registry | Machine-maintained routing/recall index, not a note; the one JSON in the vault | PUT |
@@ -127,7 +127,7 @@ Listed so they are recognised as dead and never recreated. Any one of these appe
 ## Routing decision tree (the calls that get mis-made)
 
 1. **Destination unknown right now?** → `inbox/captures/`. Known? → route directly; never park a known fact in the inbox.
-2. **Is it about the operator's work over time?** → `journal/` (pick the grain by cadence). **About the vault's mechanical health?** → `_agent/health/`. These two look similar monthly but answer different questions.
+2. **Is it about the member's work over time?** → `journal/` (pick the grain by cadence). **About the vault's mechanical health?** → `_agent/health/`. These two look similar monthly but answer different questions.
 3. **Does the effort have an end state?** → `projects/` (folder = `status:`). **No finish line?** → `areas/`.
 4. **A fact about the world:** timeless → `semantic/`; a thing that happened → `episodic/`; needed only for now → `working/`. A fact about a *person* → `resources/people/`; a fact about an *organization* → `resources/companies/`.
 5. **A decision:** always `decisions/by-date/`; mirror into a project only if one already exists.

chorus-memory.plugin.src/skills/chorus-memory/references/session-log-template.md

@@ -80,7 +80,7 @@ client: claude-code
 Build and package the chorus-memory CoWork plugin against the live vault.
 
 ## Notes Read
-- [[BOOTSTRAP]], [[STRUCTURE]], [[_agent/memory/semantic/operator-preferences]]
+- [[BOOTSTRAP]], [[STRUCTURE]], [[_agent/members/<member>/preferences]]
 
 ## Actions Taken
 Verified the REST API end-to-end, confirmed the scaffold copied into the live vault,

chorus-memory.plugin.src/skills/chorus-memory/references/vault-layout.md

@@ -119,18 +119,18 @@ change `updated:` or `status:`, use PATCH with `Target-Type: frontmatter`.
 
 ## File-Specific Conventions
 
-### operator-preferences.md (`_agent/memory/semantic/`)
+### preferences.md (`_agent/members/<member>/`)
 
-The profile analog. Canonical headings:
+Each member's profile analog — how the agent should work FOR that member. Group-visible by design (one vault, one key); only that member's own sessions edit it. Canonical headings:
 
-- `## Operator` — who the vault owner is (one paragraph)
+- `## Member` — who this member is (one paragraph)
 - `## Fact / Pattern` — **promoted, deduped rules.** No date prefix. Timeless.
 - `## Observations` — **timestamped raw observations.** Date-prefixed lines (`- 2026-06-06: ...`). Default landing zone for new evidence.
 - `## Evidence` — citations/links supporting the rules
 - `## Recommendation or Implication` — how the rules should shape behavior
 - `## Review Notes` — confidence / last review date
 
-Append observed facts under `## Observations` by default. Promote to `## Fact / Pattern` (dropping the date) once a pattern stabilizes. "The operator" is the vault owner — refer to them generically and in the third person (the display name is the runtime `owner` config value).
+Append observed facts under `## Observations` by default. Promote to `## Fact / Pattern` (dropping the date) once a pattern stabilizes. Write in third person by name ("Jason prefers X"), so the note reads correctly to every member and agent.
 
 ### projects/active/\<slug\>.md
 
@@ -189,11 +189,11 @@ ADR-style: Context → Decision → Consequences. If the decision belongs to an
 
 ### companies/\<slug\>.md
 
-`type: company`. An organization the vault owner works with — client, vendor, partner, or employer (e.g. `acme.md`). Distinct from `people/` (individuals, who *belong to* companies) and `references/` (external sources). Lowercase kebab-case slug.
+`type: company`. An organization the group works with — client, vendor, partner, or employer (e.g. `acme.md`). Distinct from `people/` (individuals, who *belong to* companies) and `references/` (external sources). Lowercase kebab-case slug.
 
 ---
 
 ## Cross-References
 
 Use Obsidian wiki links freely: `[[note-name]]` or `[[folder/note]]`. The REST API
-doesn't resolve them, but Obsidian does when the operator browses the vault.
+doesn't resolve them, but Obsidian does when the member browses the vault.