lfg2025/archy
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases 44 Wiki Activity

docs(CLAUDE.md): single-node gate GREEN — demote priority banner

Browse Source 
run-gate.sh 5/5 on .228. Reframe the TOP PRIORITY banner as
gate-green; keep the master plan as north-star source of truth; mark
the gate definition-of-done green and point at multinode as the next
exit criterion.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
archipelago 2026-06-23 04:35:50 -04:00
parent ae47897601
commit 0dd19f0721
1 changed files with 16 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
CLAUDE.md
View File

@ -1,13 +1,18 @@
# Archipelago — agent guide # Archipelago — agent guide
## 🚩 TOP PRIORITY (until production testing passes) ## ✅ Single-node production gate is GREEN (2026-06-23)
**Read `docs/PRODUCTION-MASTER-PLAN.md` first.** It is the authoritative plan and `tests/lifecycle/run-gate.sh` is **5/5 on .228, 0 failures** — the single-node exit
overrides ad-hoc direction until the production test gate is green. Goal: a criterion is met and the priority banner is demoted. Next exit-criteria: the
world-class, **developer-ready app platform** where every app is manifest-driven, **multinode pass** (`docs/multinode-testing-plan.md`) and workstreams B/C/D.
manifests ship via the **signed registry** (not OTA disk files), and **third-party
developers publish apps via an external/decentralized registry** — all rootless, **Read `docs/PRODUCTION-MASTER-PLAN.md` first** — it is still the authoritative plan
secure, robust, and 100%-uptime-capable. for the north star: a world-class, **developer-ready app platform** where every app
is manifest-driven, manifests ship via the **signed registry** (not OTA disk files),
and **third-party developers publish apps via an external/decentralized registry** —
all rootless, secure, robust, and 100%-uptime-capable. It no longer overrides all
ad-hoc direction now that the gate is green, but it remains the source of truth for
sequencing the remaining workstreams.
Detailed sub-plans (all linked from the master): Detailed sub-plans (all linked from the master):
- App platform / packaging phases + security model → `docs/APP-PACKAGING-MIGRATION-PLAN.md` - App platform / packaging phases + security model → `docs/APP-PACKAGING-MIGRATION-PLAN.md`
@ -45,6 +50,8 @@ Detailed sub-plans (all linked from the master):
`tests/lifecycle/run-gate.sh` green across install / UI / stop / start / restart / `tests/lifecycle/run-gate.sh` green across install / UI / stop / start / restart /
reinstall / reboot-survive / archipelago-restart-survive / uninstall — **5× on reinstall / reboot-survive / archipelago-restart-survive / uninstall — **5× on
.228** (`ARCHY_ITERATIONS=5`). **Run the gate ON the node** (it uses local podman/systemctl/bitcoin .228** (`ARCHY_ITERATIONS=5`). **Run the gate ON the node** (it uses local podman/systemctl/bitcoin
probes), not via RPC from another host. Until green, the master plan is the priority. probes), not via RPC from another host. **✅ GREEN 2026-06-23 (5/5, 0 not-ok)** — keep it
green (re-run after orchestrator/lifecycle changes); regressions are top priority again.
**Multinode testing (.198 + the rest of the fleet) is a SEPARATE plan** — **Multinode testing (.198 + the rest of the fleet) is a SEPARATE plan** —
`docs/multinode-testing-plan.md` — not part of this single-node gate criterion. `docs/multinode-testing-plan.md` — not part of this single-node gate criterion, and is
the next exit criterion now that single-node is green.