Epic: deployment architecture — services layer + deploy tool (tracking) #5765

Activity

1. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1451
2. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   Issue map for this epic (filed 2026-11-04 with the design PR #5764):

   • deploy tool v1 (registry + systemd generations) — deploy tool v1: target registry (deployTargets) + systemd generation activation #5766
   • deploy tool: Cloudflare target class — deploy tool: Cloudflare target class — generalize the <name>-deploy apps to all Workers #5767
   • M1: route-proxy hand unit → target — Migration M1: route-proxy from hand unit to services-layer deploy target #5768
   • M2: fleet three, one declaration — Migration M2: one declaration for the fleet three (laptop-agent, secrets-broker, queue-broker) #5769
   • M3: sandbox quota-recorder + generic restorer — Migration M3: sandbox quota-recorder as first sandbox deploy target + generic unit restorer #5770
   • M4: pm-stack off the checkout — to be filed when M1–M3 land (per design §7)
   • Containers: Nix-build audit — Containers: Nix-build audit — mcpx Containerfile, duplicate lab-ops Dockerfile, amd-crd definition-or-waiver #5771
   • VMs: declarative guests — VMs: declarative guest definitions (nixvirt / microvm.nix) + mutable carve-out list #5772

   Design doc: doc/2026-11-04_deployment-architecture-services-layer.md (PR #5764).
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane code-g
   • Session / ID: task 10171
   • Found via: queue claim
   • Task: Triage issue Epic: deployment architecture — services layer + deploy tool (tracking) #5765 (epic: deployment architecture tracking) — direct execution lane; mapping the epic against its children and current state, then routing.
5. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage verdict (task 10171, lane code-g, 2026-11-05)

   Verdict: epic #5765 is live and almost fully decomposed. Design PR #5764 is MERGED (2026-11-05T01:48Z). The epic's checkboxes are all still unticked, but the child issues exist — the boxes, not the work, are what is stale.

   Filed and OPEN (verified by search this run):

   • Deploy tool v1 (registry + systemd generations): deploy tool v1: target registry (deployTargets) + systemd generation activation #5766
   • Deploy tool Cloudflare target class: deploy tool: Cloudflare target class — generalize the <name>-deploy apps to all Workers #5767
   • M1 route-proxy: Migration M1: route-proxy from hand unit to services-layer deploy target #5768
   • M2 fleet three: Migration M2: one declaration for the fleet three (laptop-agent, secrets-broker, queue-broker) #5769
   • M3 quota-recorder + restorer: Migration M3: sandbox quota-recorder as first sandbox deploy target + generic unit restorer #5770
   • VMs declarative guests: VMs: declarative guest definitions (nixvirt / microvm.nix) + mutable carve-out list #5772

   Missing:

   • Containers: Nix-build audit (mcpx, lab-ops duplicate Dockerfile, amd-crd) — no dedicated issue found. (impl(lab): generic containers for ID and fleet purposes (Nix-built) #6076 covers generic lab containers; it is not this audit.)
   • M4 pm-stack off the checkout — correctly unfiled: the epic itself says "filed when M1–M3 land", and M1–M3 (Migration M1: route-proxy from hand unit to services-layer deploy target #5768/Migration M2: one declaration for the fleet three (laptop-agent, secrets-broker, queue-broker) #5769/Migration M3: sandbox quota-recorder as first sandbox deploy target + generic unit restorer #5770) are still open. No action until they land; the epic is the reminder.

   Routing: one follow-up triage task enqueued to file the containers Nix-build audit issue in the epic's terms and tick/link the epic's program list to the child issues above, so the tracking page matches reality. Nothing here needs Drew; the program rules on the epic (independent reversibility, no system-switch dependency, additive flake change only, secrets by name) bind all children as written.

   Epic stays open as the tracker.
6. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   and removed

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   on Nov 5, 2026
7. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · triage complete (task 10171, lane code-g)

   • Follow-up enqueued: task 10492 (triage, repo-health-code-pilot) to file the Containers Nix-build audit issue and sync this epic's checklist links.
   • Epic stays open as tracker; labels set to queue/queued for task 10492.
8. dezren39

   added

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
9. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane code-u
   • Session / ID: task 10492
   • Found via: queue claim (direct execution lane)
   • Task: Triage issue Epic: deployment architecture — services layer + deploy tool (tracking) #5765 (tracking epic) — verify the design landed and every programme item is filed and tracked.
   • Expectation: s — triage findings + child map recorded on issue Epic: deployment architecture — services layer + deploy tool (tracking) #5765.
   • Links: task 10492 (repo-health-code-pilot)
10. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · triage findings (task 10492, lane code-u, direct lane)

    Verdict: HEALTHY TRACKING EPIC — design landed, programme fully decomposed into tracked child issues. Nothing sits silently; no follow-up owed by this triage.

    Evidence (fresh, 2026-11-05):

    • Design source: PR doc: deployment architecture — a services layer outside the system switch #5764 (doc/2026-11-04_deployment-architecture-services-layer.md) is MERGED (2026-11-05T01:48Z).
    • Every programme checkbox on this epic maps to a filed, open, queue-tracked child issue:
      • deploy tool v1 (registry + systemd generations) → issue deploy tool v1: target registry (deployTargets) + systemd generation activation #5766 (already triaged)
      • deploy tool: Cloudflare target class → issue deploy tool: Cloudflare target class — generalize the <name>-deploy apps to all Workers #5767
      • M1: route-proxy hand unit → target → issue Migration M1: route-proxy from hand unit to services-layer deploy target #5768
      • M2: fleet three, one declaration → issue Migration M2: one declaration for the fleet three (laptop-agent, secrets-broker, queue-broker) #5769 (already triaged)
      • M3: sandbox quota-recorder + generic restorer → issue Migration M3: sandbox quota-recorder as first sandbox deploy target + generic unit restorer #5770 (already triaged)
      • Containers: Nix-build audit → issue Containers: Nix-build audit — mcpx Containerfile, duplicate lab-ops Dockerfile, amd-crd definition-or-waiver #5771
      • VMs: declarative guests → issue VMs: declarative guest definitions (nixvirt / microvm.nix) + mutable carve-out list #5772
    • The one unfiled item is deliberate: M4 (pm-stack off the checkout) is specified on this epic as "filed when M1–M3 land" — correctly absent today, and this note is its named trigger: when issue Migration M1: route-proxy from hand unit to services-layer deploy target #5768, issue Migration M2: one declaration for the fleet three (laptop-agent, secrets-broker, queue-broker) #5769, and issue Migration M3: sandbox quota-recorder as first sandbox deploy target + generic unit restorer #5770 close, M4 gets filed referencing this epic. That is a SET-REMAINDER recorded here, not a gap.
    • Programme rules (independently reversible migrations; no system switch required to land; only additive flake change; secrets by name from the brokers) are stated on the epic and bind the children.

    This triage (task 10492) completes as triaged. The epic stays open as the tracking record until its children close; progress belongs on the child issues, not here.
11. dezren39 commented on Nov 5, 2026

    

    dezren39

    on Nov 5, 2026

    MemberAuthor

    More actions

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), lane code-u
    • Session / ID: task 10492
    • Found via: queue claim (direct execution lane)
    • Task: Triage of issue Epic: deployment architecture — services layer + deploy tool (tracking) #5765 complete — design PR doc: deployment architecture — a services layer outside the system switch #5764 merged, all seven actionable programme items filed as issue deploy tool v1: target registry (deployTargets) + systemd generation activation #5766–VMs: declarative guest definitions (nixvirt / microvm.nix) + mutable carve-out list #5772 and queue-tracked, M4's filing trigger (M1–M3 closure) recorded on the epic. No follow-up enqueued.
    • Expectation: done — triage outcome exists.
    • Links: task 10492 (done, outcome triaged), children issue deploy tool v1: target registry (deployTargets) + systemd generation activation #5766, issue deploy tool: Cloudflare target class — generalize the <name>-deploy apps to all Workers #5767, issue Migration M1: route-proxy from hand unit to services-layer deploy target #5768, issue Migration M2: one declaration for the fleet three (laptop-agent, secrets-broker, queue-broker) #5769, issue Migration M3: sandbox quota-recorder as first sandbox deploy target + generic unit restorer #5770, issue Containers: Nix-build audit — mcpx Containerfile, duplicate lab-ops Dockerfile, amd-crd definition-or-waiver #5771, issue VMs: declarative guest definitions (nixvirt / microvm.nix) + mutable carve-out list #5772
12. dezren39

    removed

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 5, 2026
13. github-actions

    assigned

    dezren39

    on Nov 5, 2026
14. developing-today commented on Nov 5, 2026

    

    developing-todayBot

    on Nov 5, 2026 – with developing.today

    Contributor

    More actions

    Agent note — future M4 issue must carry the ownership-handoff acceptance (from issue #6251)

    Per issue #6251, the M4 acceptance in doc/2026-11-04_deployment-architecture-services-layer.md §7 now includes an explicit Home Manager unit-ownership handoff for the PM units declared under home-manager.users in nixos/services/pm-stack/default.nix (declaration removal or a durable override in the proving change) plus post-activation survival verification. The future M4 implementation issue filed under this epic must carry that same handoff + post-activation acceptance.