16 KiB
Curated documentation snapshot as of 2026-10-24 08:08 UTC. Lane-owner factual review pending unless explicitly stated; not release approval, execution admission, or confirmation that implementation is published.
Fixed requirement and evidence matrix
All 48 IDs and 30 task titles below are transcribed from the canonical scope ledger. Titles are scope definitions, not current completion statuses. Every whole requirement remains OPEN / not certified by this collection pending owner reconciliation. Narrow evidence must never be promoted to whole-row completion.
| ID | Requirement | Mandatory scenario / remaining acceptance | Current evidence boundary |
|---|---|---|---|
| A01 | Native identity/authentication | Native identity login/logout/account swap/expiry and cancelled consent; reject stale/app-generated keys; iframe/tab/Companion authority isolation. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A02 | Backstage UX and assets | Both Backstage asset sources; save/reopen/reload/cancel/resume and worker failure; protect old assets on replacement; private drafts and explicit publication consent; original responsive accessible UI. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A03 | Distributed film catalog | Publisher/buyer/unrelated late-node signed catalog pagination, identity/revision/withdrawal, partitions/backfill, draft/private-master secrecy and bounded discovery. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A04 | Global film discussion | Stable film discussion across origins; signed comment/reply/reaction identity, deduplication, partition/reconnect, bounded subscriptions and author/XSS refusal. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A05 | Shared native checkout and settlement | Enabled native/external rails, exact recipient/price/revision/fees/consent; unknown settlement/lost reply/crash/concurrency; one intent and at most intended spend; producer-unavailability privacy. | Isolated app signed-admission 127/7 raw/outer PASS; native 28 new cases UNRUN; paired first invoice/recovery/installed acceptance OPEN. |
| A06 | Entitlements and recovery | Payment vs first-play clock; atomic concurrent first start/watch-later/original resume window; entitlement authority, expiry/range/seek/key/cache, explicit renewal and recovery without repayment. | Isolated app signed-admission 127/7 raw/outer PASS; native 28 new cases UNRUN; paired first invoice/recovery/installed acceptance OPEN. |
| A07 | FIPS-only streaming | Every remote media variant/redirect/master/trailer/subtitle/segment/key enforces authenticated FIPS+entitlement; deny fallback when FIPS fails; restore without repayment; actual codec/seek/background. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A08 | Availability and capacity | Authorized replica/readiness/capacity and failover; bounded resources/backpressure; declared codec/bitrate/link/concurrency soak, p50/p95 and expiry/recovery; no unqualified availability promise. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A09 | Durable app delivery | Exact immutable UI/API/native compatibility, served-byte identity, nonempty migrations, monetary journal/outbox/asset preservation, restart/update interruption and rehearsed rollback; managed installed lifecycle. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A10 | Bounded chunked ecash streaming | Zero/off/integer/upper-bound chunk budget, insufficient next chunk/exact stop, atomic reserved+spent, concurrent sessions, changed rates/fees, paid retry/seek, pause/background, unresolved locks and no double debit after restart. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A11 | Social actions and all-supported-rail zaps | Original zap preset/custom/return UX, rent-independent creator capabilities, each supported native/external approval and rail-correct receipt, pending/confirmed distinction, no access grant and exactly-once social totals. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A12 | Integrated Networking Profits | Disjoint revenue buckets, confirmed-only totals, no session double count, period/timezone/pagination, idempotency/reorg/restart, unknown vs zero, no private payer budgets and gross vs net. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| A13 | Public guest IndeeHub isolation | Public guest isolation from owner session/wallet/signer/Backstage/private files and management; cross-origin/iframe/peer/account/logout negatives, no unauthorized mutation or privilege transfer. | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B01 | Paid Cloud Files | Original paid-file attempt recovery/exact bytes without repayment; retain earlier incident evidence | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B02 | Wallet fee experience | Fast/custom fees, shortfall/budget/restart/RBF/CPFP/reorg and unknown-not-zero matrix | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B03 | Cloud connectors | Real Nextcloud/Immich and album/account permissions, revocation, exact bytes/ranges/preview, 250+1 pagination and stale/refresh revision; installed/absent-stopped File Browser/lifecycle/proxy/native identity. | Provider/browser sub-exits retained; actual 250+1 pagination NOT qualified; installed/native-identity lifecycle remains open. |
| B04 | File Browser and uploads | File Browser credentials/custom users, removal warnings, exact-byte resumable/cancellable upload and phone progress | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B05 | Cloud viewer/downloads | Current viewer/download menus, safe areas/fullscreen, authenticated save/cancel and no login-HTML downloads | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B06 | Public files/folders | Explicit public file/folder/pricing/discovery/withdrawal after connection UX; no unauthorized publication | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B07 | Mesh file sharing | Private multi-file Mesh picker/staging/recipient binding/retry/cancel/partial recovery/exact receiver bytes after connection UX | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B08 | Private V4V demo | Shared non-film native media session/queue/position/reopen and permission transitions | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B09 | Reusable audio/video platform | Physical background/lock/headset/PiP/logout/reconnect/process recreation | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| B10 | Companion notification artwork | Actual-track native notification artwork physical acceptance — LAST | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C01 | Peering and requests | Reciprocal request/approval/removal, replay/auth/late-reply/reconnect state | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C02 | Fleet and federated sync | Fleet actions/provenance/authenticated metrics/mixed-version/dedup/partial sync | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C03 | Availability/map and final connection UX | Final connection/map/mobile/accessibility and operator-reviewed UX — before B06/B07 | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C04 | Latency and companion reliability | Measured useful-data cold/warm p50/p95, cancellation/background/resume | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C05 | Monitoring and visual regressions | Current affected-node Monitoring/disk/null/threshold/footer/filter regression; retain historical repairs | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C06 | HTTPS app authentication | Trusted HTTPS/origin/session/iframe/gate and actual affected Alby Copy; physical trust remains separate | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C07 | AIUI setup/funding | Current AI provider/auth/error/unfunded/outage/prompt/funding-refresh behavior, without unapproved paid inference | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C08 | MeshCore | Actual standard MeshCore two-way/device/serial/reconnect interoperability | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C09 | Firewall/tunnels | Effective firewall/tunnel/NPM/IPv4+IPv6/routes/TLS/ACME/reboot/rollback | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| C10 | Mesh message formatting and replay | Reported actual-frame sender/body/replay UX; missing physical input/semantics not invented | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D01 | Lifecycle/update safety | Managed lifecycle install/start/stop/restart/upgrade/interruption/preserve/uninstall/reinstall | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D02 | Container storage and recovery | Store/update/legacy/alias/tombstone/ownership behavior and truthful outcomes | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D03 | NPM/public security | Public Web Router/NPM managed route/config/data/security preservation | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D04 | Gitea/Portainer/GitWorkshop | Gitea/Portainer/GitWorkshop install orders, Git/SSH/LFS/registry/Compose/workspace persistence | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D05 | Bitcoin/Lightning/ecash application regressions | Named Bitcoin/Lightning/ecash current package/readiness/backup/no-resurrection regressions; prior LND incident not reopened | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D06 | Angor | Angor current client/explorer/TLS/WebSocket/full-chain checks; retained historical missing-announcement limitation | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D07 | Websites/external access | Cloud websites/generic public routes, effective access controls and rollback | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D08 | Business/mining apps | Actual Just Works/Gashboard/DATUM identity/business/miner/admin/reboot workflows | Whole requirement OPEN; owner must reconcile scenario-level evidence against the testing contract. |
| D09 | Terminal/developer environment | Real production terminal HTTP/WebSocket/tmux auth/input/resize/history/reconnect/dead-session and metadata-failure rollback; exact packaged default-workspace sandbox, installed login/browser creation/tools/shell/keys/process/reboot, physical Companion and independent acceptance. | Disposable production transport/history/metadata rollback passed at earlier exact source; packaged sandbox/installed/device/independent acceptance OPEN. |
| D10 | Shared design and app-development contract | Real generated starter app using maintained design contract, responsive/error/accessibility/package checks | Earlier generated-app/browser/package sub-exits; full design/accessibility/managed/physical requirements OPEN. |
| D11 | Hardware/discovery UI | Signed event/hash/author validation, replacement/withdrawal/expiry, details/link, stale cancellation and responsive accessible controls; actual configured relay/external handler, installed/device/visual and independent acceptance. | Earlier signed synthetic-relay/browser and frontend sub-exits; actual configured relay/installed/device/review OPEN. |
| E01 | Provenance and review | Exact accepted source/proposal/mirror/history/provenance reconciliation | No whole-row approval established; accepted provenance/artifacts/installed/UAT/release gates remain distinct. |
| E02 | Reproducible artifact set | Compatible immutable artifacts, independent required review, nonempty backup/migration/rollback and integrated freeze | No whole-row approval established; accepted provenance/artifacts/installed/UAT/release gates remain distinct. |
| E03 | Installed-artifact acceptance | Exact x86 fresh install/upgrade/OTA/reboot/rollback and applicable APK/device qualification | No whole-row approval established; accepted provenance/artifacts/installed/UAT/release gates remain distinct. |
| E04 | UAT and sign-off | Integrated regression/soak, authorized installed parity and final operator UAT/release-owner handoff | No whole-row approval established; accepted provenance/artifacts/installed/UAT/release gates remain distinct. |
Inherited task map
T labels overlap requirements; they do not create a second completion denominator. Current task statuses require owner reconciliation, not adoption of historical ledger flags.
| Task | Scope |
|---|---|
| T00 | Provenance, baseline and requirements reconciliation |
| T01 | Shared contracts and risk review |
| T02 | Reproducible build and guarded delivery scaffold |
| T03 | Native identity and original UI preservation |
| T04 | Backstage assets and publishing UX |
| T05 | Stable film identity and distributed catalog |
| T06 | Discussion and social consistency |
| T07 | Cloud-aligned native/external checkout |
| T08 | Rental lifecycle, entitlement and expiry |
| T09 | Strict FIPS media and original player integration |
| T10 | Authorized replicas and availability |
| T11 | Monetary-state packaging and upgrade acceptance |
| T12 | Cloud recovery and fee regressions |
| T13 | Independent Cloud connectors |
| T14 | Public files and Mesh multi-file delivery |
| T15 | Shared media/private V4V and last artwork fix |
| T16 | Requests, Fleet and final connection UX |
| T17 | App latency, monitoring, HTTPS and AI setup |
| T18 | MeshCore interoperability and public message repairs |
| T19 | Firewall, tunnels and public routes |
| T20 | Lifecycle/container/app regressions |
| T21 | Terminal, developer contract and discovery UI |
| T22 | Integrated frozen-candidate qualification |
| T23 | Installed artifacts and final operator UAT |
| T24 | Release-owner handoff and metadata gap |
| T25 | Chunked ecash streaming and scoped allowance |
| T26 | Original zap UI, all supported rails and receipts |
| T27 | Networking Profits integration |
| T28 | Mesh rendering and replay UX investigation |
| T29 | Public guest IndeeHub isolation and external access |
Eight-app whole-app acceptance
| App | Remaining acceptance boundary |
|---|---|
| KithMoot | OPEN: Actual signer/private-room/media/Companion and managed lifecycle |
| Qortal | OPEN: Candidate provenance/review/compatible package, nonempty migration/rollback, gateway/bootstrap and installed lifecycle |
| Podsteadr | OPEN: Production provisioning/identity/bridge, lifecycle/ownership/migration, device/NAT/financial reconciliation and accepted provenance |
| Just Works | OPEN: Actual identity/business/import/LNURL and managed lifecycle |
| DATUM | OPEN: Miner/admin/service/reboot/configuration preservation |
| Gashboard | OPEN: Matching package, extension/mobile signing and device regression |
| Blossom | OPEN: Existing-data ownership/migration/rollback and managed lifecycle |
| Public Web Router | OPEN: Existing config/data, lifecycle and authorized route/TLS acceptance |
Scenario acceptance rules
Use the full families in Testing-Process.md, not only the latest blocker. For each scenario the owner must record source/artifact, real versus simulated dependencies, raw and outer verdict, exact names/skips, failure history and installed/device applicability. No unresolved mandatory scenario may be counted passed. This first curated matrix is scope-complete by ID, not yet evidence-complete by subscenario.