Skip to content

domain-driven-design: glossary layout, pressure-test observe, write-for-humans eval #7591

Open
8 of 9 issues completed

Description

@kyle-sexton

Parent

Refs #7555. Source: PLAN Phase 23, topic poteto-review. Thread: Other plugins.

Depends on

Outcome

/domain-driven-design:curate-language proposes a GLOSSARY.md per bounded context plus a
GLOSSARY-MAP.md; /prototype:pressure-test gains observe; write-for-humans gets a grounding rule
only if an eval shows the gap.

Decisions

  • /domain-driven-design:curate-language proposes GLOSSARY.md per bounded context plus
    GLOSSARY-MAP.md, stays domain-only; replace the four UBIQUITOUS-LANGUAGE.md lookups; glossary
    grouping line (D70, Q51, Q75, Q525; Matt's current glossary layout). Setting: glossary paths
    GLOSSARY.md, GLOSSARY-MAP.md.
  • Teach glossary rules; questionnaire template drops em dashes (Q525).
  • /prototype:pressure-test gains observe; prototype evidence on a throwaway branch after the
    secrets check (Q167, Q168; combined: Lauren and Matt both keep prototype branches).
  • /docs-hygiene:write-for-humans grounding rule only if an eval shows the gap (Q526).
  • Rejected: CONTEXT.md (no difference in a 4-agent experiment, "context" overloaded); a third
    prototype skill; prototype evidence as a note only or pushed without the check.

Key interfaces

From the design's module layout: "domain-driven-design: curate-language proposes GLOSSARY.md
per bounded context plus GLOSSARY-MAP.md." "prototype: pressure-test gains observe."
Settings: "Glossary paths GLOSSARY.md, GLOSSARY-MAP.md."

Slices, filed when this phase starts: glossary, pressure-test-observe, write-for-humans-eval.

Done when

  • rg -c 'UBIQUITOUS-LANGUAGE' plugins --glob '!**/CHANGELOG.md' returns 0 (nonzero on main) and
    bash scripts/check-purged-em-dashes.sh exits 0.
  • The write-for-humans eval slice carries a Probe result: comment.
  • Every slice sub-issue is closed by a merged PR.

Out of scope

  • Dossier branches (Dossier thread), beyond sharing the secrets check.

Activity

  1. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 16, 2026
  2. github-actions commented on Oct 16, 2026

    @github-actions
    Contributor

    Proposed work class: work-class: scoped
    Basis: automated intake triage; the lanes App applied this class.

    Size: Medium
    Complexity: Medium
    Uncertainty: Known
    Flags: none
    Blocked by: #7571

    Understood: update curate-language in domain-driven-design to propose a GLOSSARY.md per bounded context plus a GLOSSARY-MAP.md, replacing the UBIQUITOUS-LANGUAGE.md lookups. Add observe to prototype's pressure-test. Add a write-for-humans grounding rule only if an eval shows the gap. The outcome, decisions and done-when checks are specific, so I'm asking nothing further. The issue lists #7571 (glossary path settings) as a dependency, so I've recorded it as a blocker. I didn't find a likely duplicate among the open issues.

    Automated triage, applied by the lanes App.

  3. changed the issue type fromtoon Oct 16, 2026
  4. changed the issue type fromtoon Oct 16, 2026
  5. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Oct 24, 2026
  6. kyle-sexton commented on Oct 24, 2026

    @kyle-sexton
    MemberAuthor

    Released for re-triage under the owner's 2026-10-24 rule: an issue stops for a person only for an intent or vision question, a security call, a host or attended run, or spend outside prepaid credit. The hold label came off and intake triage runs again now; it re-applies a hold, with a numbered question, when one of those applies.

    To hold this issue again, add needs-human (or status: needs-decision) and say why in a comment.

  7. 11 remaining items

  8. removed
    admission-deferredAdmitted but waiting for WIP room; the hourly work-unblock sweep labels it agent-ready.
    on Nov 1, 2026
  9. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  10. github-actions commented on Nov 1, 2026

    @github-actions
    Contributor
    No description provided.
  11. added
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Nov 1, 2026
  12. melodic-automation-lanes commented on Nov 1, 2026

    @melodic-automation-lanes
    Contributor

    The work-resolve-issue lane did not start this issue: it needs a person to make it clearer first.

    Reason: intent

    Why, in the run's own words:

    What should /prototype:pressure-test observe do, and what check shows it is done? The issue names the mode and one property of it (prototype evidence goes on a throwaway branch after a secrets check), but not what observe observes, what it produces, or a done-when item for it; the only done-when items left are 'every slice sub-issue is closed by a merged PR' and a Probe result: comment on a write-for-humans eval slice, and neither slice issue is filed yet. Two related points need a person's call: (1) the throwaway-branch evidence contradicts rule 6 'Delete or absorb when done' in plugins/prototype/context/discipline.md and the recorded rejection in docs/upstream/mattpocock-skills.md row 'prototype HTML demo shell' ('Rejected: keeping the prototype runnable on a throwaway branch as the primary record'), so confirm the issue's decision replaces that rule and that row; (2) the 'secrets check' is meant to be shared with the Dossier thread and no such check exists in the repository, so its home and contract are an undecided shared design. Please file the pressure-test-observe and write-for-humans-eval slices with their own outcomes and done-when items (or record the observe behavior here as a Decision recorded. comment). This umbrella issue then closes once those slices close.

    What the run says it did not do:

    • scripts/check-purged-em-dashes.sh (done-when item 1, second half) was not run: this lane runs only the named wrappers. CI's purged-em-dashes job runs it.
    • Filing the pressure-test-observe and write-for-humans-eval slice sub-issues and posting the eval's Probe result comment: this lane cannot file issues, post comments or run the eval.

    The newest comment from a listed maintainer, #7591 (comment), does not start with **Decision recorded.**, so the lane did not count it as an answer. If it answers the question, post the answer again in a new comment whose first line is:

    **Decision recorded.** <answer>
    

    Run: https://github.com/melodic-software/claude-code-plugins/actions/runs/41293793737

    To retry, answer the question in a comment whose first line is **Decision recorded.**, then remove needs-human and add agent-ready again.

  13. removed
    agent-readyFully specified and briefed; eligible for autonomous pickup from the frontier.
    on Nov 1, 2026
  14. kyle-sexton commented on Nov 1, 2026

    @kyle-sexton
    MemberAuthor

    Decision recorded.

    Issue Triage session (agent), applying a decision recorded in the poteto-review interview ledger; this comment asserts no new owner decision.

    The issue lane stopped here with reason intent (comment 6556369883), asking what /prototype:pressure-test observe does and what check shows it is done. The poteto-review interview answered that as Q167. Its ledger records the owner's answer as "accepted as recommended audit A7" (.work/poteto-review/interview-checklist.md:212, a local session record), and decision row 99 records Q160, Q162 and Q165-Q169 as "APPROVED as recommended" (.work/poteto-review/GUIDE.md:209, owner 2026-10-15). The session's question the owner accepted, verbatim: "Should /prototype:pressure-test gain an observe option where the agent runs the variants of a fork a run can settle, records behavior, output and timing (timing labeled unqualified), and recommends, handing off to /performance:goal only when the fork is itself a performance target?" Recommended answer: "Yes, as described; the human keeps product and preference calls; the STOP gate for unrequested prototypes stays." Q168 (evidence on a throwaway branch after the repository's secrets and machine-data check) is recorded the same way (interview-checklist.md:213).

    The remaining work is split into sub-issues, each with its own done-when:

    This issue closes when every sub-issue closes by a merged pull request. needs-human comes off: the intent question has a recorded answer.

  15. removed
    needs-humanHuman-in-the-loop required; autonomous sessions must not resolve items carrying this.
    on Nov 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-specNeeds a Brief or plan before anyone can build it.priority: mediumReal value, no hard deadline; normal backlog flow.status: readyTriaged, unblocked, and fully specified; eligible to pick up.work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.

    Fields

    Work status

    needs-spec

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions