Release Planning
App Version Map
The path from current internal build to a paid beta version, then a future app-store/mobile companion. Desktop paid beta remains the shipping target.
Editable Version Decisions
Full collaboration formChecking command-center API...
Current Version State
Version Roadmap Board
This is the working release ladder the daily agents read before cutting builds or shifting work toward mobile.
| Lane | Version | Ship Decision | Must Be True | Owner |
|---|---|---|---|---|
| Internal alpha | 0.1.0-alpha.76 | Keep for internal QA and command-center builds | Clean build, release evidence, command center, billing shell, consent gates, paid-feature gates, privacy controls, and typed IPC stay green | Codex |
| Paid beta candidate | 0.1.0-beta.1 | Cut only after live-money blockers close | Business identity, price/cap, support roundtrip, hosted billing backend, Stripe test/live rehearsal, policies, trusted installer path, and cloud dashboard are ready | User + Codex |
| Reliability beta | 0.2.0 | Follow paid beta feedback | Computer-control regression tests, listen/pause behavior, diagnostics, crash handling, updater plan, support macros, and visual evidence improve from beta usage | Codex |
| Public launch | 1.0.0 | Launch when paid beta is stable | All P0 blockers closed, billing/support/legal paths proven, release notes and rollback path current, marketing assets match the app, and customer onboarding is repeatable | User + Codex |
| Mobile companion | Future app | Map now, build after desktop paid beta gates | Cloud account/auth, account model, app-store privacy disclosures, support process, policy updates, and companion feature boundary are approved | Codex queued |
0.1.0-beta.1 Paid Beta Gate
- Do not change
package.jsonto beta until the deployability verdict is no longerNO_GO_LIVE_MONEY. - Use this page as the release candidate intake form for publisher name, beta distribution, notes, and mobile boundary decisions.
- Run
npm run test:app-version-roadmap,npm run test:release-package, andnpm run build:cleanbefore treating a candidate as shippable.
Mobile Companion Boundary
- Allowed now: define account/auth needs, cloud data shape, store-review checklist, and companion UX scope.
- Blocked now: store submission, mobile billing, mobile customer promises, or anything that weakens the desktop paid-beta launch path.
- The companion app must use the cloud command-center/account model instead of storing launch operations only on this computer.
Daily Version Agent Queue
| Agent | Daily Check | Writes Back To Dashboard |
|---|---|---|
| Release Ops | Version in package metadata, release notes, known issues, checksums, signing/trust decision, and rollback path agree | Release package page, appVersion state, QA matrix |
| Product Program | Saved user decisions change beta scope, pricing, cloud, support, legal identity, or version target | Deployability queue, app-version page, next actions |
| Cloud Platform | Cloud dashboard, Worker API, D1/R2, and Access decisions are ready enough to support desktop beta and later companion app | Cloud page, handoff readiness, app companion boundary |
| Marketing Visuals | Launch screenshots, demo storyboards, app-store style visuals, and public claims match the current version | Visuals page, launch site, marketing page |
Version Targets
| Version | Purpose | Must Include | Status |
|---|---|---|---|
| 0.1.0-alpha.76 | Current internal command-center + billing integration alpha | Billing server, activation shell, consent/data controls, paid gates, high-impact approval, typed IPC, policy packet | Current |
| 0.1.0-beta.1 | First paid beta candidate | Stripe test/live readiness, license activation, support path, signed/trusted installer path, privacy/terms | Blocked |
| 0.2.0 | Reliability beta | Fixed action/interrupt tests, diagnostics, stronger security gates, onboarding | Planned |
| 1.0.0 | Public paid launch | All P0 gates closed, real support, policy review, update path, stable pricing | Future |
| Mobile companion | Future app companion after paid desktop beta | Cloud account, account auth, support policy, store review materials, privacy updates | Mapped |
Version Rules
- No paid beta version is cut until the app metadata, release notes, support path, billing backend, and signing/trust path match the intended beta release.
- Desktop paid beta ships first. Mobile/app-store work is tracked here so it is ready without distracting from the release gate.
- Every paid candidate needs release notes, known issues, checksum/signing notes, and rollback path.
- Version status must be updated from the Collaboration page when publisher/release channel decisions are made.
Roadmap Source
NyrA App Version Roadmap
Scope: NyrA Swarm Little Buddy desktop paid-beta path, with a future mobile companion mapped but not allowed to outrank desktop launch blockers.
This file is the source text rendered into the command center App Version page. It is meant to be read by the daily build agents before any release label, package version, beta scope, or mobile-app work changes.
Version Ladder
| Lane | Version | Decision | Required Evidence |
|---|---|---|---|
| Internal alpha | 0.1.0-alpha.76 |
Keep as the current internal QA and command-center build line. | Clean build, release package evidence, command-center state, billing shell, consent controls, paid gates, high-impact approvals, typed IPC, policy drafts, Android hosted bridge proof, Android visible-label phone control, phone-control capability audit, swarm route transparency, visible best-model scorecard, and support diagnostics remain green. |
| Paid beta candidate | 0.1.0-beta.1 |
Cut only after live-money blockers close. | Legal/business identity, monthly price, hosted AI cap, support ticket roundtrip, hosted billing backend, Stripe test/live rehearsal, policy review, trusted installer path, and cloud dashboard readiness. |
| Reliability beta | 0.2.0 |
Use paid beta feedback to harden reliability. | Voice trigger/pause behavior, computer-control regression evidence, diagnostics, crash handling, updater plan, support macros, and product screenshots match the shipped app. |
| Public paid launch | 1.0.0 |
Launch only after beta proves repeatable onboarding and support. | All P0 blockers closed, signed or store-trusted release path, customer support process, legal/accounting review, stable pricing, rollback path, and marketing visuals that match the product. |
| Mobile companion | Future app | Map now, build after desktop paid beta gates are closed. | Cloud account/auth model, account data shape, app-store privacy disclosures, support process, policy updates, and explicit companion feature boundary. |
Beta Cut Rules
- Do not change
package.jsonfrom0.1.0-alpha.76to0.1.0-beta.1while the deployability verdict isNO_GO_LIVE_MONEY. - Do not ship a paid beta without current release notes, known issues, checksum/signing notes, install notes, support path, and rollback instructions.
- Do not expose live checkout until the billing backend, Stripe webhook, Customer Portal, support inbox, public policies, domain, and legal/accounting review are ready.
- No mobile companion work can outrank desktop paid-beta blockers.
- The mobile companion must rely on the cloud account/dashboard model, not local files stored only on this computer.
Daily Agent Checks
| Agent | Check | Dashboard Output |
|---|---|---|
| Release Ops | Package version, app metadata, release notes, known issues, checksums, signing/trust decision, and rollback path agree. | App Version, Release Package, QA Matrix |
| Product Program | Saved user decisions change beta scope, pricing, cloud, support, legal identity, or version target. | Deployability, Next Actions, App Version |
| Cloud Platform | Cloud dashboard, Worker API, D1/R2, Access, and state sync can support desktop beta and later companion app. | Cloud, Handoffs, App Version |
| Marketing Visuals | Screenshots, demo storyboard, launch copy, and future app-store style visuals match the current shipping version. | Visuals, Launch Site, Marketing |
Handoffs Needed Before Beta
| Handoff | Owner | Dashboard Field |
|---|---|---|
| Publisher/legal name | User | appVersion.publisherName and decisions.businessName |
| Beta distribution path | User + Codex | appVersion.betaDistribution and decisions.releaseChannel |
| Code-signing or store-trust path | User + Codex | decisions.codeSigningDecision |
| Support inbox roundtrip | User | billingRehearsal.supportInboxConfirmed |
| Hosted billing backend URL | User | billingRehearsal.backendBaseUrl |
| Cloud dashboard/account model | User + Codex | cloudMigration.* |
| Mobile companion boundary | Codex | appVersion.mobileCompanionBoundary |
Current Decision
Desktop paid beta is first. The future app version is mapped here so cloud, account, support, policy, and visual choices do not have to be rebuilt later, but no app-store/mobile promise should be made until the desktop paid beta can be deployed and supported.