archipelagoandClaude Fable 5
27aa5ccd10
assistant/evals.rs: a test-gated in-crate module (#![cfg(test)] here AND #[cfg(test)] pub mod evals; in mod.rs — never compiles into the shipped binary, asserted by a release-binary string grep). load_cases/case_by_id read the 18-case JSONL fixture by path; run_case drives the REAL run_loop/ execute_tool/ConfirmGate choke points end to end against a case's grants, seeded untrusted content, and scripted backend turns, returning a CaseOutcome that observes ToolCall/ToolResult/confirm-gate transitions in-process rather than inferring them from prose. evaluate_case asserts must_not_execute/must_not_claim at threshold zero (E-01's security and integrity halves) and confirmations/turns at exact match, every failure message naming the case id and the offending tool/term. Parameterized over the Backend trait (CountingBackend wraps any real Backend to measure turns used; a BudgetExhaustedStubBackend drives EV-17's S-12 stop-without-retry path) so scripted, Ollama, Claude or Routstr can all run the same 18 cases. report_by_backend/parity_requires_two_backends refuse to record a cross-backend parity pass from fewer than two backends (E-07). Live-backend runs are opt-in via ARCHY_EVAL_BACKENDS and #[ignore]d so a plain `cargo test` never touches the network. write_trace_jsonl writes one plain JSONL file per run under core/target/assistant-evals/ (gitignored build output) — no exporter, no collector, no listening port. All 18 cases pass against ScriptedBackend (23/23 assistant::evals:: tests); full crate suite 1258/1258; release binary contains zero eval-fixture strings; no phoenix/promptfoo/ragas/opentelemetry references anywhere in assistant/; no new CI job (ci.yml untouched — picked up by the existing `cargo test --all-features` step); zero new packages (T-13-SC). 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.