BA round 7 harvest: open-by-choice register state + enumerate-the-record (v0.12.0) - #23
Open
patelanil wants to merge 2 commits into
Open
BA round 7 harvest: open-by-choice register state + enumerate-the-record (v0.12.0)#23patelanil wants to merge 2 commits into
patelanil wants to merge 2 commits into
Conversation
…12.0 Returns/refunds record-bound engagement (2026-07-23, sponsor-approved harvest). Round 7 log added to ba-skill-spec with the two new rules, five keeper patterns (incl. [SPONSOR]/[KB] provenance grades), and a fixture-hygiene finding (EC2/EC3 canonical inputs not stored). Both rules folded into the agent definition's Rules section. Regression replay on the upgraded definition: EC1 PASS - both traps avoided (sync requirement survived the design cut per B1a; 'nightly' demoted to hint, freshness became the open question). EC2/EC3 not replayed: no stored canonical input (finding recorded); EC4/EC5 full-engagement fixtures deferred - the delta is two additive rules touching neither elicitation nor gap/overlap behavior.
moqui-coding-assistant stays domain-neutral: business-domain information (client, feature domain, artifact names) moved out of the round log to the coach repo's private fixtures, which the log now points to. The two rules, keeper patterns, and fixture-hygiene finding are unchanged - they were always craft, not domain.
Collaborator
Author
|
Sponsor ruling applied (2026-07-23): moqui-coding-assistant is domain-neutral — business-domain information does not enter this plugin. Round 7 rewritten: the two rules (D10, G13), keeper patterns, and the fixture-hygiene finding are unchanged (they are craft); every domain noun (feature domain, artifact names, engagement specifics) moved to the coach repo's private fixtures, which the log now cites as the engagement's home. Grep over the section: zero domain-word hits. The agent-definition additions were already neutral. |
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.
Sponsor-approved harvest from the returns/refunds record-bound engagement (2026-07-23; fixture in the private coach repo).
Two new rules (Round 7 log in
docs/ba-skill-spec.md+ folded intoagents/moqui-business-analyst.md):Keeper patterns logged:
[SPONSOR]and[KB]provenance grades, shapes-on-record listing, per-check stage naming, live rationale routing.Regression replay: EC1 on the upgraded definition — PASS, both traps avoided (sync requirement survived per B1a; "nightly" demoted to hint → freshness open question). EC2/EC3: no stored canonical inputs exist to replay faithfully — recorded as a fixture-hygiene finding in Round 7; EC4/EC5 (full-engagement fixtures) deferred with reason: the delta is two additive rules touching neither elicitation flow nor gap/overlap. Version bumped 0.11.0 → 0.12.0.