Reader Naming Cleanup
Reader-Oriented Source Names
A behavior-preserving cleanup that made Gantry's project vocabulary readable in code and conventions.
0 milestones 3 tasks 8 agents
3 plan 3 execute 4 review
161k peak context
32m 39s total 8m 51s per task
3m 14s plan 8m 27s execute 6m 38s review
7 edits 146 commands
codex harness
This run cleaned up source names that made Gantry harder to read than it needed to be. The plan was not to change how runs behave, where files live, or what users see on the command line; it was to make project-specific concepts spell themselves out for the next person or fresh agent reading the code.
The work first made the rule explicit, then renamed local domain types, then widened the same discipline across orchestration-related identifiers. Current source has been reorganized since the run, especially around the build driver, but the convention and the full-word vocabulary are still visible in the live tree.
How this walkthrough is structured
Feature
What did the run build and ship?
The current tree still tells readers to spell out Gantry domain terms, and the live code keeps the major type and orchestration names in full-word form while preserving persisted run layout.
Build
How did Gantry structure the work?
The run treated naming as a behavior-preserving dependency chain: document the rule, make the bounded type renames canonical, then sweep the broad orchestration surface after review tightened the remaining work.
Reader Naming Rules
4 agents 3m 59s wall time 51k peak context
The convention still stands in the repository root guidance. It tells contributors to write project-specific domain words in full, gives `BuildContext` and `orchestration_dir` as the preferred forms, and keeps everyday locals such as `ctx`, `sha`, and `cfg` as acceptable shorthand. The old mirror file named by the commit is no longer present, so the durable feature is the surviving project convention rather than a separate agent prompt surface.
This sprint carried the policy, not the implementation rename. Its brief made the unit small enough for a fresh agent: update project conventions so future source edits could distinguish reader-hostile project clips from ordinary programming shorthand. The run record shows this work was run again after the local type sprint triggered a re-plan, but it did not need a repair or recovery. That boundary matters because the convention had to remain consistent with the source cleanup that followed it.
Local Type Renames
2 agents 8m 51s wall time 91k peak context 1 replan
The live tree still carries the main results, though later refactors moved much of the build driver out of the original paths. `TemplateSubstitutionError` is the map unit error type used by the map gate, `HarnessCapabilities` remains the harness capability surface, `CurrentUnitCursor` names the stats cursor, and gate paths use `should_abort` for stop predicates. `BuildContext` still appears as the documented name for the build context, but the current run engine has since been reshaped enough that this sprint's source edits are partly absorbed into newer structure.
This was the bounded source rename before the wide orchestration pass. The brief named concrete local concepts: build context, template substitution errors, abort predicates, the unit cursor, and harness capabilities, while preserving idiomatic local variables and the abort latch. It passed its gates, then review requested a re-plan before the next slice. That makes this unit the hinge of the run: it established canonical type names the later orchestration sweep had to consume without reopening their meaning.
Orchestration ID Renames
2 agents 8m 59s wall time 161k peak context
The full-word orchestration vocabulary is now the live code's norm. Runtime naming, run discovery, worktree reset exclusions, MCP run metadata, process reporting, and repair paths use forms such as `orchestration_dir`, `orchestration_rel`, and `root_orchestration_rel`. A few `orch` locals remain in tests and survey fixtures, and persisted compatibility strings are intentionally protected, but the source APIs users of those modules read now spell out the Gantry domain term.
The final sprint was the broad sweep across source identifiers, comments, helper names, and documentation links. It depended on the previous sprint's contract because orchestration names passed through build, run, registry, worktree, MCP, and test code. Its done condition was strict about preserving `.gantry` layout, serialized data, command output, and user-facing messages, so the hard part was separating source vocabulary from stable external strings. The run closed this slice green, without a recorded repair.