Rule on a design_context brief fact for change-auditor and seam-designer #1431

New issue

Open

opened 2026-10-27 17:48:53 +00:00 by jared · 0 comments

jared commented

2026-10-27 17:48:53 +00:00

Owner

Problem

The change-auditor and seam-designer read a ticket body and the repository, but no fact carries a per-ticket design slice: the proposed objects, the invariants, and the sub-system boundary from the system model. Step 7 of the path to real asks for a design_context fact in their briefs, with the proof that one ticket run with and without it scores better on design compliance.

Reproduce

grep -rn design_context plugins/os-sdlc/lib plugins/os-sdlc/agents

Output: no match. The only mention is docs/system-design-format/README.md section 6 step 7.

Approach

This step touches two agent charters (plugins/os-sdlc/agents/change-auditor.md, plugins/os-sdlc/agents/seam-designer.md) and adds a parsed brief field, so the brief vocabulary is a one-way door. Run /os-adr:find on the brief format and the agent-charter conventions first; then decide the ruling below; then split the build into a code-change ticket.

Required work: none beyond the acceptance criteria.

Acceptance criteria

Given the ADR search result, when the owner rules, then the ruling names whether design_context is a new brief field (ADR through /os-adr:create) or a section of an existing field, and which object builds it from OsSdlc::SystemModel::Model.
Given the ruling, when it is recorded, then a category/code-change ticket exists with Required work checks for the brief builder, the two charters, and the with-and-without scoring run.

Owner sketch

class OsSdlc::Dispatch::Brief
  def design_context; end
end

Origin

Trigger: pattern-detection track handoff 2026-10-27-1540, step 5: capture README section 6 steps 4, 5, 7
Improvised this session: none
Chain: agents design without the model's slice ← no design_context fact in the brief ← RULING (README section 6: "Step 6 and 7 touch agent charters and a parsed vocabulary; run /os-adr:find first")
Root candidate: none found; searched design_context, brief field, change-auditor charter, seam-designer charter, sub-system boundary
Where: docs/system-design-format/README.md section 6 step 7; plugins/os-sdlc/lib/os_sdlc/dispatch/brief.rb
Session: 47f54f99-e35c-4567-a3e6-581fecf54dc3
Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-ticket-1392/47f54f99-e35c-4567-a3e6-581fecf54dc3.jsonl

VERDICT: CREATE

## Problem The change-auditor and seam-designer read a ticket body and the repository, but no fact carries a per-ticket design slice: the proposed objects, the invariants, and the sub-system boundary from the system model. Step 7 of the path to real asks for a `design_context` fact in their briefs, with the proof that one ticket run with and without it scores better on design compliance. ## Reproduce ``` grep -rn design_context plugins/os-sdlc/lib plugins/os-sdlc/agents ``` Output: no match. The only mention is `docs/system-design-format/README.md` section 6 step 7. ## Approach This step touches two agent charters (`plugins/os-sdlc/agents/change-auditor.md`, `plugins/os-sdlc/agents/seam-designer.md`) and adds a parsed brief field, so the brief vocabulary is a one-way door. Run `/os-adr:find` on the brief format and the agent-charter conventions first; then decide the ruling below; then split the build into a code-change ticket. Required work: none beyond the acceptance criteria. ## Acceptance criteria 1. Given the ADR search result, when the owner rules, then the ruling names whether `design_context` is a new brief field (ADR through `/os-adr:create`) or a section of an existing field, and which object builds it from `OsSdlc::SystemModel::Model`. 2. Given the ruling, when it is recorded, then a `category/code-change` ticket exists with Required work checks for the brief builder, the two charters, and the with-and-without scoring run. ## Owner sketch ```ruby class OsSdlc::Dispatch::Brief def design_context; end end ``` ## Origin - Trigger: pattern-detection track handoff 2026-10-27-1540, step 5: capture README section 6 steps 4, 5, 7 - Improvised this session: none - Chain: agents design without the model's slice ← no design_context fact in the brief ← RULING (README section 6: "Step 6 and 7 touch agent charters and a parsed vocabulary; run /os-adr:find first") - Root candidate: none found; searched design_context, brief field, change-auditor charter, seam-designer charter, sub-system boundary - Where: docs/system-design-format/README.md section 6 step 7; plugins/os-sdlc/lib/os_sdlc/dispatch/brief.rb - Session: 47f54f99-e35c-4567-a3e6-581fecf54dc3 - Transcript: /home/jared/.claude/projects/-home-jared-dev-cc-os--claude-worktrees-ticket-1392/47f54f99-e35c-4567-a3e6-581fecf54dc3.jsonl VERDICT: CREATE

jared added the

plugin/os-sdlc

filed-by/user

category/owner-ruling

labels

2026-10-27 17:48:53 +00:00