03a3e4e0c1
All checks were successful
Demo images / Build & push demo images (push) Successful in 3m49s
Task 2 of 02-04 — finishes the remaining tabs' lifecycle audit (Apps.vue, Discover.vue) and widens registration from the 02-02 tracer's single seed path to every main tab the profiling pass showed remounting. - Apps.vue: the 15s "unable to connect" timer follows activate/deactivate (idempotent re-arm, cleared on exit) and resets connectionError on entry so a since-reconnected node doesn't show a stale error instantly; the intro flag stays once-per-session. - Discover.vue: loadCommunityMarketplace/loadBitcoinPruneStatus now route through the same shared 'app-catalog'/'bitcoin.prune-status' cache keys Marketplace.vue introduced in 02-02, rather than duplicating the fetch; RefreshIndicator wired to the catalog resource's loadState. Discover's own dynamic-catalog-first fetcher (fetchAppCatalog with a curated-list fallback) is preserved as this key's fetcher for this view — both views are valid producers of the same shared cache entry. - Fleet.vue: confirmed no lifecycle side effects (grep for the five tokens found none) — left unchanged, registered as-is. - keepAliveRoutes.ts: KEEP_ALIVE_PATHS now derives from TAB_ORDER (single source of truth) plus /dashboard/discover, deliberately withholding /dashboard/settings even though it's in TAB_ORDER — Settings.vue's child sections (SystemDangerZone's reboot poll interval, VpnStatusSection/KioskDisplaySection/TransportPrefsCard/ClaudeAuthSection's one-shot onMounted fetches) were never in this plan's file scope and would misbehave under KeepAlive exactly as this plan exists to prevent. Every other TAB_ORDER path measured Remounted:true or was unmeasured in 02-FINDINGS.md, so per the plan's literal exclusion rule (only a measured Remounted:false excludes) they all stay registered, including Mesh and Chat. - keepAliveLifecycle.test.ts extended (in the prior commit) with shouldKeepAlive true/false assertions across every registered path and six secondary-screen paths, plus the KEEP_ALIVE_MAX+2 eviction test against the real DashboardRouterView + KEEP_ALIVE_PATHS. Co-Authored-By: Claude Fable 5 <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.