Skip to content

feat(cockpit): Work through by the briefing's buckets, one card with the bucket's answers - #703

Merged
mboiman merged 3 commits into
bks-lab:mainfrom
mboiman:feat/cockpit-briefing-buckets
Nov 21, 2026
Merged

mboiman merged 3 commits into
bks-lab:mainfrom
mboiman:feat/cockpit-briefing-buckets

Conversation

@mboiman

@mboiman mboiman commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

What

Work through gets a switch cockpit.flow.buckets (feature flow_buckets, on by default): every point stands in exactly one bucket of the briefing profile, and each card offers that bucket's answers. Builds on #702 (tab answers, tab_accept).

Briefing (server rule, so the printed briefing and the cockpit agree)

  • An inbox item put off waiting on the Bridge (defer --on Bridge) is delegate, or do when only the person can take its next click (only-you, e.g. a login). Before, a section forced to bucket: waiting held such rows under "Waiting on others".
  • task_who reads "the Bridge" in any spelling.
  • One numbering rule for every style (briefing_view.numbered), carried on each row as nr. Calm now numbers its waiting rows too, each with its topic.
  • A cockpit pass (--max-items, every row) numbers rows as the printed briefing would: the profile's style and max_items, without what was settled in the cockpit.
  • The view names every shown bucket with its title and answers (bucket_defs).

Cockpit

  • Left: the buckets in profile order with counts. The open bucket lists its points.
  • Middle: one card with its kind and facts, its title, one sentence Next (the tab's question, the card's step, or a fixed sentence per bucket, no model call), and the bucket's answers as big buttons (first one primary). It also shows "In the briefing: no. N". Everything else (states, Hand over, fields, Description, Steps, Activity, the tab's screen) is under More. There is no right column.
  • Each answer runs the same act as the briefing's answer, matched by its position in the options: do_it, later to the next briefing day, settle/shelve, a picked day then later, the check-in chase (draft only) via do_it, runs_on, task_keep, and the tab's own answers (dialog options, yes/no, tab_accept). No new server verb.
  • An answer moves on to the next point. An empty bucket opens the next bucket that has points.
  • While the switch is on, the Aufgaben columns and Jev's squares use the bucket names.
  • Follow-up to fix(cockpit): a waiting tab's question skips Claude Code chrome, its ready answer goes out with Enter #702: the classic card of a waiting tab shows the question itself (the last sentence that asks, read across wrapped lines), not the first line of the screen.
  • task_rows rows no longer carry the default bucket do.

Docs: docs/bridge-cockpit.md (Buckets, config key, feature row), docs/briefings.md (rule row, numbers), docs/bridge-cockpit-dev.md.

Tests

  • New: test_briefing_buckets.py (11, red on main), test_bridge_cockpit_buckets.py (4), bridge_cockpit_buckets.test.mjs (11).
  • Local: scripts/tests 6667 passed / 5 skipped, frontend 1349 passed, build-cockpit-demo.py --check clean, validate-bridge.py 82 passed.

🤖 Generated with Claude Code

mboiman and others added 2 commits November 21, 2026 12:12
…rinted row has a number

An inbox item put off waiting on the Bridge (inbox.py defer --on Bridge) stood under
"Waiting on others", also through a section forced to bucket: waiting (8 rows on
21.11.2026). It is the Bridge's to do (delegate), or the person's (do) when only they can
take its next click (gate only-you, a login). task_who reads "the Bridge" in any spelling.

The numbers a briefing prints come from one rule (briefing_view.numbered) and stand on
each row as `nr`; calm now numbers its waiting rows too, each with its topic. A cockpit
pass (every row, --max-items) numbers as the printed briefing would: the profile's style
and max_items, without what was settled in the cockpit. The view names every shown bucket
with its title and answers (`bucket_defs`), an empty one too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: mboiman <mboiman@gmail.com>
…the bucket's answers

With cockpit.flow.buckets (feature flow_buckets, on by default) every point of Work
through stands in exactly one bucket of the briefing profile (the server's bucket rule;
names, order and answers from view.buckets), the left column lists the buckets with their
counts. One card at a time says one sentence Next (the tab's question, the card's step, or
a fixed sentence of its bucket) and offers the bucket's answers as big buttons, the first
one the Bridge taking the next step; each answer is the act the briefing's answer is
(do_it, later, settle/shelve, a day picked, runs_on, task_keep, a tab's own answers
including tab_accept). Everything else stands under More, there is no right column, an
answer moves on by itself, and the card names its number in the printed briefing. The
Aufgaben columns and Jev's squares say the buckets' names while it is on.

The classic card of a tab that asks shows the question itself (the last sentence that
asks, across wrapped lines), no longer its screen's first line (bks-lab#702 follow-up). A task a
page names beside the briefing no longer carries the default bucket do.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: mboiman <mboiman@gmail.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: mboiman <mboiman@gmail.com>
@mboiman
mboiman merged commit 32794dc into bks-lab:main Nov 21, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant