Known Task Rail
The Tasks Rail Before Work Starts
A run that made readable nested task lists visible before their work began.
1 milestones 8 tasks 28 agents
2 plan 8 execute 12 review
202k peak context
145k median execute
5h 58m total 15m 7s per task
4m 4s plan 1h 19m execute 43m 9s review
138 edits 1k commands
codex harness
2.8M tokens in 248.7k tokens out
The Known Task Rail run changed how Gantry exposes task lists and names task cards. Its brief covers preview announcements for readable nested lists, the boundary between previews and live enumeration, the Tasks rail, fleet progress, release rehearsal, and per-task card headlines. The digest records one milestone, although its brief describes the work at a broad engine boundary. The visible commit isolates the matching published pattern specification; the current tree also carries the preview event, the display projection, fleet exclusion, and task-aware card-headline code named by the brief.
How this walkthrough is structured
Feature
What did the run build and ship?
The current tree documents task-list directories by container task path and contains the preview and card-headline behavior the milestone describes.
Build
How did Gantry structure the work?
One milestone gathered task-list previews, their live-enumeration boundary, and task-aware card names into a single engine change whose gate required a retry.
Milestone 1
Known Task Rail
8 tasks 25 agents 2h 39m wall time 202k peak context
The recorded commit preserves the published pattern specification's statement that the run stores the task-list directory declared for each container task path. The live tree contains `TaskListAnnounced` with a preview field, display handling for previews, fleet logic that excludes previewed lists, and task-title-aware headline resolution. Those current files confirm the capability described by the brief, but the record's sole measured commit isolates only the specification change rather than each engine contribution.
The milestone gave one agent the full boundary between display-only task-list previews and live enumeration. Its brief made the distinction explicit: previews must not alter run shape, task-list directory state, progress, or the ledger, while real enumeration remains authoritative. The same unit joined that boundary to the Tasks rail, release rehearsal, fleet records, and task-specific card headlines. The ledger records a red run-scoped gate after the milestone body completed, followed by a green retry; the run facts do not attribute that difficulty to a narrower unit.