docs: bring the README, runbook, glossary and ADR notes up to date
Some checks failed
validation / verify (push) Failing after 11s
Some checks failed
validation / verify (push) Failing after 11s
The README now covers the router, Change requests, overlay Skills, Jev's uses and the current layout. VALIDATION.md no longer points at the removed root Terraform. ADR-0004 and ADR-0007 gain dated "As built" notes; ADR-0007's says which uses of Jev send Deliverable content. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -35,3 +35,12 @@ Accepted by the owner on 2026-10-08, agreeing to each of these:
|
||||
- The evaluation must be able to see a difference a Skill makes. Its structural checks cannot, so the judged checks and the thresholds on Revisions, time and tokens become part of the loop.
|
||||
- The glossary gains **Lesson candidate**, **Lesson** and **Overlay Skill**.
|
||||
- Skills can no longer be loaded once at start-up for all Executions: the runtime must resolve a role's Skills per Execution.
|
||||
|
||||
## As built (2026-10-09)
|
||||
|
||||
Two points differ from the text above; the decisions stand.
|
||||
|
||||
- **Default overlays are a deployment setting, not part of the provider bundle.** `DEFAULT_OVERLAY_SKILLS` names the overlays every Execution loads. Whose standards apply belongs to the deployment and the caller, not to a Cloud provider.
|
||||
- **Skills are still loaded once at start-up.** The runtime loads every provider Skill and every overlay in the configured folders when it starts, and an Execution chooses among them. An overlay added to a folder needs a restart.
|
||||
|
||||
Decision 2 has a first result: on one benchmark case run each way, the lessons held quality and removed a Revision. One lesson was retired because the fault was in a review, not in the agents.
|
||||
|
||||
@@ -81,3 +81,10 @@ Accepted by the owner on 2026-10-07, with each of these:
|
||||
- Jev becomes a dependency of every interactive Execution. Its availability, latency, rate limits and data retention must be known before this is built; none is documented publicly.
|
||||
- Decisions become measurable: each has a confidence, so thresholds can be tuned from recorded Executions.
|
||||
- An unusual request that fits none of the questions is handled by asking the user, where a language model might have improvised.
|
||||
|
||||
## As built (2026-10-09)
|
||||
|
||||
- **Jev is used beyond the Orchestrator.** It also chooses the pillars a change touches and the Skill references a Specialist reads first, checks remote MCP replies and the user's text for instructions aimed at the agent, tells a rewording from a change, and scores each Execution's design recommendations. Each has a fallback in code and is a setting.
|
||||
- **Decision 4 covers Orchestrator decisions only.** These other uses do send content: design recommendations, Check and Element text, remote MCP replies and the Workflow request. Jev's data retention is therefore a question about Deliverable content, and it is still unanswered by the vendor.
|
||||
- **Jev did not become a hard dependency.** Without a key, or when a call fails, every decision takes its fallback and the Execution continues.
|
||||
- **The fourth route, which Deliverables a change reaches, is decided in code** from the changed requirements and the Requirements chain, not by Jev.
|
||||
|
||||
Reference in New Issue
Block a user