Substantive rework, not a path swap: - Retires D-15's pin-and-verify model. scripts/aiui.pin, pin_commit and --update-pin are dropped outright — there is no second repository left to pin, so build-aiui.sh now attributes a build to this repo's own `git rev-parse HEAD` instead. - Re-derives the build: aiui/ is an in-repo pnpm/turbo workspace with its own package.json and lockfile but no committed node_modules, so build-aiui.sh must `pnpm install --frozen-lockfile` before it can build (new requirement; the old model assumed a developer's separate AIUI clone was already installed). - Retargets deploy-to-target.sh (both its primary and --both/secondary AIUI sections) and setup-aiui-server.sh off the stale $PROJECT_DIR/../AIUI/packages/app/dist path, which still resolves on disk to a stale pre-migration clone and would otherwise silently ship old bytes instead of failing loudly. - Carries the /aiui/-scoped CSP sandbox work (AIUI-04) through unchanged per D-19, and fixes two acceptance-criteria drifts discovered while verifying the plan against deploy-to-target.sh's post-13-02 state and nginx-archipelago.conf's post-pentest-hardening state (CSP header count and the "no session gate needed" grep), neither of which is a D-19 effect. - Folds in a real defect found while doing this work: the 2026-07-31 same-host deploy guard only catches path containment, not sibling directories — the exact shape this worktree's own topology exhibits (archy-phase13 as a sibling of the main checkout, reachable over loopback SSH). New Task 3 widens it to refuse any same-host source/destination mismatch, extracted into a testable assert_safe_same_host_deploy in scripts/lib/common.sh and pinned by tests/production-quality/deploy-guard-same-host.sh. The checkpoint task is renumbered Task 3 -> Task 4 accordingly. 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.