Eve library

Eve safety, governance and privacy · whole-source review

Guide

Revision 1

On this page

This map records a complete editorial read of the pinned 174-line V1/docs/eve/safety-governance-and-privacy.md. It adds three exact assignments to two existing safety assignments and keeps seven meaningful units open. It does not establish current policy enforcement, audit retention, attack results, reader comprehension, listening or product acceptance.

Reviewed assignments#

The earlier eve-depth-boundaries.json file binds Capability grants and least authority and Budget, quota, and kill switches. The new eve-safety-boundaries.json file binds:

Source unit Guide and slide Complete teaching boundary
122126982d8d02fa8d1ee1dd · Policy order, lines 38–53 eve-safety-detail / eve-detail-protective-order All six precedence levels, no-bypass rules, cross-tenant denial and observable/testable supersession without unauthorized policy disclosure.
49db05fb167ee93b8c20e68a · Audit and non-repudiation, lines 146–156 eve-safety-detail / eve-detail-disclosure-audit Every attributable action field, typed append-safe receipt, investigation-preserving redaction and the separation of explanatory prose from authoritative service state.
2738738317cc3847e5e2720a · Abuse and adversarial cases, lines 157–167 eve-safety-detail / eve-detail-adversarial-review All twelve attack classes and the deterministic policy, schema, authorization and independent-verification enforcement boundary.

Every slide cites the exact heading and source at inventory revision 1ceae52c7896a59ac74a4429d410f3218f0b91c6. Worked examples do not widen the assignments beyond the complete source units.

Units that remain unassigned#

The source contains twelve meaningful units. Five now have reviewed assignments; seven remain open:

  • Eve Safety, Governance, and Privacy, lines 1–37: the guides teach the layered rule but do not preserve the complete state machine, every transition and every terminal audit path as one unit.
  • Lilith policy envelope, lines 54–66: the crisis slide retains the policy domains and builder/member boundary, but does not identify the canonical Lilith specification and test-invariant link required by the source.
  • Crisis-aware behavior, lines 67–79: the crisis journey is substantively covered, but the slide does not identify the named customer walkthrough and its role as the owning behavior evidence.
  • Human confirmation and side effects, lines 99–110: the confirmation and impact slides cover authoritative builder decisions and high-impact controls, but omit the source's separate member-domain-contract boundary.
  • Grounding and disclosure, lines 123–133: the disclosure slide preserves nearly every state and field, but omits safety-supersession disclosure and the named memory/grounding contract link.
  • Privacy and consent, lines 134–145: the data slides cover distinct classes, minimization and retention, but omit the complete voice recording/listening, provider, retention, consent and cloning-rights requirements.
  • Related, lines 168–174: no slide explains all five linked documents and their roles beside the safety contract.

No assignment follows from citation or high lexical overlap. Each future assignment must cover its whole unit and pass exact unit, revision, slide, citation, guide and assembled-fingerprint checks.