Skip to content

t3-golive: later switches refuse once fork features are on #529

Closed

Description

@scuttletoby

Problem. The go-live design (section 4.7) turns fork features on after day 0: agentSlots, then waitFor, then usagePacingGate: "advise". The kit's switch requires every fork feature to be off, in four places:

  • check (lib/golive/check.py _report): "fork features off" fails, so switch refuses before anything changes.
  • the switch's before step (switch.py _before): it raises if the stopped home's report has features on.
  • verify (switch.py _look): "fork features on" is a problem, so a verify on a home with features on can never pass and would go back with W1.
  • rehearse R3 (rehearse.py): the same check on the copy.

So the first switch works, but no later fork-to-fork update can go through t3-golive switch once any feature is on.

What a change needs (proposal).

  1. Replace "all off" with "unchanged": check records the live build's fork.featuresOn (the live server is a fork build from the second switch on), and before and verify require the same list, not []. The first switch keeps [], because the upstream live build has no fork report.
  2. The rehearsal must not act on the copy. With waitFor on, the rehearsal's server on the copy home could deliver waits or send messages. The rehearsal should start the copy with fork features forced off, by writing the copy's settings only (never the home's), and say so in its facts.
  3. Decide whether later updates use the kit at all, or upstream's own t3 update / the fork's automaticUpdates (fork Auto-update: server updates itself when quiet #5) once the fork build is live. If the kit stays the way, (1) and (2) are needed before the next fork release goes live.

State question. A rerun after features changed between check and before refuses, with nothing changed. A home with an empty or missing settings file decodes to all off and still passes.

Found while fixing the SSH-launch gap (golive-gap-handoff PR).

Activity

  1. added 2 commits that reference this issue on Nov 20, 2026
    1f98aee
    383a11d
  2. added 2 commits that reference this issue on Nov 21, 2026
    7bf6748
    439eaa6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions