2f99db5e6b
- Add FEDERATION_STORE_LOCK (tokio::sync::Mutex<()>) guarding every load-mutate-save cycle in federation/storage.rs, closing the race where the 90s auto-sync loop's stale pre-removal snapshot could silently re-save a peer the operator just removed (no error logged anywhere). - Split load_nodes/save_nodes/tombstone_did/untombstone_did into thin locked outer wrappers + lock-free *_inner bodies so remove_node and add_node can hold the guard across their whole tombstone+save critical section without self-deadlocking (Mutex is not re-entrant). - Route load_nodes, save_nodes, remove_node, add_node, tombstone_did, untombstone_did, set_trust_level, and update_node_state through the lock (set_trust_level pulled forward from Task 2's scope — required for test_concurrent_writes_do_not_lose_updates, part of Task 1's own required-green test suite, to pass; documented in SUMMARY). - Convert save_nodes_inner to an atomic write: serialize to a sibling nodes.json.tmp in the same directory, then tokio::fs::rename onto the real path, so a crash mid-write never leaves a partially-written nodes.json for a concurrent reader. - Add 3 new regression tests, two of which are fail-first proven: heavy tokio::spawn-based concurrency (not just tokio::join!, since remove_node's extra tombstone I/O hop structurally biased a simple 2-task race toward the safe ordering) reliably reproduced both the lost concurrent write and the removed-node-reappears bug pre-fix; both are green post-fix along with the existing suite (13/13). 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.