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>
Capture, distil, review, publish, retire (ADR-0004). Lesson candidates of
past Executions are grouped into what recurred; a lesson-curator role,
outside any Execution, proposes a lesson per group worth one; each proposal
is an issue file a person approves or rejects; an approved lesson is
written into the provider's lessons Skill, which a Specialist is given only
once it holds lessons for that Specialist's Deliverable. LESSONS_ENABLED
off runs without them, for an evaluation with and without.
The curator proposed six lessons from 21 Executions. The owner approved all
six on 2026-10-09 and they are published: five for the target architect,
one for the IaC author. None is proved by an evaluation yet.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>