Epic — Unified Single-Runtime Deployment
Part of #327 (deployment umbrella). No closing keyword — closes by hand when children land.
Position NetScript as a direct contender to Next.js/Nuxt: one deploy output for an entire app (web + services composed in-process), runtime-agnostic via Nitro v3 (nitro.build) with its adapter surface (database, cache, KV, tasks, WebSocket, lifecycle, cloud deploy presets). Teams scale by splitting resources into "macro services" — fine-grained vertical & horizontal scaling with mixed deploy targets — on the SAME app model as multi-process NetScript; divergence only at composition (PR #822 RFC §3/§D composition contract).
Origin: netscript-start "frontend RFC: unified". Owner-ratified direction 2026-07-17: this is its own epic, NOT desktop-tied — the desktop in-process window is merely one target. Supersedes the #349 WATCH posture (2026-07-03 assessment predates live Nitro v3 docs).
First action: the seed run (see the plan sub-issue) — Nitro v3 validation, adapter mapping vs shipped @netscript adapters, saga/oRPC/Fresh-2 fit, epic decomposition, composition contract, supersession map. Sub-issue set is filed by the seed's stage-H, not here.
Absorbed pending seed (re-homed from Tier-4 desktop, milestones → Backlog/Triage): #451 (in-process link adapter), #453 (single-writer relocation), #454 (single-process mode), #455 (offline sync).
Shared foundations consumed: packaging/install/update substrate (#456/#457 + the .NET Aspire packaging integration), composition-modes contract.
Milestone: 0.0.1-beta.13 — the implementation marquee after PM (#510) ships beta.12. Design source: PR #822 (rfc.md + plan.md rev 10, 9-cycle adversarial trail) in .llm/runs/rfc-single-deployment--orchestrator/.
Epic — Unified Single-Runtime Deployment
Part of #327 (deployment umbrella). No closing keyword — closes by hand when children land.
Position NetScript as a direct contender to Next.js/Nuxt: one deploy output for an entire app (web + services composed in-process), runtime-agnostic via Nitro v3 (nitro.build) with its adapter surface (database, cache, KV, tasks, WebSocket, lifecycle, cloud deploy presets). Teams scale by splitting resources into "macro services" — fine-grained vertical & horizontal scaling with mixed deploy targets — on the SAME app model as multi-process NetScript; divergence only at composition (PR #822 RFC §3/§D composition contract).
Origin: netscript-start "frontend RFC: unified". Owner-ratified direction 2026-07-17: this is its own epic, NOT desktop-tied — the desktop in-process window is merely one target. Supersedes the #349 WATCH posture (2026-07-03 assessment predates live Nitro v3 docs).
First action: the seed run (see the plan sub-issue) — Nitro v3 validation, adapter mapping vs shipped
@netscriptadapters, saga/oRPC/Fresh-2 fit, epic decomposition, composition contract, supersession map. Sub-issue set is filed by the seed's stage-H, not here.Absorbed pending seed (re-homed from Tier-4 desktop, milestones → Backlog/Triage): #451 (in-process link adapter), #453 (single-writer relocation), #454 (single-process mode), #455 (offline sync).
Shared foundations consumed: packaging/install/update substrate (#456/#457 + the .NET Aspire packaging integration), composition-modes contract.
Milestone: 0.0.1-beta.13 — the implementation marquee after PM (#510) ships beta.12. Design source: PR #822 (
rfc.md+plan.mdrev 10, 9-cycle adversarial trail) in.llm/runs/rfc-single-deployment--orchestrator/.