archipelagoandClaude Opus 5
c098124d93
Task 3: four registry-wide structural tests in tools.rs, iterating registry() so a future tool that crosses the D-09 ceiling fails CI rather than depending on a reviewer noticing: - registry_never_exposes_excluded_authority (S-04/T-13-24): scans every ToolDef's name+description for EXCLUDED_AUTHORITY_TERMS. - read_tools_never_confirm (S-07/T-13-31): every non-destructive tool executes via the real execute_tool choke point without raising anything confirmation-shaped. bitcoin_status/network_status excluded from live execution (their handlers make real outbound network calls that would make this test flaky on a sandboxed box); their destructive:false placement is still covered by the other assertions. - loop_is_bounded (S-13/D-05): MAX_TURNS is enforced, and 3 consecutive malformed-argument calls for the same tool name abort the turn with an apology before a 4th scripted backend turn is ever polled. - every_tool_has_explicit_category_and_destructive: sanity-checks the registry has exactly the 13 hand-written tools (4 destructive) that made it in, as a runtime backstop to the acceptance criteria's static grep for `..Default::default()`. Negative-case demonstration (per the plan's acceptance criteria): a hypothetical `wallet_send_sats` tool with a description mentioning "spending sats" trips EXCLUDED_AUTHORITY_TERMS's "spend" term, verified by tracing the exact haystack-contains logic registry_never_exposes_excluded_authority runs (see 13-05-SUMMARY.md for why this was traced rather than executed). 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.