feat: overlay Skills, and five more Jev decisions (iterations 4 and 5)
Iteration 4: - Overlay Skills (step 12): an Execution names an organisation's standards Skill from the folders the deployment configures; recorded with its version. An example standards Skill and an evaluation case that uses it. - Lessons (step 10): a prove command that compares a run with lessons against one without, and triage of evidence an existing lesson already covers. Iteration 5: - Step 8: the references of a Specialist's Skills its task needs are named in its context as read_first. - Step 14: a remote MCP server's reply that instructs the agent is withheld; the user's own text is flagged as a risk and nothing more. - Step 15: in a Change request, items only reworded are listed apart from real changes. - Step 19: each Execution's design recommendations are judged when it ends and the scores kept in its record. The evaluation takes its rubric from the same place. Each question was calibrated against live Jev; none has run in a case. Steps 6, 7, 9, 13 and 18 stay planned, with the reasons in the plan map. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
23
.agents/plans/iter-05-jev-decisions/steps/step-3.md
Normal file
23
.agents/plans/iter-05-jev-decisions/steps/step-3.md
Normal file
@@ -0,0 +1,23 @@
|
||||
# Step 3 — Implementation Detail
|
||||
|
||||
Built on 2026-10-09. **Not run in an Execution with real models.**
|
||||
|
||||
1. `pillars_touched` in `app/tools/pillars.py` asks one graded question per pillar: how directly does this change affect the pillar's recommendations (not at all, only indirectly, directly). A pillar at `JEV_PILLAR_THRESHOLD` (1.5 on that 0 to 2 scale) or above is consulted again. An empty list means the change touches none; no decision means consult them all.
|
||||
2. When the design advisor is started on a Revision, or in a Change request, and advice from an earlier consultation exists, the engine asks which pillars the change touches (`_pillar_hints` in `app/nodes/execution_nodes.py`) and puts the answer in its context as `pillars_to_consult`. The change is the Deliverable's feedback, or in a Change request the requirements added, changed and removed.
|
||||
3. `consult_pillar_advisors` with an empty list consults nobody and returns the advice already given.
|
||||
4. A completed Execution writes `working.json`: each pillar's advice and checklist review. A Change request starts from its Baseline's, so the pillars a change does not touch are not consulted again. In the first Change request, before this, the design advisor consulted all six afresh and that was its longest step.
|
||||
|
||||
Differs from the plan: the plan asked a yes or no per pillar. Measured against live Jev on six changes, that was yes for nearly every pillar every time (0.39 to 0.96 across the five real changes). The graded form separates them:
|
||||
|
||||
| Change | Pillars at "directly" |
|
||||
|---|---|
|
||||
| Retention to 7 years, undeletable | security, reliability, operations, cost, sustainability |
|
||||
| Survive the loss of a region | reliability, operations, cost |
|
||||
| Budget halved | operations, cost, performance, sustainability |
|
||||
| Page load 1 s to 300 ms | operations, cost, performance |
|
||||
| A page title renamed | none |
|
||||
| Customer-managed keys for one bucket | security |
|
||||
|
||||
Operations and cost are picked for almost every real change, so the saving is two to five advisors of six, not five of six.
|
||||
|
||||
Tests: `tests/execution/test_pillars.py` (3), `tests/execution/test_change_requests.py` (2).
|
||||
Reference in New Issue
Block a user