You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The in-between tier (owner-identified, 2026-07-17): between server Servy deployment and the
beta.14 single-output consumer artifact — a Windows machine running the desktop window as a
native app (Desktop Frontend #840 artifacts) with its sidecars installed as Windows services
(Servy, shipped adapter #339) and Scheduled Tasks (PM-C), supervised by the OS + the PM control
plane, window connecting as a client over per-machine loopback discovery.
Why it's cheap: it is a composition of already-planned pieces — PM-19 compiles the process
graph to units (beta.12), the Servy deploy spine already ships install/uninstall/status verbs,
PM-C adds the task backend, #840 ships the window. This slice delivers the topology:
Graph compile split: resident sidecars → Servy services; cron-policy workloads → Scheduled
Tasks; window = client (fixed ports from the machine port registry).
gate: e2e on a Windows runner — install graph (services + ≥1 scheduled task) via CLI,
window client connects, task fires post-reboot, health via control plane, uninstall clean
gate: docs page — the three Windows tiers (thin-client / hybrid / single-output) and when
to choose each
Depends on: #510 (PM v1-min, beta.12), PM-C, #840 (window artifacts), PM-18 #529. Design source: PR #822 (rfc.md) + run .llm/runs/rfc-single-deployment--orchestrator/.
Part of #327.
The in-between tier (owner-identified, 2026-07-17): between server Servy deployment and the
beta.14 single-output consumer artifact — a Windows machine running the desktop window as a
native app (Desktop Frontend #840 artifacts) with its sidecars installed as Windows services
(Servy, shipped adapter #339) and Scheduled Tasks (PM-C), supervised by the OS + the PM control
plane, window connecting as a client over per-machine loopback discovery.
Why it's cheap: it is a composition of already-planned pieces — PM-19 compiles the process
graph to units (beta.12), the Servy deploy spine already ships install/uninstall/status verbs,
PM-C adds the task backend, #840 ships the window. This slice delivers the topology:
Graph compile split: resident sidecars → Servy services; cron-policy workloads → Scheduled
Tasks; window = client (fixed ports from the machine port registry).
v1 install path = prosumer/CLI (
netscript deploy …, elevation via the existing spine) —no .NET packaging dependency; the consumer-grade MSI variant of this topology folds into
feat(deploy): installers — scopes, least-privilege ACLs, journaled operations, port registry [SD-3] #833/feat(deploy): NetScript.Aspire.Packaging — .NET Aspire hosting integration (ATS-exported) for installer authoring #825 at beta.14.
Update posture: services/tasks update via the deploy spine (health-gated
up, PM-18); thewindow updates via the native tier (feat(sdk): robust programmatic auto-update — typed wrapper over Deno.autoUpdate + release client #841). The combined atomic transaction remains beta.14
scope — documented boundary, not pretended.
gate: e2e on a Windows runner — install graph (services + ≥1 scheduled task) via CLI,
window client connects, task fires post-reboot, health via control plane, uninstall clean
gate: docs page — the three Windows tiers (thin-client / hybrid / single-output) and when
to choose each
Depends on: #510 (PM v1-min, beta.12), PM-C, #840 (window artifacts), PM-18 #529. Design source: PR #822 (
rfc.md) + run.llm/runs/rfc-single-deployment--orchestrator/.