Skip to content

Turn on placement: what blocks it #902

Open

Description

@scuttletoby

placement and placementNeeds cannot be switched on on any machine yet.

What blocks it:

  1. The settings themselves (P2, placement P2: placement and placementNeeds setting contracts #798) were merged after the newest release (0.1.12-nightly.20261121.5051.fork.1), so no running build knows them.
  2. Nothing reads them yet: the facts each machine reports (P3, PR Placement P3 (facts out): t3_environment_read returns hostResources and placement #820) are in review, and the wiring that places delegated work by the rules (later rows) is not built. The pure rule engine (P5, placement P5: pure rule engine, hard rules H1 to H9 and upstream's rank #787) is merged but not used.
  3. Follow-ups: placement: P2/P6 follow-ups from the P5 rule engine reviews #794, Placement P2 follow-ups for P4/P5 (from the #798 review) #805, Placement P3 minors from the #820 lens #821.
  4. Machine facts (labels such as gpu or owner-logins, a factsCommand) must come from each machine's private machine file, not from this repository; none is written yet.

Done when: a release carries P2, P3 and the wiring; each machine's labels are in its private machine file; "mode": "advise" on one machine logs where it would place a test delegation and changes nothing (advise before enforce).

Way back: "placement": {"mode": "off"} and remove placementNeeds.

🤖 Generated with Claude Code

Activity

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