- An Execution's files are written as each Deliverable is submitted, marked
in_progress, so a killed process or one waiting for its user leaves them on
disk. A write removes files an earlier write left that it no longer has.
- A question about delivered work is answered from that Execution's solution
guide by the reply writer; a question about the service is answered as
before. Nothing is started for either.
- Lessons: prove writes only for lessons the Skill holds; the Skill records
the vendored Skill versions the lessons were read against, status names any
that changed, and a test fails until they are reviewed.
- Four more code patterns: Firestore, BigQuery, Eventarc and GKE.
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>