Dorian
1c43d039ed
nostr:nevent1qqs0prrsudg9mqx03u4cl8a53pn4wl45ls0qayw34tw6n4xdz5zd5xgpz3mhxue69uhhyetvv9ujumn8d96zuer9wc3k0ak0 PR-Author: Personal nostr:npub1w3sqdkrhn0gyuvsex32effzgnfpyde6qrrc4u467flg5e9txh4wsfn5vjg CoverNote: Maintainer approved the scoped UI/UX change on 2026-11-13; installed acceptance and release qualification remain pending ## Screens and flows to review 1. **Settings → What's New** (`/dashboard/settings`): sign in on a qualified test node, open What's New, read the new 2.1.22, 2.1.21, beta.2 and beta.1 entries, scroll through older entries, then close with the Close button and the top-right control. Check that the heading, dates, badges, scroll area, backdrop, focus, and close controls retain the existing design. Empty, loading, and error states are not applicable to this static release-note modal; the success state is readable content without clipping. 2. **Login startup** (`/login`): on a node starting behind a 502/503 proxy, confirm the startup status remains visible and the password form is not shown prematurely; when the backend answers 200 or 401, confirm the ordinary login form appears and accepts the normal sign-in. Check a transient network failure followed by recovery. Navigate away during a pending health check and confirm it does not restart polling or show a late login state. The empty state is the normal password form with no entered value; loading is the startup status behind 502/503; error is the existing incorrect-password treatment; success is the usable form followed by normal sign-in. Fresh-node setup should still appear only after an actual setup-state response. The Login template and styling are byte-identical to the prior accepted source; the change cancels late startup work after navigation. 3. Review both flows at desktop and phone widths with the operating system set to light and dark preference; the product's dark-only styling should remain consistent. Smoke-check the Login flow on a kiosk if that surface is available. No app installation, test funds, wallet operation, or identity change is required for this UI review. ## Source and test scope The only visible UI addition is curated release-note text in the existing Settings modal. No layout, style, color, icon, animation, or Login markup changed. Source tests cover 502/503 and network-error recovery and late response cleanup (focused Login 14/14 PASS; full Vue typecheck PASS; What’s New sync 36 versions PASS). The static before/after screenshots are review fixtures, not installed-node acceptance. Maintainer approval of the note-only UI and Login lifecycle scope is recorded; the static preview is not installed acceptance. ## Upgrade correction Fresh historical ISO installations can contain the exact signed web UI without the `archipelago-runtime` subtree added by the historical OTA packager. Version 2.1.21 rejected this legitimate layout during first-boot admission. Recognize complete absence of that subtree only for the 12 audited historical releases; every remaining path, file hash and executable bit still has to match the authenticated archive. Partially present runtime trees, symlinks, changed files and unrelated missing files remain refused. Preserve the actual old layout for recovery. The public 2.1.21 offer is on hold. This change prepares immutable version 2.1.22; it does not alter the published 2.1.21 tag or artifacts or promote the update feed. It also corrects stale test fixtures and source formatting so release checks remain effective. ## Validation and remaining gates - Adoption and resume regression suites: 74 passed, including rejection of a linked runtime subtree without changing the link target. - Authenticated historical archive projection audited for all 12 supported releases; historical ISO builder sources independently reviewed. - Login regression suite: 14 passed; frontend typecheck, release-note synchronization and Rust formatting pass. - Full isolated backend suite: 3,187 passed, 0 failed, 29 ignored. The exact checkout regression also passed in isolation before the full run. Earlier failures and resource-limited attempts remain preserved. Immutable production artifacts and real upgrade/preservation checks remain required before feed promotion. - Maintainer approval of the UI scope above is recorded. Source-bound production artifacts, real fresh-ISO and existing-OTA upgrade preservation, and public asset/feed gates remain pending; this description does not claim installed acceptance. - The optional payment-password setting remains off by default. Test fixtures opt in when exercising fresh funds authority; identity export remains protected. The original on-chain rental guard still refuses a different rail. Assistant signing remains outside its tool dispatcher and uses visible consent. The opaque-tag test now checks the existing behavior that suppresses unproven update notices. - The 2.1.22 legacy compatibility inventory retains the same 12 historical version/manifest-hash entries as 2.1.21; its only content change is the target version. Publication must still retrieve and authenticate every declared alias and full fallback frontend through the installed verifier. - ISO build and clean-install qualification remain separate. Earlier failed and resource-limited test attempts remain preserved evidence.
Archipelago
Alpha testing — funds at your own risk. Archipelago is experimental software and is not production-ready. Any funds you put on it are at your own risk. Substantial security hardening is planned before production readiness; current builds are for testing and feedback.
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.
Current release
As checked on 2026-11-12, the latest published application update is
v2.1.0-beta.2.
It has signed OTA assets but no installer ISO. The latest publicly
qualified x86_64 installer remains
v1.9.0-alpha.
The later v1.9.1-alpha RC1 ISO is explicitly marked unqualified in its release
notes. Check the releases page
for a newer qualified installer or update before using these versions. Source
on main, published artifacts, and installed-node acceptance are separate.
ngit is the canonical source contribution and review platform. Gitea mirrors accepted source and hosts release downloads. For Nostr-native cloning:
nostr://npub1w3sqdkrhn0gyuvsex32effzgnfpyde6qrrc4u467flg5e9txh4wsfn5vjg/relay.ngit.dev/archy
Clone with ngit, or use the Gitea mirror when you need a conventional Git remote. Contributions should follow CONTRIBUTING.md.
Install on a server
Use a dedicated x86_64 Intel/AMD server, mini PC, or PC, an SSD, and an 8 GB or larger USB drive. For Bitcoin and multiple apps, 8 GB or more RAM and a generously sized SSD are recommended; an unpruned Bitcoin node needs room for the growing blockchain. Connect Ethernet and a monitor/keyboard, or use your server's remote console and virtual installation media.
-
Choose a qualified installer from the releases page and download its checksum alongside it. At the 2026-11-12 check, that means:
-
Verify the download. Save the ISO and
.sha256file together, then on Linux run:sha256sum --check archipelago-installer-1.9.0-alpha-unbundled-x86_64.iso.sha256The result must be
OK. This checks file integrity; the signed JSON is provided separately for release-signature verification. -
Write the ISO to USB using Balena Etcher or your preferred image writer. Write the image rather than copying the ISO into the USB filesystem. For a remotely managed server, attach the ISO as virtual installation media instead. This is a raw
.iso; no decompression is needed. -
Boot the server from that media and follow the console installation prompts. Verify Secure Boot compatibility for the selected image and firmware; later image-recipe work does not change previously published ISOs. Installation erases the selected target disk, so back up its contents and check the disk selection carefully.
-
Remove/eject the installation media and boot from the installed disk. Find the server's address in your router's DHCP client list or local console, then open
http://<server-ip>from another device on the same network. -
Complete first-run setup: create your dashboard password and follow the onboarding wizard to choose apps and Bitcoin storage settings. The unbundled ISO downloads app images as needed, so allow internet access for app setup.
For an existing Archipelago server, use the dashboard's Settings update flow for a published OTA rather than reinstalling. See the user walkthrough for onboarding and daily use.
This remains alpha software: funds are at your own risk, and production security hardening is still ahead.
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
- Troubleshooting
Quick start
Frontend
cd neode-ui
npm ci
npm start
The dev UI runs at http://localhost:8100 with a mock backend on :5959.
Backend
cd core
cargo check --locked
On a machine with installed apps, run backend tests only through
scripts/test-backend-isolated.sh from the repository root. See the
developer guide; cargo test --no-run compiles but
does not execute tests.
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.
New Developer Reading List
Start here, in order:
- This README for the product, source tree and published release distinction.
- Documentation index for a task-based map.
- Working rules and contribution guide for safe checks and the canonical ngit workflow.
- Developer guide for local setup and the source map.
- OS architecture and its visual HTML guide for system layers, trust and update boundaries.
- Release & Testing for current scope and the evidence required before calling a build accepted.
Then read the documents for the area you are changing:
| Area | Guides |
|---|---|
| Backend and API | API reference · container lifecycle |
| App packaging | App developer guide · manifest spec · Quadlet compilation · secrets · catalog distribution · packaged apps |
| Installer and OS updates | Image recipe · OS updates · protected updater contract |
| Network and security | Nostr Git workflow · multi-node architecture · external access and websites · security policy |
The roadmap describes direction. The documentation index links to dated designs and historical evidence when you need them; those records do not replace current acceptance.
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.