1
0
forked from jason/echo

README banner: correct Phase 1-4 wording

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
2026-07-21 15:30:14 -05:00
parent 2ddf199850
commit 1a7690426f
+2 -2
View File
@@ -3,8 +3,8 @@
> **CHORUS is a group-based fork of [ECHO](https://git.alwisp.com/jason/echo)** — one shared > **CHORUS is a group-based fork of [ECHO](https://git.alwisp.com/jason/echo)** — one shared
> Obsidian vault serving a group of members instead of a single operator. The conversion > Obsidian vault serving a group of members instead of a single operator. The conversion
> plan and settled design decisions live in [CHORUS-PLAN.md](CHORUS-PLAN.md). The pre-fork > plan and settled design decisions live in [CHORUS-PLAN.md](CHORUS-PLAN.md). The pre-fork
> ECHO v1.5.1 state is preserved at the `echo-fork-point` tag. **Phases 14 (through shared-write > ECHO v1.5.1 state is preserved at the `echo-fork-point` tag. **Phases 14 (rename, identity, per-member
> namespacing) are done**; the body of this README below the fold still describes the > namespacing, shared-write hardening) are done**; the body of this README below the fold still describes the
> inherited single-operator behavior and is rewritten in Phase 5. > inherited single-operator behavior and is rewritten in Phase 5.
> Deployment endpoint: `https://chorusapi.mpm.to`. CHORUS is a **clean break** from > Deployment endpoint: `https://chorusapi.mpm.to`. CHORUS is a **clean break** from
> ECHO — fresh vaults on fresh machines; it carries no ECHO back-compat and never > ECHO — fresh vaults on fresh machines; it carries no ECHO back-compat and never