feat: consult only the pillars a change affects directly (iteration 5 step 3)
A graded question per pillar (not at all, only indirectly, directly) picks the pillar advisors to consult again on a Revision or a Change request; the design advisor is told which, and keeps its earlier advice for the rest. As a yes or no the answer was yes for nearly every pillar of every change. A completed Execution now writes working.json with each pillar's advice and checklist review, and a Change request starts from its Baseline's, so only the pillars a change touches are consulted afresh. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -71,6 +71,9 @@ JEV_COVERAGE_THRESHOLD=0.6
|
||||
# product? Off until a full case has run with it.
|
||||
JEV_REQUIREMENTS_REVIEW=false
|
||||
JEV_REQUIREMENTS_THRESHOLD=0.3
|
||||
# How directly a change must affect a pillar for its advisor to be consulted again:
|
||||
# 0 not at all, 1 only indirectly, 2 directly.
|
||||
JEV_PILLAR_THRESHOLD=1.5
|
||||
|
||||
# PostgreSQL (Execution records, and checkpoints when CHECKPOINTER=postgres)
|
||||
POSTGRES_HOST=localhost
|
||||
|
||||
Reference in New Issue
Block a user