Skip to content

Business analyst answers draw the process - #188

Merged
trick77 merged 3 commits into
masterfrom
worktree-ba-diagrams
Sep 17, 2026
Merged

trick77 merged 3 commits into
masterfrom
worktree-ba-diagrams

Conversation

@trick77

@trick77 trick77 commented Sep 17, 2026

Copy link
Copy Markdown
Owner

BA answers to process questions came back as prose although nothing barred a diagram. Three causes in the prompt: the BA block ended with "then stop" before the diagram rule was read, the diagram rule triggered on "control flow or a call sequence" (developer words that never fire on a business question), and the shape rule sent ordered steps and branches to a list.

Changes:

  • answerBA names when a picture belongs, in the reader's words (case, approval, hand-off: flowchart; exchange between systems, roles, people: sequence).
  • answerDiagram triggers on a branch or a second party, whoever the parties are; a plain sequence of steps stays a list, one rule or value stays prose. Caps and label rule unchanged.
  • answerShape hands ordered steps with a branch or a second party to the diagram.
  • answerProcesses asks for the BPMN walk as the flowchart; the comparison blocks ask for a sequence between the repositories unless a walk is listed.
  • ask.DiagramKind reports the drawn picture under the browser's parse conditions; TestEvalMeasureAnswers prints diagram per answer and diagrams per run.

Measured on the flow corpus, BA audience, two runs each against origin/master the same day: 1 diagram in 19 answers before, 13 in 19 after; rubric 52/56 before, 50/56 after, the two misses in an answer without a diagram, inside judge noise. All 96 labels under 40 characters, every spec inside the caps. Details in docs/measurements/2026-09-17-ba-diagrams.md.

Developer answers get the same trigger and shape rule; not measured here, the harness default is BA. The UI was not driven by hand: the renderer is untouched and DiagramKind mirrors its conditions, which all 13 specs pass.

…ggers in domain words

The BA block shaped the answer as prose-and-stop and the diagram rule at the
end of the prompt never overrode it; its trigger was in developer words
(control flow, call sequence) and the shape rule sent ordered steps to a
list. The audience block now names when a picture belongs, the diagram rule
triggers on a branch or a second party whoever the parties are, the shape
rule hands such steps to the diagram, and the process listing and the
comparison blocks ask for the walk or the exchange as the diagram.

ask.DiagramKind reports the drawn picture per answer; the answers harness
logs it beside the digraph count.
Closed fence, header by first token, valid JSON, at least one node or actor
with id and label: the browser's conditions, so an empty or cut-off spec
counts as none. The comparison blocks yield to a listed process walk, so
one prompt no longer asks for both a sequence and a flowchart under at most
one diagram. The measured counts are unchanged under the strict reading.
@trick77
trick77 merged commit 9745370 into master Sep 17, 2026
2 checks passed
@trick77
trick77 deleted the worktree-ba-diagrams branch September 17, 2026 17:22
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