# Eve development and change · whole-source review

This map records a complete editorial read of the pinned 144-line
`V1/docs/eve/development-and-change-map.md`. It identifies five compact recipes
already taught completely by existing detailed Eve slides. It is not a claim of
complete Eve change-management teaching, current runtime enforcement, executed
verification, comprehension or product acceptance.

## Reviewed assignments

[`eve-development-change.json`](../assignments/eve-development-change.json)
binds these exact source units to assembled slide fingerprints:

| Source unit                                                                                      | Guide and slide                                             | Complete teaching boundary                                                                                                                                                               |
| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `0fd760da9a80aa9365dbf0be` · Add or modify an invocation point, lines 49–55                      | `eve-invocation-detail` / `eve-detail-invocation-exercise`  | Typed registry/guard, shell call, serialization, server validation, accessibility, analytics, desktop/mobile journey, and out-of-scope, unauthorized, stale and focus-restoration cases. |
| `c866146561ae3bc047d00c8c` · Add a task family or routing rule, lines 56–62                      | `eve-request-detail` / `eve-detail-routing-counterexamples` | Family contract, skill, tools, grounding, budget, model/escalation, evaluation, five language-case classes, prompt hash and family floors.                                               |
| `48cd152674c828037d898a8d` · Add a tool, lines 63–70                                             | `eve-request-detail` / `eve-detail-tool-contract`           | Typed contract, scope, effects, retries, audit/UI result, read freshness/redaction and mutation confirmation, conflict, replay, transaction and recovery.                                |
| `86f0bc5f5007051dfa3b0771` · Change prompts, skills, examples, or tool descriptions, lines 71–76 | `eve-model-detail` / `eve-detail-prompt-change`             | Model-visible byte inventory and ratchet, affected decks under the pinned registry, cost/latency inspection, scorecard evidence and rejection of copy-only review.                       |
| `830c589aaed85099310bca7f` · Change model/provider configuration, lines 91–97                    | `eve-operations-detail` / `eve-detail-release-exercise`     | Registry/config validation, explicit fallback, measurement protocol, family floors, escalation/cost/latency/provider-failure evidence and rollback data.                                 |

Each slide cites the exact source heading at inventory revision
`1ceae52c7896a59ac74a4429d410f3218f0b91c6`. The examples on the routing and
release slides remain illustrative; the assignments establish teaching of the
documented recipes and do not turn those examples into observed classifier or
deployment results.

## Units that remain unassigned

The source has thirteen meaningful units and one structural **Change recipes**
heading. The remaining eight meaningful units stay open:

- **Eve Development and Change Map, lines 1–27:** existing slides reuse parts of
  the change path, but none preserves the complete ownership-to-release Mermaid
  sequence and its full trust, test, quality, operations and documentation
  transitions.
- **Source map, lines 28–46:** the ownership slide compresses the table. It does
  not teach every concern, canonical area and typical-proof cell or the complete
  Docs Center ownership lookup instruction.
- **Change memory or grounding, lines 77–83:** the ownership slide names the
  affected boundaries but does not explicitly retain the entire unit/service/
  integration/contract/evaluation/privacy/browser verification set.
- **Change safety or persona policy, lines 84–90:** the crisis slide preserves
  versioned no-bypass, locale/cultural, crisis/refusal and surface review, but
  it does not state the complete adversarial suite or the source's disclosure,
  resource and supersession warning for presentation edits.
- **Contract checklist, lines 98–113:** the tool slide covers the fields needed
  by its worked mutation, but not all eleven questions for every new assistant
  contract, including plane/identity, data classification and full lifecycle.
- **Verification matrix, lines 114–128:** the ownership slide summarizes the
  change classes, but it does not reproduce every minimum proof cell and the
  resource-policy qualification as one complete unit.
- **Documentation obligations, lines 129–137:** the release exercise mentions
  handbook, diagrams, audits/TODOs and Docs Center regeneration, but omits the
  exact identity/plane/invariant/reading-path triggers and source-link, search
  and featured-rail outputs.
- **Related, lines 138–144:** no slide teaches the purpose and relationship of
  all five linked documents. A navigation list does not become complete teaching
  through citation alone.

The deliberately structural **Change recipes** heading remains structural in
coverage. Adding more assignments requires a complete explanatory slide for the
whole remaining unit, followed by the same source, slide, citation, guide and
assembled-fingerprint checks used here.
