From 1a7690426f6379e0080694ef4b7be8786e89e4d8 Mon Sep 17 00:00:00 2001 From: Jason Stedwell Date: Tue, 21 Jul 2026 15:30:14 -0500 Subject: [PATCH] README banner: correct Phase 1-4 wording Co-Authored-By: Claude Fable 5 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 754d5a3..cd1d0f5 100644 --- a/README.md +++ b/README.md @@ -3,8 +3,8 @@ > **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 > 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 1–4 (through shared-write -> namespacing) are done**; the body of this README below the fold still describes the +> ECHO v1.5.1 state is preserved at the `echo-fork-point` tag. **Phases 1–4 (rename, identity, per-member +> 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. > 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