3.4 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.
Release plan
Fixed scope
Retain all 48 requirement IDs: IndeeHub A01–A13 and platform B01–B10, C01–C10, D01–D11, E01–E04. The platform lane has 35 IDs and eight apps: KithMoot, Qortal, Podsteadr, Just Works, DATUM, Gashboard, Blossom and Public Web Router. App rows are acceptance obligations, not eight additional closed requirements. The inherited T00–T29 task map is a cross-lane work breakdown, not additional scope. See matrix.
Dependency order
- Reconcile provenance, requirements, existing dirty work and accepted component pins (T00); review shared contracts/risks (T01); establish reproducible artifacts and guarded delivery (T02).
- IndeeHub identity/Backstage/catalog precede authenticated checkout; checkout and recovery precede entitlement/player qualification. Publication must retain private-master and account isolation. First invoice, lost reply, withdrawal and restart must preserve one logical original operation.
- Connection UX precedes public files and private multi-file sharing. Cloud and native-identity dependencies remain separate from isolated provider fixtures.
- Finish coherent source/integration slices, mandatory regressions and independent review before package/installed acceptance. Test nonempty migration and rollback, not only fresh state.
- Freeze the integrated candidate (T22); qualify exact installed artifacts and operator scenarios (T23); hand off to the release owner (T24). B10 artwork remains the last feature-work correction after the other lanes; actual-device acceptance remains required before full closure. This does not impose a new blanket physical-acceptance prerequisite on independent source work.
Guarded delivery groups
| Group | Scope | Required boundary |
|---|---|---|
| Y1 | Identity/Backstage; diagnosed Mesh rendering slice only | Provenance, contracts, artifact and applicable identity/asset tests |
| Y2 | Publication/catalog/shared discussion | Prior dependencies; separate public-event authority |
| Y3 | Checkout/rentals/zaps/FIPS | Financial/security review, recovery and explicit spend authority where needed |
| Y4 | Chunked ecash/profits/durable update/availability | Monetary preservation, budget and replica qualification |
| Y5 | Cloud/connectivity/system/developer slices | Slice-specific dependencies, not an unchecked omnibus |
| Y6 | Radio/routes/sharing | Hardware/network changes separately authorized |
| Y7 | Background media and last artwork correction | Actual supported devices |
| Final | Frozen integrated backend/UI/apps/APK | All mandatory gates and explicit operator/release-owner sign-off |
Grouping is not deployment permission. Do not expose enabled mock payments or incompatible half-updated schemas. Blocked capacity/review/device dependencies block only dependent work, not all source implementation.
Timing and completion
Record attributable full-agent elapsed including investigation/failures separately from build/test runner duration and unknown queues. Use comparable qualified exits only; no historical countdown, human-hour multiplier or test-count percentage. External review, device, provenance and environment waits remain explicit. Completion requires the agreed installed/operator outcomes, not healthy containers or a green isolated suite.