BA method rule: confirm named business terms with the Expert User - #22
Open
patelanil wants to merge 2 commits into
Open
BA method rule: confirm named business terms with the Expert User#22patelanil wants to merge 2 commits into
patelanil wants to merge 2 commits into
Conversation
… the label Sponsor correction from the notnaked send-sale discussion (2026-07-22): "send-sale" generally means the item is NOT in stock at the placing store (not a hard rule). A downstream design pass assumed the intuitive reading and got the typical case backwards; the story itself had it right. New never-invent bullet: confirm a term's typical real-world state with the Expert User, and carry multi-sub-case scenarios distinctly in the story. Note for the merge decision: additive rule; the BA fixture replay gate (hotwax-agency fixtures/ba/) has NOT been run for this edit.
Sponsor ruling on the first commit: send-sale specifics are HotWax retail DOMAIN knowledge and belong in the hotwax-agency plugin's shared docs/domain-knowledge/ base (created there, hotwax-agency PR #17), not in this generic BA role definition. The bullet now carries only the role-method half: confirm a named term's typical state with the Expert User, read the engagement's domain-knowledge base when one exists, and carry multi-sub-case scenarios distinctly.
patelanil
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this is (reworked per sponsor correction)
The sponsor's ruling on the first draft: send-sale specifics are HotWax retail domain knowledge and belong in the hotwax-agency plugin's shared knowledge base — not in this generic, domain-agnostic BA role definition. The domain content now lives in hotwax-agency's new
docs/domain-knowledge/(hotwax/hotwax-agency#17), and hotwax-agency's Phase-3 handoff seeds the BA with the relevant entries on each engagement.What remains here is only the role-method half, one never-invent bullet: a named business term implies a typical real-world state — confirm it with the Expert User rather than infer it from the label; read the engagement's domain-knowledge base when one exists; carry multi-sub-case scenarios distinctly in the story.
Replay gate note: additive rule; the BA fixture replay (
hotwax-agency/fixtures/ba/) has not been run for this edit.