Wiki: the implementor's checks entry is built (#420)
Pipeline-Agent: spec writer
Pipeline-Session: i420-spec-10@2026-10-18T04:17:22.460Z
#423: Reviewer page: post-verdict's own row, each shared name's module, and the two failure tests
#423: Reviewer page: the accept entry is built, with its tests
Reviewer: the machine and its review entry, and the sessions effect (#421)
Pipeline-Agent: spec writer
Pipeline-Session: i421-spec-7@2026-10-17T22:57:37.557Z
Pipeline roles: the implementor's fix entry and its per-lens re-review, as #418 builds them
Pipeline-Agent: spec writer
Pipeline-Session: i418-spec-10@2026-10-17T23:20:38.317Z
Spec draft for #415: the bundle's bound stays in the pure review-prefix module, which the op imports
Pipeline-Agent: spec writer
Pipeline-Session: i415-spec-4@2026-10-17T22:20:44.213Z
Wiki: the review bundle and the lenses' shared prefix in First review, linked from three-lens-review (#415)
Pipeline-Agent: spec writer
Pipeline-Session: i415-spec-4@2026-10-17T21:28:30.292Z
Pipeline roles: roles-6-10-scope, defer the final security review and re-check cost (Axlog, 2026-10-17)
Wiki: review-keeps-on-clean-rebase (#394)
Pipeline-Agent: spec writer
unrelated-fixes-allowed: writers may fix and improve beyond the issue's scope (#405)
Wiki: security-skip-unchanged (#387)
Records Axlog's decision to skip the security review when the head's
tree equals the tree that last passed, applies it to the planned final
security review, and replaces the finalizer's open question about the
first security review.
Pipeline-Agent: spec writer
sync-only-at-merge: a cleared review or fix round goes straight to checks; sync runs after implementation only when merge asks (#340)
Pipeline-Agent: implementer
Docs: stage jobs hold repo/ and docs/ side by side, every stage reads the wiki, and pipeline_commit needs write access (#338)
Pipeline-Agent: implementer
Issue pipeline: budgets bound context only (budgets-bound-context); writers commit often; rate limit off by default
Issue pipeline: writers-only context limits and watchdog max, a context log, no cache reads in reportedTokens (#314)
- The watchdog's over-budget kill and the job's context watch (soft steer,
hard stop) hold writer sessions only: implementer, fixer, CI fixer and
conflict resolver. Other sessions record a null tokenBudget.
- #272's reader retry (<key>.retry, the read-in-parts line) is gone; an
older job.json's retry record still reads.
- job.json gains firstContext and turns; contextStop is {"context":N}.
- New: runs/<slug>/issue-N/context.jsonl, one line per ended session, its
fields, and a jq line for peak context per role and stage.
- reportedTokens counts input, output and cache writes, as the rate limit
does; both pools are still charged the role budgets up front.
(Axlog, 2026-10-16)
Pipeline roles: credit the owner's decisions to Axlog
Add the Pipeline roles specs: the design for splitting the issue pipeline into roles
New pages: Pipeline-Roles (index), and one per role: Triage, Spec writer,
Implementor, Reviewer, Finalizer, Orchestrator, plus Shared (pipeline_commit,
role machines, restarts, the usage log and wiki provisioning). Linked from
Issue-Pipeline and the sidebar.