Shared Plan Visibility
Plan Artifact In Every Preamble
The run made Gantry show scoped workers the durable plan source they can consult.
0 milestones 2 tasks 5 agents
2 plan 2 execute 1 review
97k peak context
28m 41s total 7m 37s per task
1m 47s plan 9m 32s execute 1m 53s review
10 edits 90 commands
codex harness
This run addressed a context problem in Gantry's own agent workflow. The durable plan artifact already existed as the source record for a build, but downstream workers could still receive a scoped task without an explicit pointer back to that source. The change put that pointer in the shared environment preamble, framed as context rather than new authority, and then routed the value through the run shapes that launch scoped workers.
How this walkthrough is structured
Feature
What did the run build and ship?
Current Gantry still persists a source-plan artifact and renders a plan-artifact line into worker preambles when a usable path exists.
Build
How did Gantry structure the work?
The run split the work between the shared preamble contract and the driver routing needed to make that contract true for scoped workers.
Shared Artifact Reference
2 agents 11m wall time 97k peak context
The environment renderer still has an optional plan-artifact field on its facts struct. When present, `compose_environment` emits a single line naming the artifact as the specification for the run; when absent, it omits the line. The wording remains in the common preamble path, not in role-specific prompt templates.
This sprint carried the common wording and data shape before any driver tried to supply paths. Its brief was deliberately narrow: add an optional reference to the shared environment preamble, keep the line absent when no artifact is available, and preserve role scope by presenting the artifact as orientation. The unit stayed green through review, which fits a boundary centered on one renderer and focused expectations.
Worker Path Routing
1 agents 4m 15s wall time 77k peak context
The current run engine resolves a source-plan anchor from the active unit first and falls back to the run root for child orchestration directories. Tests still cover a child worker receiving the root plan path rather than a missing nested file. Pattern execution also checks that the protected source-plan artifact is not modified by workers, so the pointer remains a read surface rather than a mutable work target.
This sprint consumed the preamble contract and was asked to prove path correctness across ordinary builds, child units, and map-style work. The ledger records it as already satisfied with a green gate, so the run did not leave a separate commit boundary for this slice. Its architectural boundary is still visible: once the common line existed, the remaining work was resolving the worker-visible anchor rather than changing prompt scope.