Skip to content

fix: derive requirement hearing questions only from convergence gaps - #105

Merged
shinpr merged 2 commits into
mainfrom
fix/hearing-question-source
Oct 29, 2026
Merged

shinpr merged 2 commits into
mainfrom
fix/hearing-question-source

Conversation

@shinpr

@shinpr shinpr commented Oct 29, 2026

Copy link
Copy Markdown
Owner

Summary

  • requirement-analyzer returns scope and cost evidence only; the orchestrator forms hearing questions, one per convergence field below ready.
  • Remove per-recipe copies of the User decisions rule; Scope Confirmation owns it.
  • Preconditions held outside the repository change enter requirements and hearings only when the user raises them.
  • Bump version to 1.8.6.

🤖 Generated with Claude Code

shinpr and others added 2 commits October 29, 2026 10:08
requirement-analyzer returned its own user-facing questions, including
exclusion questions, without the convergence criteria that keep
unrequested capabilities out of the hearing. Each entry recipe also
restated a broader User decisions rule than the hearing's one question
per field below `ready`.

The analyzer now returns scope and cost evidence only, and Scope
Confirmation owns the User decisions rule without per-recipe copies. The
requirement criteria keep preconditions satisfied outside the repository
change out of the record and hearing unless the user's wording raises
them.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@shinpr shinpr self-assigned this Oct 29, 2026
@shinpr
shinpr merged commit e1d00d6 into main Oct 29, 2026
2 checks passed
@shinpr
shinpr deleted the fix/hearing-question-source branch October 29, 2026 02:14
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