Skip to content

feat: mission.target.toml — declarative fleet target state (consumed by mission.reconcile, #116)#117

Open
gHashTag wants to merge 1 commit into
mainfrom
feat/mission-target-toml
Open

feat: mission.target.toml — declarative fleet target state (consumed by mission.reconcile, #116)#117
gHashTag wants to merge 1 commit into
mainfrom
feat/mission-target-toml

Conversation

@gHashTag
Copy link
Copy Markdown
Owner

@gHashTag gHashTag commented May 3, 2026

Goal

Operator-canonical declarative target state for the entire IGLA RACE fleet (7 Railway accounts, 4 RunPod GPU pods, queue invariants, acceptance gates). Lives in repo root, versioned, auditable.

Today: human-readable spec. When mission.reconcile ships, this file becomes authoritative — operator edits the TOML, one MCP call mutates the live fleet to match.

Sections

[fleet]                  — 7 accounts, 15 canonical Railway lanes
[fleet.runpod]           — P5 GPU lane spec (4 A40 pods, $20 budget)
[queue]                  — PhD-DAY wave, Plan-C-Lite slice
[queue.plan_c_lite]      — 14 T1+T2 formats, Fibonacci seeds, phi-LR ladder
[queue.champion_battery] — 81K-step runs of 7 best configs × 5 seeds
[purge]                  — pre-wave hygiene (NaN, zombie, transient retry)
[health]                 — heartbeat TTL, emit-rate, champion-beat notify
[acceptance.phd_lite]    — PhD-defense acceptance gate (1320 runs, 90% done, Pareto, slope-test)

Why now

Today's session has three implicit "target states" living in different ad-hoc Python scripts and SQL hygiene blocks. Consolidating them in one TOML lets the operator:

  • Diff today's wave against tomorrow's by editing one file
  • Bisect regressions by checkpointing the file with each wave
  • Future-proof for mission.reconcile: zero rewrite when it ships, just hook the TOML parser

Acceptance

R5 honesty

This PR ships the TOML. It does NOT yet ship the parser or the reconciler — those are tracked in #116 Phase P6/P7. Operator can read this file today; agent will consume it tomorrow.

References

🌻 phi^2 + phi^-2 = 3 · TRINITY · DECLARATIVE · NEVER STOP

Single source of truth for what the IGLA RACE fleet should look like.
Consumed by the upcoming `mission.reconcile` MCP verb (trios-railway#116
follow-up comment 4365612774) in Terraform plan/apply pattern.

Sections:
  [fleet]                — 7 accounts, 15 canonical Railway lanes
  [fleet.runpod]         — P5 GPU lane spec (4 A40 pods, $20 budget)
  [queue]                — PhD-DAY wave, Plan-C-Lite slice
  [queue.plan_c_lite]    — 14 T1+T2 formats, Fibonacci seeds, phi-LR ladder
  [queue.champion_battery] — 81K-step runs of 7 best configs × 5 seeds
  [purge]                — pre-wave hygiene rules
  [health]               — heartbeat TTL, emit-rate invariants, champion-beat notify
  [acceptance.phd_lite]  — PhD-defense acceptance gate

Today the file is operator-readable; when `mission.reconcile` lands it
becomes authoritative — operator edits this TOML, one MCP call mutates
the fleet to match.

Anchor: phi^2 + phi^-2 = 3.

Refs:
- EPIC trios#446
- MCP v3 O(1) design trios-railway#116
- 6-lane canon trios#445
- 64-format catalog trios-railway#115
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants