Implement the Stable Address, the derived Move and Infrastructure Intent #324

Activity

1. ExtraToast

   added

   type: featureNew user-facing or operator-facing capability.New user-facing or operator-facing capability.

   area: deployhomelab-deploy, deploy-v2, manifests, and rollout flow.homelab-deploy, deploy-v2, manifests, and rollout flow.

   priority: P2Medium; normal planned work.Medium; normal planned work.

   on Oct 9, 2026
2. ExtraToast

   added a parent issue on Oct 9, 2026

   • Change a shared provider without downtime: Stable Address, derived Move, Infrastructure model #320
3. ExtraToast

   added a commit that references this issue on Oct 9, 2026

   docs: specify the Stable Address, the derived Move and Infrastructure…

   ...

   25e210c
4. ExtraToast

   added sub-issues on Oct 9, 2026

   • Pin the facts a Move derives from: an engine image's version, the active Instance, and each engine's move method #330
   • Derive and render the Stable Address, and resolve every dependency coordinate to it #331
   • Declare availability on an engine Process #332
   • Derive a Move in layer 2, with a hand-written Postgres 16 to 17 example #333
   • Move an Application between Projects by declaring it in the new one first #334
   • Render a Move: its step Jobs, its move identity and policy for both Instances #335
   • Run a Move in the Release Gate and record it in ClusterState #336
   • Read Infrastructure Intent and generate the node contract from it #337
   • Navigate an Estate root for cross-file OCL in the model-driven implementation #338
   • Draw chapter 15's model, a Move's steps and the Stable Address #339
5. 4 remaining items

   Load more
6. ExtraToast

   marked this as blocked by 2 issues on Oct 12, 2026

   • Map: re-establish deploy-kit's goals, rewrite its spec, and order the work until the estate is handed over #341
   • Cut what the map cut and release package 1.0.0 #379
7. ExtraToast

   added 4 commits that reference this issue on Oct 21, 2026

   fix(model): only an engine with a move method needs its image's versi…

   ...

   5fe1a03

   feat(model): an images-lock entry without a version is refused

   ...

   b632b7f

   feat(model): an images-lock entry without a version is refused

   ...

   5d7d33c

   feat(model): an images-lock entry without a version is refused (#540)

   ...

   ce78178
8. ExtraToast

   removed a parent issue on Oct 23, 2026

   • Change a shared provider without downtime: Stable Address, derived Move, Infrastructure model #320
9. ExtraToast

   added a parent issue on Oct 23, 2026

   • Epic: every Project on the estate path, and the old path retired estate#202
10. ExtraToast

    marked this as blocking on Oct 23, 2026

    • Move Vault to secrets-system and hand secrets over to the estate path estate#209
11. github-actions

    added

    status: in-progressActively being worked.Actively being worked.

    on Oct 27, 2026
12. ExtraToast

    removed a parent issue on Oct 27, 2026

    • Epic: every Project on the estate path, and the old path retired estate#202
13. ExtraToast

    added a parent issue on Oct 27, 2026

    • Estate delivery: deploy with deploy-kit, pause and roll back, watch it from one dashboard #195
14. ExtraToast commented on Oct 27, 2026

    

    ExtraToast

    on Oct 27, 2026

    Last edited by ExtraToast

    ContributorAuthor

    More actions

    Resume here: landing the Move stack (updated 2026-10-27)

    State

    • Pin the facts a Move derives from: an engine image's version, the active Instance, and each engine's move method #330, Derive and render the Stable Address, and resolve every dependency coordinate to it #331 and Stable Address feat(model): derive and render the Stable Address, and point every alias at it #646 are merged. Sidecar volumes A sidecar cannot mount the Process's volumes or run before it #271 (feat(model): let a sidecar mount the Process's volumes it names, and run before it as an init step #651) is merged too.
    • The Move stack is on main: feat(model): derive a Move from a Process and its active Instance #648 (Derive a Move in layer 2, with a hand-written Postgres 16 to 17 example #333) as e81d8425, feat(model): render an open Move: its Instances, step Jobs and move identity #649 (Render a Move: its step Jobs, its move identity and policy for both Instances #335) as f00fc54e, feat(model): move an Application between Projects by declaring it in the new one first #650 (Move an Application between Projects by declaring it in the new one first #334) as 30bc5414.
    • Run a Move in the Release Gate and record it in ClusterState #336 is in delivery. Build the Postgres move method, and run the drills the new records rest on #340 is the maintainer's drill. Declare availability on an engine Process #332, Read Infrastructure Intent and generate the node contract from it #337, Navigate an Estate root for cross-file OCL in the model-driven implementation #338 and Flip the Stable Addresses of a Move that carries no data #667 (the flip for a stateless Move) come after 1.0.

    Next step: after 1.0.0: #667 (one flip image for every Move, decided 2026-10-27), then #332 and #337 as their notes say.

    Ledger numbers on main once all three land: REQ-112 for #648, REQ-113 for #649, REQ-114 for #651 (sidecars, already on main), REQ-115 for #650. The ledger's "holds N rows" line is 115 at the end.

    Landing one stacked PR, after the PR below it merges

    Run this in the PR's worktree. <old-base> is the parent's head SHA given above.

    git fetch origin main
    git rebase --onto origin/main <old-base>
    # Generated files: take main's copy, then regenerate.
    git checkout --ours -- spec/v1/examples spec/v1/schemas spec/v1/diagrams
    # docs/requirements.md: union the rows by hand, keep a single "holds N rows" line,
    # and renumber the citing test comments.
    # Test files where both sides add a describe block: keep both, and check the closing braces.

    Regenerate:

    • the descriptor and schemas: a throwaway regen.ts at the repo root, deleted afterwards, which writes descriptor(), projectIntentJsonSchema() and every PUBLISHED_SCHEMAS entry from ./src/index.ts;
    • the oracles: run test/model/resolution.test.ts, project-intent.test.ts and platform-intent.test.ts with an oracle setup file that writes the expected JSON;
    • the platform drawing: python3 scripts/diagrams/class-diagram.py 14-platform-intent out.drawio, then export it with draw.io (-x -f svg -e -b 10) to spec/v1/diagrams/14-platform-intent-model.drawio.svg. A 3-way merge cannot handle this file, which is one line.

    Then:

    • npm run verify must pass. Push only on success, with --force-with-lease=<branch>:<sha>.
    • gh pr merge <N> --auto --squash.
    • Change the PR body's first line from "Stacked on…" to "Rebased onto main…".
    • If CI mutation shards fail, list the survivors from the Stryker report artifacts and kill them with tests. An equivalent mutant gets a // Stryker disable next-line <Mutator> with a reason.

    Gotchas

    • Never git add -A with scratch scripts in the tree. A stray script once reached a pushed commit.
    • Mutation testing is incremental against main's baseline, so mutants on lines a PR never touched can resurface.
15. ExtraToast

    added a sub-issue on Oct 27, 2026

    • Flip the Stable Addresses of a Move that carries no data #667
16. ExtraToast commented on Nov 2, 2026

    

    ExtraToast

    on Nov 2, 2026

    ContributorAuthor

    More actions

    The derived Move is cut from this epic (maintainer, 2026-11-02). #336, #340 and #667 are closed as not planned, and #807 removes what #333, #334, #335 and #330 landed for it. The Stable Address, #332, #337 and #338 stay here.