A pillar's checklist item the request gives no information about was marked
"not addressed", which reads as a fault in the design. It is missing
information. The checklist review gains a fourth outcome, to confirm with the
customer, which must carry the question to ask. The questions are written
into the design recommendations and the guide, and to customer-questions.md;
the evaluation's judged check counts such an item as accounted for.
Records the owner's decisions of 2026-10-10 and the vendor's answers on Jev's
retention, training, context and rate limits (iteration 5 step 1), and the
owner's labels, which showed the judged question was wrong, not the judges.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>