8000 The Working order rail · Issue #35 · kiran-brahma/writing-tool · GitHub
[go: up one dir, main page]

Skip to content

The Working order rail #35

Closed
Closed

Description

@kiran-brahma

Parent

#34 — the Obelus v1.2 spec (docs/specs/obelus-v1.2.md). Covers stories 160–166.

Read docs/adr/0010-the-working-order-is-the-navigation.md before starting. It is the decision this
ticket implements, and its four properties are the boundary.

What to build

The rail's top-level control becomes the Band — Structure, Paragraph, Word — plus All.
Selecting a Band shows that Band's Passes together with the Findings those Passes produced, so a
Run and its result are one view. The Judge becomes a destination below the Band control, not a fourth
Band. The Findings / Reader accounts / Audit accounts tab strip is removed: an account is shown in
its Pass's Band beside that Pass.

Today the rail is eight sections in one scroll column, with the Findings above the Passes that
produce them, so the loop costs a scroll down and a scroll back on every cycle.

workingOrder(passes) already groups Passes into Bands. Give it a second job — partitioning the
Findings queue by the Band of the Pass that produced each Finding — so the derivation stays in one
pure function and the rail stays display over Core, as every panel already is.

Where the displaced sections go:

  • Outline and metrics — a collapsible strip above the Band control.
  • Milestones and Revisions — under the Judge destination, where they are its raw material.

Three new keys in the existing settings key-value store: the last Band, and whether the rail is
collapsed (the third, first-run dismissal, belongs to the How this works ticket). database.settings
is get(key) / put({key, value}), so no Dexie migration is needed — do not add one.

Where

  • src/core/pass.ts — extend workingOrder; workingOrderBand is unchanged.
  • src/App.tsx — the rail region.
  • src/editor/ — ModelPassesPanel, RulePassesPanel, FindingsSidebar, ReaderPanel,
    AuditPanel, JudgePanel, MetricsPanel, OutlinePanel.
  • src/storage/settings.ts, src/useDocument.ts — the two new keys.

Acceptance criteria

  • The rail's top-level control is the Band: Structure, Paragraph, Word, plus All. (story 160)
  • A Band shows its Passes and the Findings those Passes produced in one view. (story 161)
  • All shows every open Finding across every Pass. (story 162)
  • The Judge is its own destination below the Band control, visually separated, and is not a
    Band. (story 163)
  • Reader accounts and Audit accounts appear in their Pass's Band; the three-tab strip is gone.
    The Audit pass is document-scope so it lands in Structure; the Reader pass is section-scope so
    it lands in Paragraph. (story 164)
  • Outline and metrics are collapsible; milestones and Revisions sit under the Judge. (story 165)
  • The rail opens on Structure when no Band is stored, on the stored Band thereafter, and
    collapses entirely. (story 166)
  • ADR 0010, tested: every Band is reachable in one click from every other in any order; no
    Band is gated on another; All is always available; no Run is refused, deferred or hidden
    because of the Band showing.
  • No Dexie migration is added.

Verification

Pure tests on the extended workingOrder: the Band partition of the Findings queue; that every Band
is present whatever the Pass set; that All contains every Finding that exists. Same input, same
output — no clock, store or random source.

No DOM layer. Do not add Testing Library, jsdom or Playwright — see the spec's Testing Decisions.
State the observable checks you ran in the app for the layout itself.

Constitution

A recommendation, never a gate — ADR 0009 and the four properties above. Nothing here inserts
model-derived text, and the findings schema is unchanged.

"Stage" is banned. CONTEXT.md's Working order entry lists pass stage under Avoid and it
is banned for the Band too: not in a ticket title, a commit message, a variable name or a comment.
The terms are Band, Working order, Finding, Pass, Judge.

Activity

  1. kiran-brahma commented on Sep 22, 2026

    @kiran-brahma
    OwnerAuthor

    Landed in 0cc6890.

    • The rail's top-level control is the Band — Structure, Paragraph, Word — plus All (story 160).
    • A Band shows its Passes and the Findings those Passes produced in one view, per Pass (story 161).
    • All shows every open Finding across every Pass, and carries a Finding whose Pass has left the set (story 162).
    • The Judge is its own destination below the Bands, visually separated, and is not a Band (story 163).
    • Reader and Audit accounts render in their Pass's Band; the three-tab strip is gone (story 164). Audit is document-scope, so Structure; Reader is section-scope, so Paragraph.
    • Outline and metrics collapse above the Band control; milestones and Revisions sit under the Judge (story 165).
    • The rail opens on the stored Band (Structure when none), collapses entirely, and both keys persist (story 166).
    • workingOrder(passes, findings) partitions the Findings queue by the Band of the Pass that produced each Finding. Pure tests cover the partition, every Band present whatever the Pass set, and All holding every Finding that exists. soloRulePass and isWorkingOrderBand join Core so the rail and the runner cannot disagree.
    • No Dexie migration: railBand and railCollapsed ride the existing settings store.
    • New term Rail recorded in CONTEXT.md.

    ADR 0010 properties, observable in the app (no DOM layer, as the spec requires): Structure/Paragraph/Word/All switch the panel in one click in any order; All lists the whole queue; the Judge sits below the tabs; the rail collapses and reopens, restoring the last Band on reload; no Run is disabled by which Band is showing.

    The old ModelPassesPanel, ReaderPanel and AuditPanel fold into one BandPanel; FindingRow and the account renderers are shared. No affordance inserts model-derived text.

    Tests: 828 passing; scripts/agent-gates check clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentSpec is ready for an agent to implement

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0