Chronicler · human view
The job rail: one spine, three hosts, and the fortnight that built it
How does one bounded piece of work travel from REQ to main, and what does each successful stage actually establish?
- Dispositionlive. Human's 2026-09-05 reading that the pipeline was nearly done remains part of its history. Subsequent work improved review, landing checks and the Codex route; it did not…
- arc
library/work/job-rail/README.md
What the account is
A live library arc for the job rail: one spine, three hosts, and the fortnight that built it. Observed at commit 86902d70 with PATCH-354's repair verified at 761a242; it launches no provider job. Disposition stays live — Human's 2026-09-05 sense that the pipeline was nearly done is history, not certification of the whole lifecycle.
Where the work stands
The spine can make a candidate, submit it to independent Eyes, and record the result. Moving an accepted candidate onto main still needs the holder's integration work. Native-session preservation and returning attention to the actual creator remain further claims with their own evidence. SQLite owns lifecycle and review; Git owns exact source.
Five boundaries on the table
The export's boundary table keeps distinctions visible: Scope and contract (REQ-429 and REQ-448 fulfilled), Candidate and review (identity separate from Eyes), Landing (REQ-449 fulfilled; REQ-358 deferred; PROP-312 open), Codex route (REQ-451 fulfilled with FIND-1584 limits), and Cross-host policy (shared ingress exists; PROP-315 still open).
Why the rail changed
Four joined changes: transport became host-specific behind shared ingress; REQ and PATCH acquired shared lifecycle machinery in the shop job path; candidate identity moved to Git commit/tree plus overlay rather than physical disk bytes; and the worker's packet began to describe the bench it actually receives (REQ-410–412, REQ-448).
Three hosts, distinct proofs
Codex, Claude, and Grok each carry live pins with named limits — not a standing certification of all hosts. Codex has the newer MCP specimen REQ-451 and PATCH-354's binder repair. Claude Eyes gained structured verdict capture (REQ-439) while Hands still has no product schema. Grok classifies ACP completion as protocol_success and still lacks a model witness on the callback.
Landing stays the integration boundary
REQ-449's accepted landing at 83c95cb shows the current route: cherry-pick a reviewed candidate and test on the resulting main tree. PROP-312 proposes a smaller ordinary land and remains open. The durable lesson on the page: keep transport completion, product validation, contract acceptance, integration, archival, and creator attention distinguishable.
Surveyor · spine and boundaries
Structure drawn only from the export's boundary table and host sections. No wall-clock bars — this arc does not publish comparable suite timings.
- 1Scope and contractREQ-429 + REQ-448 fulfilled; wider scope needs a recorded decision
- 2Candidate and reviewGit identity + Eyes; identity, review, archival, landing stay separate
- 3LandingREQ-449 fulfilled @ 83c95cb; REQ-358 deferred; PROP-312 open
- 4Codex routeREQ-451 fulfilled; FIND-1584 limits the smoke
- 5Cross-host policyShared ingress exists; PROP-315 remains proposed
- CodexHands/Eyes schemas + REQ-451 specimen; PATCH-354 @ 761a242
- ClaudeEyes structured verdict; Hands has no product schema
- Grokprotocol_success class; callback still provides no model witness
Mermaid source
flowchart LR
REQ["REQ / contract"] --> Cand["Candidate<br/>Git commit + tree"]
Cand --> Eyes["Independent Eyes"]
Eyes --> Land["Holder landing"]
Land --> Main["main"]
subgraph hosts ["Three hosts"]
Codex["Codex"]
Claude["Claude"]
Grok["Grok"]
end
Cand -.-> hostsSurveyor · wall-clock figures
Bars use only numbers verified in the exported markdown for this arc. Each row shows value and source commit SHA. Gaps stay gaps.
No verified wall-clock figures in this export — structure above carries the weight.