# Elikem Granular Review — delivery sequence and coverage

Prepared 2026-10-03 at Elikem's request. The scope comprises the [product requirements](https://docs.dev.oshunsynthetics.com/workspace?document=fb680693-0045-46aa-bd1e-b8501a581922) and [architecture/implementation contract](https://docs.dev.oshunsynthetics.com/workspace?document=3bcaa502-52b6-41fb-884b-476cd8859593). This document is an index and acceptance contract; the Eve board is the authoritative task record. There are no writable tracker checkboxes here.

Revision 4 (2026-10-03) applies an instruction of Elikem's, as his assistant reported it (unverified; see Attribution and evidence), to adopt the assistant's review and a Codex read-only second opinion: five work packages added (EGR.33 triage and tiers, EGR.34 chunk-plan preview pilot, EGR.35 vertical-slice pilot, EGR.36 watermark-backed current sign-off, EGR.37 operational-approval bridge), dependencies resequenced so the owner sees chunks early and platform preparation starts early, and existing package bodies extended.

## 1. Delivery state and activation boundary

The plan defines 40 work packages: 37 in eve-workspace-ux and 3 in platform-ops. All are created as later with explicit dependency edges, acceptance criteria, verification requirements, implementation seams and stable links to the scope documents. Seven existing workspace UX tasks are reused; they are not duplicated, reprioritized or activated by this scope. These documents are submitted for review, not approved or published by their author.

Elikem has agreed the additive personal-review concept, asked for full scoping, and, as his assistant reports (unverified; see Attribution and evidence), on 2026-10-03 instructed that the review recommendations be applied. Scoping snapshot, 2026-10-03: at that date coding, backfill execution, feature exposure and UAT publication had not begun, and every package was created as later. Board state, read from Eve at 2026-10-05T00:42Z: of the 37 EGR packages in eve-workspace-ux, 22 are shipped (EGR.01 to EGR.14, EGR.16, EGR.18, EGR.19, EGR.21, EGR.26, EGR.33, EGR.34 and EGR.36) and 15 are ready; the board is the authoritative record and this line is a dated reading of it. Shipped means implemented, committed to main and verified by the task's own tests. It is not rollout: the EGR.01 census ran once as a read-only dry run, no backfill has been executed against a campaign, and committed code grants no feature exposure, UAT promotion or publication, which follow their own separately authorized gates. Activation of the selected implementation sequence and required PRD/architecture approvals follow existing Eve governance. Nothing in this plan turns on Automatic worker, Automatic reviewer or delegate switches. The current workers continue their existing work.

## 2. Delivery order

1. Foundation: census with per-membership revision selection, contracts, persistence and authority (EGR.01–04). EGR.03 and EGR.04 are one milestone: persistence is never exposed without owner authority and durable receipts. Resolve historical source uncertainty visibly rather than silently assuming every document is classifiable. The acceptance corpus (EGR.26) starts here, beside EGR.01 and EGR.05, and grows as capabilities arrive.
2. Deterministic core: anchors, plans, the first owner pilot, triage and tiers, frozen campaigns, sequence, personal decisions and drafts (EGR.05–11, EGR.33, EGR.34). EGR.34 is a read-only owner preview of generated chunk plans over about ten real documents. It gates both the Workspace phase (EGR.18 depends on it) and the Evolution phase (EGR.12 depends on it, and EGR.13–15 and EGR.36 inherit the gate), because both build on the chunk and anchor semantics it validates.
3. Workspace vertical slice and second owner pilot: queue, reader, recovery, baseline synthesis including “review completed, changes required”, platform preparation and the pilot (EGR.16, EGR.18, EGR.19, EGR.21, OPS.01, EGR.35). Current coverage is labelled unavailable in the slice. EGR.35 gates assistance (EGR.17), plan-editing surfaces (EGR.20) and client/CLI/MCP exposure (EGR.25), and through them the Integration phase.
4. Evolution: revision mapping, dependency drift, durable background work, the content watermark and inventory generation, current sign-off, deliberate follow-ups and assistance (EGR.12–15, EGR.17, EGR.36). Once EGR.34 is complete this phase may proceed in parallel with the Workspace slice; it is service work with no owner-facing surface until the Workspace tasks consume it.
5. Remaining Workspace: plan editing, catch-up, findings, synthesis and signed-history views, and the operational-approval bridge (EGR.20, EGR.22–24, EGR.37), after their individual service/shared UX dependencies.
6. Integration and verification: client/CLI/MCP, representative corpus, real-service non-interference, production-backed browser/accessibility and scale/recovery tests (EGR.25–29). Each implementation task also carries its own tests; this phase verifies the integrated behavior.
7. Release: health/guidance, exact candidate and pilot rehearsal (EGR.30–31); authorized Dev rollout/backfill (OPS.02); full acceptance closure (EGR.32). OPS.03 is conditional on a later request to promote a named tested UAT publication and does not block Dev completion.

The board's dependency edges enforce the two pilot gates exactly as stated here and in PRD §14; the table in §3 is the readback. This is a dependency sequence, not a promise of concurrent agent execution or calendar duration. M denotes a focused but substantial work package; L denotes a larger cross-cutting package that may need subdivision after the census/contracts. There are 25 M and 15 L packages. Do not present their sum as an elapsed delivery estimate; re-estimate against actual corpus size, shared-prerequisite readiness and verified implementation seams. Every discussed core feature is in the full release; staging behind a flag does not make a partial slice complete, and the two pilots are feedback gates, not releases.

## 3. Board work packages

Task bodies contain the detailed scope, acceptance cases, paths and checks. Dependencies shown here are the planned authoritative board edges, not informal reading suggestions.

| Task | Work package | Size | Depends on |
|---|---|---|---|
| [eve-workspace-ux:EGR.01](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.01) | census historical sources, per-membership revision selection and product-version membership | M | — |
| [eve-workspace-ux:EGR.02](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.02) | define domain, state, authority and API contracts, including the dispatch provenance extension | M | EGR.01 |
| [eve-workspace-ux:EGR.03](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.03) | add isolated persistence, immutable events and additive migrations (one milestone with EGR.04) | L | EGR.02 |
| [eve-workspace-ux:EGR.04](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.04) | enforce owner authority, execution provenance, visibility states and durable command receipts | L | EGR.03 |
| [eve-workspace-ux:EGR.05](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.05) | build lossless review projections, source anchors and coverage proofs | L | EGR.02 |
| [eve-workspace-ux:EGR.06](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.06) | generate coherent deterministic chunk plans, default questions, claim labels and calibrated estimates | L | EGR.05 |
| [eve-workspace-ux:EGR.07](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.07) | version review plans with safe split, merge, reorder and exclusion | M | EGR.03, EGR.04, EGR.06 |
| [eve-workspace-ux:EGR.08](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.08) | create frozen campaigns and resumable historical backfill | L | EGR.01, EGR.03, EGR.04, EGR.07 |
| [eve-workspace-ux:EGR.09](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.09) | recommend the next review by version, tier, prerequisites and time | M | EGR.07, EGR.08 |
| [eve-workspace-ux:EGR.10](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.10) | record personal decisions (including cut from scope) and compute honest progress | M | EGR.04, EGR.07, EGR.08 |
| [eve-workspace-ux:EGR.11](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.11) | persist private annotations, questions, drafts, resume positions and measured durations | M | EGR.04, EGR.07, EGR.10 |
| [eve-workspace-ux:EGR.12](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.12) | map revision changes conservatively and generate catch-up work (Evolution gate on pilot 1) | L | EGR.05, EGR.07, EGR.10, EGR.34 |
| [eve-workspace-ux:EGR.13](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.13) | surface cross-document dependency drift, related requirements and synthesis concerns | M | EGR.09, EGR.12 |
| [eve-workspace-ux:EGR.14](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.14) | process content changes with bounded durable jobs, watermark advancement and reconciliation | L | EGR.08, EGR.12, EGR.13 |
| [eve-workspace-ux:EGR.15](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.15) | dispatch owner-approved concerns, cut-from-scope proposals and standing decisions into existing workflows, mapped by document kind and lifecycle state | L | EGR.04, EGR.11, EGR.12 |
| [eve-workspace-ux:EGR.16](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.16) | implement baseline synthesis and personal sign-off with the three outcomes | M | EGR.10, EGR.11 |
| [eve-workspace-ux:EGR.17](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.17) | add grounded chunk suggestions and in-context explanations | L | EGR.05, EGR.06, EGR.11, EGR.13, EGR.35 |
| [eve-workspace-ux:EGR.18](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.18) | add Workspace entry, tiered queue, triage mode and progress overview | M | EGR.09, EGR.10, EGR.33, EGR.34 |
| [eve-workspace-ux:EGR.19](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.19) | build the focused source reader, context inspector and personal decision controls | L | EGR.10, EGR.18, DC.05, DC.15 |
| [eve-workspace-ux:EGR.20](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.20) | add campaign inventory, triage and chunk-plan editing surfaces | L | EGR.07, EGR.08, EGR.18, EGR.33, EGR.35 |
| [eve-workspace-ux:EGR.21](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.21) | deliver draft recovery, annotations and cross-device resume | L | EGR.11, EGR.19, M0.04, M0.05, M0.08 |
| [eve-workspace-ux:EGR.22](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.22) | show revision diffs, dependent changes and catch-up-only review | M | EGR.12, EGR.13, EGR.14, EGR.19, DC.02, M0.07 |
| [eve-workspace-ux:EGR.23](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.23) | add concern dispatch preview, standing-decision capture and result-resolution workflow | M | EGR.15, EGR.19, EGR.21 |
| [eve-workspace-ux:EGR.24](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.24) | add document/version synthesis and signed-history views | M | EGR.16, EGR.20, EGR.22, EGR.23, EGR.36 |
| [eve-workspace-ux:EGR.25](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.25) | expose bounded read/preparation operations and decision visibility through client, CLI and MCP | M | EGR.04, EGR.08, EGR.09, EGR.11, EGR.14, EGR.15, EGR.35 |
| [eve-workspace-ux:EGR.26](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.26) | assemble historical and adversarial acceptance corpus (grows with capabilities) | M | EGR.01, EGR.05 |
| [eve-workspace-ux:EGR.27](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.27) | prove persistence, concurrency and operational non-interference | L | EGR.10, EGR.11, EGR.14, EGR.15, EGR.16, EGR.25, EGR.26, EGR.36 |
| [eve-workspace-ux:EGR.28](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.28) | verify the complete browser journey and accessibility | L | EGR.20, EGR.21, EGR.22, EGR.23, EGR.24, EGR.26, EGR.27, EGR.35, EGR.37 |
| [eve-workspace-ux:EGR.29](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.29) | validate load budgets at five to ten times the live corpus, privacy boundaries and recovery | L | EGR.14, EGR.25, EGR.27, EGR.28 |
| [eve-workspace-ux:EGR.30](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.30) | add health signals and author operator/user guidance in Eve | M | EGR.14, EGR.15, EGR.24, EGR.25, EGR.29 |
| [eve-workspace-ux:EGR.31](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.31) | assemble a fully tested release candidate and pilot rehearsal | M | EGR.17, EGR.25, EGR.27, EGR.28, EGR.29, EGR.30, OPS.01 |
| [eve-workspace-ux:EGR.32](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.32) | close full-feature acceptance with owner pilot and Dev evidence | M | EGR.01–31, EGR.33–37; OPS.02 |
| [eve-workspace-ux:EGR.33](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.33) | owner triage, campaign tiers and an honest hours denominator | M | EGR.01, EGR.03, EGR.04 |
| [eve-workspace-ux:EGR.34](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.34) | owner preview of generated chunk plans before any UI investment (pilot 1; gates EGR.12 and EGR.18) | M | EGR.01, EGR.05, EGR.06 |
| [eve-workspace-ux:EGR.35](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.35) | vertical-slice owner pilot on a small frozen campaign (pilot 2; gates EGR.17, EGR.20, EGR.25) | M | EGR.16, EGR.18, EGR.19, EGR.21, OPS.01 |
| [eve-workspace-ux:EGR.36](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.36) | current-manifest sign-off on a transactional content watermark and inventory generation | M | EGR.13, EGR.14, EGR.16 |
| [eve-workspace-ux:EGR.37](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.37) | operational approval bridge and review-queue entry points | M | EGR.18, EGR.19, EGR.36 |
| [platform-ops:EGR.OPS.01](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=platform-ops%3AEGR.OPS.01) | prepare platform migration, owner-only flagged exposure, workload isolation and recovery | M | EGR.03, EGR.04 |
| [platform-ops:EGR.OPS.02](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=platform-ops%3AEGR.OPS.02) | roll out in Dev, execute backfill and record Elikem pilot | M | EGR.OPS.01, EGR.31 |
| [platform-ops:EGR.OPS.03](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=platform-ops%3AEGR.OPS.03) | promote a specific tested UAT publication only when requested | M | EGR.32 |

## 4. Shared prerequisites and overlap resolution

The source is Eve UX audit d81ff4ab-c540-4c0f-8855-20db7559413e revision 3, read 2026-10-03. Its existing 95-task family remains unchanged. Shared dependencies are limited to directly needed behavior; this feature does not wait for every unrelated Workspace improvement.

| Existing task | Reuse | New consumer |
|---|---|---|
| eve-workspace-ux:DC.02 | Real revision diff, with shared component reuse | EGR.22 |
| eve-workspace-ux:DC.05 | Long-document reading/search and sound source boundaries | EGR.19 |
| eve-workspace-ux:DC.15 | Accessible diagram source/alternatives | EGR.19 |
| eve-workspace-ux:M0.04 | Draft protection and subject-scoped form state | EGR.21 |
| eve-workspace-ux:M0.05 | Response/subject binding and retry recovery | EGR.21 |
| eve-workspace-ux:M0.07 | Revision-aware URLs | EGR.22 |
| eve-workspace-ux:M0.08 | Structured errors and session recovery | EGR.21 |

Existing board mechanisms reused without new implementations: task→document bindings and links (implementation status per span; the bounded decision-visibility read through task context), the standing-decision record (capture from a rationale), and the content review command (the bridge in EGR.37 calls it unchanged). Read alongside the already shipped eve-gap-analysis:R02.6 deterministic revision-summary work. It is not semantic approval evidence and does not replace the conservative correspondence tests. A future unified Decisions landing page can link to granular review; completion of that broader page is not a prerequisite. If a shared task ships an equivalent capability under a successor key, reconcile the dependency with evidence through Eve rather than quietly duplicate it.

## 5. Requirement-to-work coverage

| Requirement | Required delivery |
|---|---|
| GR-01 Existing/future corpus, v0 forward, per-membership revision selection, owner triage and tiers | EGR.01, .02, .03, .08, .14, .20, .26, .33; OPS.01–02 |
| GR-02 Coherent 5–15-minute chunks, default questions, claim labels, calibrated estimates, exact coverage, split/merge/reorder | EGR.05–07, .11, .17, .20, .26, .34 |
| GR-03 Guided sequence by version and tier, dependencies, time budget, filters and resume | EGR.09, .13, .18, .21, .33 |
| GR-04 Exact source, implementation status and reviewer findings in context, actions including cut from scope, undo window, owner authority and execution provenance | EGR.02–05, .10–11, .13, .17, .19, .25, .27–28, .34 |
| GR-05 Durable drafts, measured durations, cross-device resume and failure recovery | EGR.03–04, .11, .14, .21, .25, .27–30 |
| GR-06 Stable historical decisions, content watermark, scoped equivalence, selective catch-up with provenance | EGR.07–08, .10, .12–14, .22, .26–29, .36 |
| GR-07 Private concerns, cut-from-scope and standing-decision dispatch, owner resolution semantics | EGR.10–11, .15, .23, .25, .27–28 |
| GR-08 Synthesis with three outcomes, baseline and watermark-checked current sign-off, operational-approval bridge | EGR.02–03, .13, .16–17, .24, .27–28, .36, .37 |
| GR-09 Progress per tier, notes, bookmarks, explanations and useful ergonomics | EGR.10–11, .17–18, .21–24, .28–30, .33 |
| All requirements: owner pilots, rollout, independent review, full completion | EGR.34–35, .31–32; OPS.01–02; conditional OPS.03 |

## 6. Verification and release acceptance

Implementation tasks run the checks appropriate to their changes. Dedicated integration tasks verify the full loop rather than postponing all testing until the end; the non-interference and browser recovery suites start with the vertical slice and extend as capabilities arrive. Required avenues include affected lint, typechecking, unit/property tests, schema/migration validation, real PostgreSQL service and task-bridge integration, client/MCP contracts, assistance grounding evaluations, production build, Playwright end-to-end, axe/accessibility, controlled performance and recovery/security tests. Applicable existing regression suites remain required.

PRD scenarios P01–P15 are the acceptance map: inventory completeness; historical review while workers continue; resume/time-budget behavior; plan lineage; selective revision/dependency drift; races/expiry; exactly-once deliberate handoff; manifest-bound synthesis; accessible complex-source reading; owner-only authority; triage, tiers and per-membership provenance (P11); “review completed, changes required” and resolution semantics (P12); implementation status, claim labels and reviewer findings in context (P13); the operational-approval bridge and watermark refusal (P14); execution provenance for assistant-executed decisions (P15). EGR.26 supplies their corpus, .27 service/isolation proof, .28 browser proof, .29 load/privacy/recovery proof, .31 exact candidate rehearsal and .32 final evidence reconciliation. The two owner pilots (EGR.34, EGR.35) record orientation, chunk coherence, decision effort versus estimate and interruption recovery as evidence; latency and coverage percentages alone do not establish that the workflow reduces owner burden.

The strongest invariant is operational non-interference. For every personal command, including triage and the bridge's link and coverage display, compare canonical content states/revisions, operational reviews, task readiness/leases, automation switches and publication selection before/after. Test the feature disabled and unavailable. Only an explicitly confirmed handoff, or the bridge's explicitly clicked existing approve action, may create its previewed downstream effect. Concurrent source edits must not prevent deliberate review of a pinned baseline; current sign-off must nevertheless reject a moved content watermark, including relation, archival and asset changes.

Use isolated fixtures and disposable databases. Run expensive targets serially after host resource checks, respecting AGENTS.md. Do not test mutations against production content. Every receipt identifies exact commit, source/plan/corpus versions, environment, command and outcome. A blocked check requires explicit evidence and a resolution; it cannot be silently treated as passing. Reviewer identities remain independent; Elikem owns required product/architecture decisions and publication.

## 7. Platform and ownership handoff

Product workers implement services, UI, contracts and tests, and author guides/evidence through Eve. Platform-ops prepares host resources, backups, schema rollout, owner-only flagged exposure for the vertical-slice pilot, bounded background jobs, migration/backfill execution and release-controller deployment. OPS task bodies use Observed, Evidence, Impact, Suspected cause and What would close it; these are planned dependencies, not fabricated incidents.

OPS.01 now follows the schema and authority milestone (EGR.03, EGR.04) so deployment constraints surface before the Workspace phase; it prepares without exposing the feature beyond the owner-only pilot flag and re-checks background-job isolation once EGR.14 lands (verified in EGR.29). OPS.02 requires the normal approvals and explicit rollout authority, runs dry-run then authorized backfill, enables the owner view and records the live pilot. OPS.03 requires an explicit later UAT promotion instruction. Personal drafts/notes are excluded from ordinary publication snapshots; UAT remains read-only. Disable/rollback preserves immutable personal review history and pending dispatch receipts.

## 8. Assumptions and decisions recorded by this scope

The conversation settles the name, additional-layer model, zero fresh personal approvals, v0-forward sequencing, coherent 5–15-minute units, exact source decisions, change tracking, final personal synthesis and preservation of worker progress. Recommended details in the PRD/architecture include private notes by default, explicit historical acknowledgement, no automatic carry-forward approval, and owner confirmation before dispatch.

Revision 4 records the instruction of 2026-10-03, as Elikem's assistant reported it (unverified), to apply the assistant's review and a Codex read-only second opinion: owner triage and campaign tiers sized against the corpus (measured by the EGR.01 census: 1,085 review candidates; see Attribution and evidence); per-membership revision selection with a provenance class instead of a single approval-recency default; a “review completed, changes required” synthesis outcome; a transactional content watermark for current sign-off; a bridge to the existing operational approval with one approval surface; implementation status, claim labels, reviewer findings and revision provenance in the review context; a cut-from-scope outcome; bounded decision visibility to agents; standing-decision capture; a calibrated estimator; execution provenance bound to the instruction; a scale gate at five to ten times the live corpus; and two owner pilots. Revision 9 answers the independent review of revision 5 (reviews 24125a50, d734ae8e, 654d5178): visibility states and P07, an inventory generation beside the watermark, dispatch mapped by document kind and lifecycle state with one governed provenance extension, and the Evolution phase gated on the first owner pilot through EGR.12.

Revision 12 answers review 65f10c10 on revision 10. EGR.24 and EGR.16 now follow PRD GR-08 and P08: a required chunk counts as examined only when it carries a submitted decision other than defer; a deferred or unexamined required chunk, unavailable or ambiguous required source, or an open question refuses every completed outcome (“approved”, “changes required”, “completed with exclusions”) and lists the exact gap; open change requests and cut-from-scope decisions on examined chunks refuse “approved” only. Both tasks name the matching outcome-matrix and browser cases. The companion PRD and architecture revisions this index was checked against are pinned as references.

Revision 18 answers Elikem delegate decision 0a33058f on revision 16: §1 now dates the 2026-10-03 scoping snapshot and gives a dated reading of the board (22 of 37 EGR packages shipped, 15 ready), keeping implementation apart from backfill, feature exposure and publication.

Revision 20 answers review 27ad2589 of revision 19 under Elikem's delegate answer to question 4799104c: the 2026-10-03 instruction is labelled reported but unverified, the missing search receipts stay disclosed, and the withdrawn corpus estimates are replaced by the approved EGR.01 census as new, dated evidence.

**Attribution and evidence.** The 2026-10-03 instruction to apply the review is **reported but unverified**: Elikem's assistant reports that Elikem gave it in their conversation, and it is not recorded in Eve; the original conversation is not recovered. Elikem's delegate decided on 2026-10-05 (answer to question 4799104c, 04:13Z) that this record is reviewed on its current merits without that recovery. Elikem's own operational approvals of the companion PRD (revision 13, approved 2026-10-04, reviewer of record his user account) and architecture (revision 12, approved 2026-10-04) are the attributable record of the scope those revisions carry, including the revision-4 changes; both are pinned below.

The corpus figures this record first gave (prd 8; adr and architecture more than 100 each; spec 300–450; guide more than 1,000; 11,450 documents; roughly 600–800 eligible) came from searches the author ran by kind on 2026-10-03; their receipts (queries, pagination, eligibility derivation) were not preserved and remain unavailable, so they are not evidence and are withdrawn. **New evidence** replaces them: the [EGR.01 historical census, revision 8](https://docs.dev.oshunsynthetics.com/workspace?document=3daa379f-1a17-4096-8b07-e6115132fc46&revision=8) (approved), a read-only walk of the whole content event feed to a fixed cutoff (2026-10-04T15:58:27Z), its files kept as Eve media with their SHA-256. It counts 11,541 documents (guide 4,201; spec 338; adr 154; architecture 152; prd 8; the rest other kinds) and 1,085 review candidates (433 technical-spec, all flagged uncertain for Elikem to confirm; 338 spec; 154 adr; 152 architecture; 8 prd), plus 199 documents of other kinds listed as possibly misclassified. The earlier estimate of 600–800 eligible documents was low. The sequencing and coverage claims here rest on the board's dependency edges (read back in §3) and the approved PRD and architecture, not on the corpus count; the count sizes triage and hours, which the census and Elikem's triage (EGR.33) now measure.

Corpus mapping, measured performance budgets, exact owner provisioning and the admitted assistance seam are implementation discovery items with named tasks; none is represented as already verified in production. The scope does not ask for new model/provider spending, key privileges, automation activation, external messaging, operational blocking or publication. A later owner instruction can authorize the normal corresponding action.

Useful additions included: bookmarks, passage comments, cross-device resume, where-you-left-off recap, keyboard navigation, changed-only catch-up, grounded explanations, undo window and standing-decision capture. Deferred as unnecessary for this release: gamification/streaks, review quotas, external reminders, a new native app, multi-owner policy and automatic approvals. These are not missing core work packages.

## 9. Definition of complete

Scope completion means three canonical Eve documents submitted for review, 40 correctly linked later tasks, valid dependencies, complete requirement coverage and verified API readback. It does not mean the product is implemented.

Feature completion means all required functionality is implemented, exact commits are present on origin/main, applicable checks pass, required content is reviewed, acceptance findings are resolved, both owner pilots and the platform-owned Dev rollout have evidence, and recovery is proven. UAT promotion is conditional and separate. Elikem actually completing his review of the corpus he triaged into the must-review tier is ongoing use of the feature, not an engineering delivery gate.

## Related Eve records

- [Product scope and acceptance](https://docs.dev.oshunsynthetics.com/workspace?document=fb680693-0045-46aa-bd1e-b8501a581922).
- [Architecture and implementation contract](https://docs.dev.oshunsynthetics.com/workspace?document=3bcaa502-52b6-41fb-884b-476cd8859593).
- [Existing Workspace UX audit](https://docs.dev.oshunsynthetics.com/workspace?document=d81ff4ab-c540-4c0f-8855-20db7559413e), revision 3 read on 2026-10-03; existing tasks are reused without rewriting that audit.
- Owner pilots: [chunk-plan preview](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.34) and [vertical-slice pilot](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.35).
- [Final feature acceptance task](https://docs.dev.oshunsynthetics.com/workspace?view=tasks&task=eve-workspace-ux%3AEGR.32).
