Work package#
Finish the remaining Eve design defects identified in eve-design-review.md and
the relevant section 10 craft standards. Baseline delivery is 3e639b57c2; this
package starts from 582d1845a8, whose intervening changes do not change
presentations. The 25-guide Eve route contains 204 slides. The capability source
pin remains 8c27a8d3350fe7484c18585b570f72a561090540; architecture guides keep
their independently declared revisions.
The package covers the twelve product guides and a complete editorial/optical review of the thirteen architecture guides. It does not claim to implement the separate whole-monorepo teaching program or live presentation-editing service. The source inventory and narration-integrity gates establish the baseline.
Visual thesis#
An annotated field guide to Eve: cream paper, ink, terracotta, a clear Georgia claim and readable Arial evidence. Show the actual working surface when it helps recognition, a concrete record when it explains work, and a labeled relationship when ownership or state would otherwise be ambiguous.
Content plan#
Open with a concrete enrollment investigation. Follow that subject through graph selection, coverage, the task, decision, delivery and the final practice. Use a related Tara content request for Studio analysis/actions and actual member-operation examples for the member chapter. Preserve the distinction between fixture/illustrative records, implemented UI and live evidence.
| Guide | Treatment to finish | Acceptance |
|---|---|---|
| Capabilities | Concrete opening case; remove repeated masthead | The first slide makes the reader's task tangible. |
| Product graph | Pinned Explorer capture and selection detail | The real UI, fixture identity and typed links are legible. |
| Coverage | Concrete traceability specimen | Report version, direct coverage, waiver and freshness remain distinct. |
| Work | Implemented Work lens and complete lifecycle/recovery | All ten states and legal exits remain inspectable. |
| Decisions | Worked ADR and explicit successor link | Proposal, acceptance and replacement have separate authority. |
| Delivery | Lease specimen, verifier branches, recovery and manifest evidence | Remove the four-table run without losing any verifier rule. |
| Walkthroughs | Real board with controlled drift data | Run/current versions, skips and removed pending flows are honest. |
| Operator | Incident specimen and serving-configuration boundary | Recorded state, scope and proposed action remain separate. |
| Studio analysis | Concept dossier, evidence relationships and evaluator specimen | Break the five-table run; retain all registered-view teaching. |
| Studio actions | Related brief, gated transition and calendar case | Saved plan, handoff and actual publication remain separate. |
| Member | Specific supported requests and scoped operation examples | Room, identity and write confirmation are visible. |
| Practice | One enrollment case through the complete close | Each artifact contributes a precise, bounded claim. |
Retain useful comparisons and exact-value tables with a recorded reason. No layout quota. Every Eve slide receives a brief and retain/change decision tied to its final content hash, ordered guide context and visual evidence.
Interaction thesis#
Preserve slide entrance, source disclosure and workspace navigation with reduced motion. Product captures remain readable static evidence; full images are available without implying that the slide itself operates Eve. Keyboard focus, unavailable images and complete print meaning receive explicit checks.
Craft and evidence#
Define scoped typography tokens and actual-size floors; remove repetitive metadata and redundant captions before shrinking content. Review complete sequences, actual embedded views, mobile and the final PDF pages. Reuse unchanged speech only after checking both its fingerprint and what its visual references say. Add concrete visible examples without inventing deployed measurements.
Capture implemented components from the exact source pin with declared, deterministic fixture inputs. Retain source/fixture/image hashes and a runnable capture harness. Never label those records as production data or use a screenshot as proof of backend wiring. Quantitative examples state the denominator, missing values, provenance and scenario assumptions.
Extend the existing targeted Python, builder, source/crosswalk, browser, axe, PDF and center-smoke checks. Run expensive checks serially with resource supervision. Changes to shared rendering require the existing full-bank layout check once after the affected checks pass. Do not repeatedly run unchanged gates. The final receipt binds actual artifacts and records model review separately from any willing-reader observations.
Reader tasks are written before final stimulus capture. Human comprehension is not inferred from model review or automation, and unperformed reader sessions cannot be marked complete. Continue all independent implementation to publication.