Record for eve-workspace-ux:EGR.26, prepared 2026-10-04 by claude-workspace-ux-31-220-93-15 (commit 47e106380c). It documents the corpus's provenance, version, expected outcomes and limitations. Submitted for independent review; its author does not approve it.
Provenance#
Every fixture is synthetic and sanitized, written for this corpus: no production document text, private note, credential or personal data. The census fixture (tools/eve-content/testing/granular-review-census-fixture.json) models Eve's content API reads; the format and claim fixtures live in tools/eve-content/testing/fixtures/granular-review-corpus/, stored byte-exact (Git -text, excluded from Prettier) so CRLF and spacing are part of the test. A test refuses fixtures carrying Eve keys, private keys, password fields or production addresses.
Cases and expected outcomes#
| Case | What it covers | Expected |
|---|---|---|
| v0 PRD by source path | v0 membership | included; revision 1 by source lineage |
| V1.3 PRD, approved then edited | release association on an older approved revision | revision 3 by release association, not the later draft |
| Architecture with no version evidence | shared foundation | latest approved revision, labelled without version-specific provenance |
| Guide titled as an API specification | misclassified technical specification | technical-spec, uncertain, spot check |
| Reference titled as an ADR | misclassification | unresolved until its kind is confirmed |
| V4 product root spec | V2–V10 roots | historical context |
| Archived ADR | history | historical context |
| Walkthrough | out of scope | excluded with its reason |
| In-review shared spec | none-latest-draft | latest in-review revision, labelled |
| Spec under docs/releases/v1.1 with release V1.2 | two memberships, two provenance classes | v1.1 revision 1 by lineage; v1.2 revision 3 by release |
| Unreadable spec | missing source | unresolved, not dropped |
| complex-formats.md | CRLF, nested lists, a table, inert HTML, a mermaid diagram, SQL code, a reference definition, a footnote | complete coverage; primary units heading, paragraph, heading, list item ×2, table, html, diagram, code, footnote; table, code and diagram whole in one chunk; the definition an excluded unit |
| asserted-vs-proposed.md | claim labels | "already issued … recovery.ts" and "currently reset" asserted-existing; "will let" and "must expire" proposed; "The support team reviews" unknown |
| shared-foundation.md | architecture question | "Is this boundary or contract correct?"; an unmarked statement unknown |
Seeded faults the suite must catch#
A silently omitted unit (a primary unit removed from its chunk), a wrong anchor (a range shifted by one character), a wrong provenance class (a release association removed from a fixture), a mislabelled claim (a proposed label flipped to asserted-existing) and a silently dropped census document. Each is asserted to produce a named failure.
Limitations and planned extensions#
- Correspondence outcomes, including "unchanged, dependencies uncertain", join when EGR.12 exists; grounded-assistance evaluation labels when EGR.17 exists; each as a logged extension with a new corpus version.
- Browser-level fixtures for EGR.28 extend
apps/oshun/eve-content/scripts/browser-fixture.e2e.tswhen the Workspace surfaces exist. - Scenario coverage P01–P15 grows with the capabilities that exercise them; the census, coverage, anchor, plan, question and claim checks exist now, before EGR.34.
Verification#
node --test tools/eve-content/granular-review-corpus.spec.mjs: the census and each document match their expectations, the seeded faults fail, and the fixtures carry no secrets.