archipelagoandClaude Opus 5
48a2ff7c16
Deployed the poller fix to archi-dev-box and re-ran the frozen harness (02-PERF-FINAL.json, 5 runs/surface). Web5 fixed (275ms, below both its 566ms pre-phase-2 baseline and the 300ms pass bar). Server's regression closed (574ms, below 738ms baseline) though not yet under 300ms. Fleet substantially improved (790ms, down from a 2631ms regression). AppDetails restored to at/near its own baseline. Investigated the two open items the coordinator raised: - OpenWrtGateway: this run's 5/5 samples failed with a Chromium "Target crashed" error cascading from an unrelated surface earlier in the same harness run — recorded as not-measurable, not written in as data. Separately confirmed via source (OpenWrtGateway.vue's h1 renders unconditionally, and a "No router configured" RPC error deterministically shows a real Connect-to-Router form) that the prior baseline/after/remeasure numbers were measuring a genuine, substantive disconnected-state UI render, not an empty/error page — so the "six confirmed regressions" count is not retracted, but the numbers are flagged as reflecting one specific code branch. - Discover (1389ms, worst remaining, least improved): profiled directly and found a SECOND, distinct, phase-2-class cause — showStagger/card-stagger entrance-animation classes are baked into the DOM at first mount and never programmatically removed (the flag is a correctly-scoped once-per-session const, but nothing ever re-renders to strip the class), so every KeepAlive detach/reattach cycle restarts the CSS animation on reactivation, replaying the full entrance cascade on every revisit. Confirmed via a diagnostic showing DOM card count doubling transiently on every revisit and an extended animationstart/animationend event log. Not fixed this pass — the safe fix's blast radius spans 5+ files outside this plan's scope (Apps.vue, Marketplace.vue, Home.vue, several Web5 sub-cards) and needs its own real-device verification budget, matching the precedent 02-02's original KeepAlive rollout needed for this exact class of change. Named and evidenced, recommended as a dedicated follow-up rather than expanded into this plan under time pressure. REQUIREMENTS.md's PERF-02/PERF-03 rows updated to the final state. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Archipelago
Self-sovereign Bitcoin node OS and manifest-driven app platform.
Archipelago is a bootable personal server OS for Bitcoin infrastructure,
self-hosted apps, mesh communication, decentralized identity, and federation.
Apps are packaged as declarative manifest.yml files and run as rootless
Podman containers managed by the Rust backend.
What is here
core/- Rust workspace: backend API, container runtime, security, OpenWrt helpers, and performance/resource management.neode-ui/- Vue 3 + TypeScript frontend.apps/- app manifests and custom app container sources.docker/- supporting container build contexts for UI companion surfaces.image-recipe/- bootable image/ISO build inputs.Android/- Android companion app.scripts/- development, release, deployment, and validation tooling.docs/- architecture, app packaging, operations, API, and roadmap docs.
Platform model
Archipelago is built as a developer-ready app platform, not a fixed appliance:
- Apps are declared in
apps/<app-id>/manifest.yml. - The Rust parser in
core/container/src/manifest.rsis the canonical schema. - The orchestrator compiles manifests to rootless Podman/Quadlet runtime state.
- App data lives under
/var/lib/archipelago/<app-id>/. - Secrets are generated or read from
/var/lib/archipelago/secrets/and injected through Podman secrets rather than static environment values. - Release and app catalogs are signed and verified against a pinned trust anchor.
Start with:
- Architecture
- Developer Guide
- App Developer Guide
- App Manifest Spec
- Nostr Git Source Hosting Plan
- Operations Runbook
- Troubleshooting
Quick start
Frontend
cd neode-ui
npm install
npm start
The dev UI runs at http://localhost:8100 with a mock backend on :5959.
Backend
cd core
cargo build
cargo test --all-features
Linux is the supported backend runtime and release-build target. macOS is fine for frontend work and many Rust compile/test loops, but host integration tests that touch Podman, systemd, networking, or image build paths require Linux.
App manifests
./scripts/validate-app-manifest.sh apps/filebrowser/manifest.yml
python3 scripts/generate-app-catalog.py
python3 scripts/check-app-catalog-drift.py --release --strict
scripts/generate-app-catalog.py requires Python with PyYAML installed.
Documentation map
| Doc | Purpose |
|---|---|
| Architecture | System layers, crates, data paths, security model |
| Developer Guide | Local setup, code workflow, testing |
| API Reference | JSON-RPC API overview |
| App Developer Guide | How to package and test apps |
| App Manifest Spec | Manifest schema and validation rules |
| Nostr Git Source Hosting Plan | ngit/NIP-34 contribution workflow and maintainer model |
| Apps README | Packaged app catalog overview |
| Image Recipe | Bootable image build flow |
| Operations Runbook | Production operations and recovery |
| Open Source Readiness | Public-release cleanup checklist |
| Roadmap | Shipped, in-progress, and planned work |
| Unified Task Tracker | Launch hardening task list |
| Archive | Historical plans, audits, and handoffs |
Contributing
Read CONTRIBUTING.md before opening a pull request. For security issues, follow SECURITY.md and do not open a public issue.
License
Archipelago is licensed under the MIT License. Third-party notices are listed in NOTICE and generated license inventories in component release artifacts.