Skip to content

I can see and correct the decisions the team remembers, and the Lead applies them - #518

Open
a-team-app[bot] wants to merge 10 commits into
mainfrom
feat/decision-register
Open

a-team-app[bot] wants to merge 10 commits into
mainfrom
feat/decision-register

Conversation

@a-team-app

@a-team-app a-team-app Bot commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

The team now keeps a register of what you've decided. The Lead searches it before it pitches, breaks a pitch down or assumes anything, cites what it relied on under Assumed (From the register: you, on #34), records new decisions as you make them, and says what a new one replaced. On its first run after the release, finding its team's register empty, it seeds it from closed pitches' Decided sections.

Decisions…, in the palette and the View menu, lists the selected team's entries plus all teams', newest confirmed first. Search narrows them, Include all-teams and Show replaced filter them, and the selected entry is shown in full below. Enter opens where it was said, e edits the wording in place, k toggles rule/lean, w widens to all teams, and r retires. The Lead can't overwrite an entry you've corrected.

Closes #516

Beyond the task

  • w and r also undo: w narrows an all-teams entry back to its own team, and r brings a retired one back. Their buttons say which (w This team only, r Bring back).
  • The task asks for a hint row; since Dashboard dialogs have buttons and no hint row, and F1 shows each one's keys #532 moved the dashboard's dialogs to buttons and F1, this dialog has buttons at its foot and lists every key on F1 instead, like the others.
  • Focus starts on the list, so e/k/w/r work straight away. Tab goes to Search, where Up/Down still move the selection.
  • Enter saves an edit, and Ctrl+Enter does too.

a-team try a-team 518

A `decisions` table and FTS5 index beside `history` in a-team's database,
created by its own decisions_sql so a sqlite3 without FTS5 loses only the
register, never the history.

Board commands: `decisions` (search; --replaced for the whole register),
`decide`, `replace` and `reconfirm` for the Lead, and `decision you` for the
dashboard's corrections. An entry the stakeholder changed records when in
`yours`, and the Lead may replace it only with the stakeholder's own newer
word. Every write is covered by --dry-run.

The Lead's role says when to search, cite, record, replace and reconfirm, and
to seed the register from closed pitches' Decided sections when its team has
none. The dashboard's Decisions… (palette and View menu) lists, searches,
opens and corrects entries, with its keys in its hint bar and on F1.

Closes #516

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@a-team-app

a-team-app Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

Needs changing

  • scripts/board.sh:2147 and :2175 decide --replaces and replace let one team's Lead mark an all-teams entry replaced by an entry scoped to its own team. live_decision accepts any entry with everyone set, so the old entry drops out of every other team's decisions, and their only trace is a bare "Replaced" in the dialog, because the new entry isn't in their register. roles/lead.md tells the Lead to use all only for what isn't about this product, so a team-scoped answer that conflicts with a cross-team lean is the normal case, and it would quietly take the lean away from every team. Refuse it (an all-teams entry is replaced only by an all-teams one, otherwise record it beside the old one with its condition) and add a case to tests/scripts.sh.

Worth considering

  • roles/lead.md:46 Seeding runs whenever the team has no entry of its own, so a team whose closed pitches turn up nothing that generalises re-reads every closed pitch's Decided section on every Lead run, which is a lot of API calls against the shared limit. Recording that seeding has run (a history event, or a marker in the register) would make it a one-off, as the pitch's Decided Triggers miss feedback older than 24 hours #5 and Add themes and a settings dialog where the theme can be changed #8 intend.
  • replace lead <old> <new> doesn't check that <new> is the newer of the two. "Follow the newer" is only in the prose, and comparing said would cost one line.

Replacing it would drop the lean from every other team's register, with
only a bare "Replaced" in their dialog. The Lead records a team-scoped
answer beside it with its condition instead.

Closes #516

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@a-team-app

a-team-app Bot commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

Thanks. On Needs changing:

  • Fixed in 4163ea6. decide --replaces and replace now refuse when the old entry is all-teams and the new one is team-scoped, and say to record it beside the old one with its condition. roles/lead.md says the same, and tests/scripts.sh has a case for both commands that checks the other team keeps the entry.

I've left Worth considering for you to decide on.

@a-team-app
a-team-app Bot marked this pull request as ready for review October 15, 2026 06:27
a-team-app Bot and others added 2 commits October 15, 2026 21:24
Keeps both the Spending dialog and the Decisions dialog.

Closes #516

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Keeps both the Decisions dialog and MacKeys parameters on DashboardWindow.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
a-team-app Bot and others added 6 commits October 17, 2026 21:45
…r entry

lead-next says `seed` until the Lead runs `seeded lead`, so a team whose
closed pitches yield nothing to record doesn't re-read them every run.
`replace lead <old> <new>` refuses when <new> was said before <old>.

Closes #516

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…her dialogs

Main moved every dialog onto DashboardDialog and dropped StatusBar's hint row
and HintedCommand (#532), so this one follows: its actions are buttons at the
foot, e, k, w and r work only from the list, and F1 lists its keys.

Closes #516

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Main's new letters test pins the View menu's items; this branch adds one.

Closes #516

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
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.

I can see and correct the decisions the team remembers, and the Lead applies them to new pitches

0 participants