# Eve task board and monorepo backlog rationalization Date: 19 September 2026. Audited code: `e6a64111e3abb96af5a89d194d5c2c8c2d023724`. Status: **proposal for review; no implementation or task-state changes authorized by this report**. The recommended direction is to complete a few usable, governed vertical slices on the architecture already present, with one implementation owner per capability. Preserve the owner's presentation-first priority, but repair the board's dependency semantics before trusting its readiness claims. Consolidate acceptance checklists around those slices, separate release and external proof from build work, and stop counting historical plans as additional implementations. The September 18 audit and its subsequent rewrites improved the backlog substantially. They did not establish that every rewritten task is still necessary. This pass found already-implemented safety-service work, missing cross-family dependencies, requirements hidden outside the board, and runtime deployment gaps in the newest presentation plan. ## 1. Scope, method, and what the numbers mean The audit inventories every current board row, every tracked checkbox-bearing Markdown file, the committed document catalog, and comment-like code debt markers. Recommendations cover every open item through a logical group. Source review followed the owners, entrypoints, contracts and infrastructure relevant to those groups, with focused tests where they could disprove a task premise. It is **not** a claim to have manually verified every implementation behind 24,822 checkboxes or rerun the monorepo's complete test portfolio. The [evidence bundle](eve-task-rationalization-2026-09-19/README.md) includes: - [Exact measurements](eve-task-rationalization-2026-09-19/summary.json). - [Every open task's proposed home and disposition](eve-task-rationalization-2026-09-19/task-dispositions.tsv): 24,822 keys, each mapped exactly once, preserving source path, line, current state and blocker. - [Every checkbox file](eve-task-rationalization-2026-09-19/file-inventory.tsv): 1,411 files, with classification, counts and content hash, including all 75 files with open implementation-tracker items. - [Document catalog](eve-task-rationalization-2026-09-19/document-catalog.tsv): source documents indexed separately from generated slide and Docs Center entries. Catalog inclusion is discovery coverage, not proof that every paragraph is an adopted requirement. - [Inline debt markers](eve-task-rationalization-2026-09-19/code-markers.tsv) and [repeated wording](eve-task-rationalization-2026-09-19/repeated-wording.json). - A read-only [inventory and accounting checker](eve-task-rationalization-2026-09-19/inventory.mjs). | Board item kind | Open | `ready` | `later` | `parked` | | ------------------------------ | -----: | ------: | ------: | -------: | | Implementation trackers | 13,319 | 3,752 | 8,485 | 1,082 | | Coverage walks | 10,204 | 9,621 | 583 | 0 | | Release/store/compliance gates | 1,299 | 0 | 0 | 1,299 | | Total | 24,822 | 13,373 | 9,068 | 2,381 | There are 51 registry families and 38 database families. The other families classify proposals, inventories and reference material. The database has 34 retained terminal rows; these are **not** a count of all completed work, since most historical checked items were never imported as task rows. Outside the execution board are 8,845 unchecked proposal boxes, 26,648 unchecked inventory boxes, and 2,040 unchecked template/reference boxes. Do not add these to the implementation backlog. Some are duplicates; some are operating checklists; some require a fresh adoption decision. The current document catalog contains 16,379 entries, including generated presentation and reader entries. The Markdown inventory contains 11,472 files before this report. The source-marker scan found 152 comment-like `TODO`, `FIXME`, `HACK` or `XXX` matches in 84 files under apps, libraries, services and tooling. Many are quoted fixtures, generator scaffolds or references to task IDs. The bundle labels them as such; 152 is not a defect count or an exhaustive count of incomplete code. ## 2. Current architecture and the coherent path forward | Concern | Current evidence | Recommended boundary | | ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | V1 release | `libs/oshun/navigation/src/release-scope.ts`: V1.0 is Tara, Nyx, Arete and Nisaba on web/PWA; native apps and fiat rails defer to V1.1; Metis and Veritas to V1.2 | Attach a release scope to each deliverable and acceptance run. Operator development may precede a customer release without advertising a deferred room. | | Customer and operator surfaces | `apps/oshun/{web,admin,tenant-admin,mobile,bff}` and shared navigation/contracts/persistence already exist | Extend the actual owning surface. Avoid another generic workbench, assistant shell or domain backend merely because an old plan proposes one. | | Presentation host | Admin `/presentations`, static-file serving, message contracts and citation navigation have landed; `authoring/four-surfaces-architecture.md` records the host decision | Keep the admin host and existing assistant drawer. Finish trustworthy slide context and reads before edit/generation workflows. | | Presentation runtime | `docker/Dockerfile.node` packages the Node service and adds ffmpeg for BFF; `infra/hetzner/docker-compose.yml` mounts published presentation files read-only into admin | Authoring needs an explicit worker, checkout and artifact-delivery design. A successful local Python subprocess does not establish a deployed editing path. | | Generation | Isis generation API, jobs/chains, output registry, model governance, RunPod desired-state manifests and hosted lanes already provide the control plane | One authoritative job/output/policy chain. Eve, workbenches and film tooling consume it through governed adapters. | | DCC control | Bellona's Blender agent and remote host coexist with Isis's T.20 bridge and several older engine integrations | Share reviewed DCC operations and safety contracts; allow transports to differ. Bellona owns host/execution mechanics, Isis owns generation workflows, and Eve owns intent and approval. Complete the crosswalk before another adapter. | | State and jobs | Existing Postgres persistence, workbench leases, queues and provider ports; some services still use in-memory stores | Reuse lifecycle and persistence seams. A new durable worker is justified by a distinct execution boundary, not by another feature name. | | Deployment | `.github/workflows/deploy-hetzner.yml` is the canonical deployment path; RunPod is separately declared under `infra/runpod` | Consolidate operations around the current deployment and recovery model. Do not resurrect ECS/EKS as an incidental task rewrite. Local Agones experiments for V7 do not change the production decision. | | Language direction | Running estate remains substantially TypeScript/Python plus Rust/native code. `CLAUDE.md` defaults to TypeScript; the September 7 Rust audit recommends a broader Rust-centered architecture | Ratify one prospective language/ownership policy. Continue scoped product fixes in existing owners; migrate a boundary only with conformance, cutover, rollback and retirement evidence. A whole-monorepo rewrite is not a prerequisite for this backlog. | The Telegram bot and Mini App are also explicitly in V1.0 scope in `V1/TELEGRAM_SURFACE_PLAN_2026-08-05.md`; they are not deferred with native mobile. Preserve the chosen BFF transport and channel-specific acceptance. For UI, the required frontend skill supports a primary working surface, navigation and secondary context. Apply that to decks, notes, generation and workbenches. Do not turn every repeated contract cell into another panel, dashboard or independent screen. Keep all required keyboard, accessibility, responsive, state and error behavior as acceptance criteria. ## 3. Findings that change the execution plan ### F01. The scheduler's graph is materially less complete than the plans The database contains 7,700 edges: 7,340 parent/child roll-ups and only 360 explicit prerequisites. **Zero edges cross family boundaries.** This does not mean the products are independent. `tools/eve-task-board/lib/deps.mjs` resolves IDs inside their family and parses selected dependency phrases. It does not encode the Isis tracker's section-level `Dependencies:` blocks as execution edges. The presentation plan references earlier EI items in prose without machine-readable prerequisites. All 52 ready EI items have zero recorded dependency edges, including apply, regeneration, live demonstrations and artifact generation. All 1,115 ready redesign items pass the dependency predicate; Isis has 225 eligible items out of 226 ready. These are availability calculations, not sensible simultaneous starting points. Concrete missing relationships include: - `EI.7.03` after its persistence/service work; `EI.9.02` after the draft, runner, approval, apply and receipt contracts; final live demonstrations after the behaviors they demonstrate. - Isis T.02/T.05 after the relevant model admission; F.20 after the film pilot's actual producers; workbenches I6–I9 after I0.20's crosswalk. - Human-video `182.C.40.01` after consented references and externally fetchable object storage. Its own body says these block the real run, yet it is ready. - Ambient-rail consumers after the simulations they require; presentation chapters after the capabilities they describe; shared label validation after one human-labeled corpus. Recommendation: explicit fully-qualified prerequisite keys, section gates expanded into leaf prerequisites, edge provenance, and a readiness check that blocks unresolved execution dependencies. Do not infer dependencies from every casual citation. Preserve parent roll-ups separately from prerequisites. ### F02. A passing board check does not establish schedulability `./eve check --json` returns no problems and `./eve drift --json` returns empty edited/checked/unknown lists. Nonetheless, `task_links` contains eight `unresolved-dep` entries: | Source | Unresolved target | Correction | | --------------------------------------- | ----------------- | --------------------------------------------------------------------------------------------------------- | | Phase 180 `180.C.29.09`, `.29.12` | `29.08` | Resolve the abbreviated reference to the full phase ID through the synchronized tracker procedure. | | Phase 180 `180.C.36.10` | `36.01` | Same; do not silently consider the absent key completed. | | P2 `V1-P2-4500`, `4501`, `4504`, `4506` | `P14.b` | The target exists as `audit-remediation:P14.b`, at residual-backlog line 1655. Add the cross-family edge. | | P2 `V1-P2-6006` | `18.6` | Resolve the intended tracker and whether this is a prerequisite or a historical reference. | `check.mjs` detects cycles among present task rows, but does not report these unresolved links. Additionally, 56 ready items contain a `[later]` label in their body; the label does not make the database defer them. Some labels may themselves be obsolete. Decide the release/priority once, then make prose and machine state agree. Recommendation: distinguish `open`, `unblocked`, `leased`, `awaiting external proof` and acceptance-only work in reporting. Reconcile prose scheduling labels and terminal-family residue. The closed `eve-task-board` family still contains parked ETB.9.01; expose that remaining live-eval obligation explicitly. ### F03. Task identity and multiple sources of state need a stronger contract 14,335 open rows have no external task ID. Their keys depend on text and headings. The importer already has a three-step identity-reconciliation ladder; this audit does not propose rebuilding it. Substantial rewrites or moves can still change identity without an exact match. Preserve aliases, journals, evidence and old source anchors when adopting the canonical plan. `pull.mjs` mirrors workbench state without checking the tracker box, while `import.mjs` derives state from the tracker and specially preserves terminal state only for procedure-policy families. Audit and test the full promote → lease → pull → import → done sequence, including rejection, verification and lost leases. The separate-command tests do not establish the combined lifecycle. This is a source-indicated integration risk, not a claim that this session observed a live task being lost. The generated `TODOS/BOARD.md` also says context, docs search, merge resolution, promote and pull are not built; their implementations and tests exist. Its fallback merge guidance can discard journals. Generate current help from the implemented command registry and teach the installed row-level merge driver. ### F04. Safety automation was rewritten from stale defect descriptions Fresh result: **all 156 tests in five service test files pass**. This overturns the task text's reliance on old failing-test counts. It does not certify the service for production. | Task | Current code/evidence | Proposed disposition | | ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | SA.1 | Current suite is measurable; `TEST_RESULTS.md` is not refreshed by this audit | Keep only the evidence refresh and correct verification manifest. | | SA.2 | Routes use `request.server.getCronPattern`, `calculateNextRun` and `calculateAverageSecurityScore`; scheduling/metrics tests pass | Retire the instruction to reimplement the old handler fix. Preserve any missing frequency/score edge-case tests as residual acceptance. | | SA.3 | Both `adversarial_prompts` and `harmful_content` templates exist in `src/app.ts`; corresponding tests pass | Retire reimplementation. Retain a category-completeness regression if the existing suite does not enforce it for future categories. | | SA.4 | Top-level metadata is returned; persona/metadata tests pass. `src/types.ts` does not supply the requested shared response contract | Rewrite to the remaining exported contract and response-schema conformance. | | SA.5 | JWT plugin registration exists, but no route `jwtVerify`/authorization enforcement; tests request protected behavior without credentials. Startup has a fallback JWT secret | Keep and strengthen: mandatory production configuration, operator/service scope, route coverage, explicit health/readiness/docs policy. | | SA.6 | Eleven `/v1/evals/` routes are mounted | Retire the mounting premise; verify validation, runner absence, unknown IDs, authorization and failure propagation on those routes. | | SA.7 | Attacks, evaluations, reports and schedules still use Maps | Keep durable storage and restart/crash recovery; environment acknowledgement is not a durable backend. | | SA.8 | Orchestrator-level lifecycle tests exist | Keep an HTTP-level lifecycle with denial, failure, restart and durability evidence; avoid duplicating the existing unit lifecycle test. | Source anchors: `apps/lilith/svc-safety-automation/src/app.ts:53,117,312,334,1601,1979,2021,2053`; `__tests__/safety-automation.test.ts`; `__tests__/health.test.ts` also contains permissive “200 or 400” assertions. This is a good candidate for one small service-hardening workstream, not eight assumed-new implementations. ### F05. Presentation integration needs a deployed write path and narrower milestones EI.1–EI.3's landed host/message/citation behavior should be retained. The final snapshot includes EI.3.06's canonical navigation entry/contextual slide action and EI.3.07's responsive layout, F6 focus transfer and browser verification; do not recreate them. EI.3.07 also fixed a server/client boundary error that component-only tests had missed. Its mobile result explicitly retains the copilot's minimum viewport of 1024 px: keep phone deck access, but do not promise a phone copilot without a separate product/accessibility decision. The upstream completion notes also record an unrelated remaining admin interruption-capability test failure, which belongs in C02's baseline rather than a false claim of a completely green admin suite. The remaining EI.4–EI.6 context, grounding, trust-label and operator-admission work is valid. The large remainder should be separated into read, notes, controlled authoring, and ad hoc artifact milestones rather than one undifferentiated Phase 0. The write proposal assumes BFF can run Python against a writable checkout while admin serves the resulting preview and published files. The checked-in BFF container does not package that Python/rendering environment; admin's published directory is a read-only mount. Local co-location does not solve container visibility, worker permissions, locking across processes, interruption recovery, receipt/file consistency or atomic publication. EI.1.06 packages published output; it does not deliver this authoring runtime. Recommended design: BFF authorizes and records intent, a bounded isolated worker owns a proposal checkout and rendering tools, and admin reads versioned artifacts. Reuse the workbench's execution/lease machinery where it fits; do not grant the general BFF unrestricted write access to the shared checkout. Text edits may remain lightweight jobs, but still need one durable lifecycle and an explicit deployment contract. Stage before publication; use revision hashes for both apply and revert; test crashes between file writes, receipt writes and publish. EI.0.03's parked threat-model task should split into an early design/gap record and later verification of actual controls. The threat model should identify the missing runtime boundary before it is built; it should not claim nonexistent controls as implemented. EI.12's ad hoc decks overlap Eve 8.15's artifact workspace and 17.23's generated media delivery. Share artifact identity, tenant/owner checks, revisions, retention/erasure, attachments and approval receipts; keep deck rendering and slide-specific behavior as a format adapter. Similarly reuse ETB.8.10's committed source corpus work when extending document grounding rather than adding a third independent Docs Center ingestion path. ### F06. Creative ownership remains unresolved at the implementation boundary Workbenches I0.20 and Isis T.21.07 are legitimate reconciliation work. They should produce one acceptance crosswalk used by Eve Phase 5, workbenches I/B, Isis T/F, Neith 144.2.7 and relevant phase-71/78 residue. Shared operations can have both interactive and headless transports without duplicating job, asset or policy authority. T.00.06 asks for the ADR's “nine” questions, specifically Q1–Q9. `ADR-0008-open-3d-studio-capability-ownership.md` §8 has **eleven**, including Q10's two workflow registries and Q11's release qualification. Its acceptance clause requires every question answered, so the task is internally incomplete. Expand it to all eleven, preserve the already-recorded delegation and decisions, and link each answer to an implementation or a deliberate non-goal. Do not repeat yesterday's obsolete claim that Eve 15.7/17.4/17.22 have no reconciliation with Isis: their appended September 18 notes now establish it. The old leading text still names superseded provider owners. Because this tracker has an append-only policy, expose an explicit effective requirement in the canonical crosswalk; alter the original text only through its digest/evidence procedure. Provider-specific implementation should be a choice behind a capability, not a permanent product promise. ### F07. Scope inflation obscures the smallest useful deliverables The workbench ledger holds 8,451 open cells. Its 727 UX/STD/CAP contract cells are requirements and acceptance, not 727 independent builds. Phase Y has 1,370 open cells, V 1,465, E 1,444, A 1,012 and B 1,029. They are now deferred, which is correct; enumerating thousands of behaviors is still not decomposition into verified increments. For each domain, first reconcile existing routes, contracts and providers, then choose a single usable author → validate → persist → review → publish path. Attach the relevant contract cells to that path. Split an implementation only when it has a distinct owner, failure boundary or independently testable output. Do not create a universal workflow framework before two consumers demonstrate a shared need. Do not discard these requirements just to reduce counts. The redesign ledger similarly contains 1,386 open Phase D entries. The repetition screen finds 78 groups containing 820 occurrences across tracker files, mostly chapter procedures. This is a first-line lexical screen, not a count of semantic duplicates. A chapter brief, narration, responsive screenshots, PDF check and receipt can become one parameterized delivery checklist per chapter with independent per-slide evidence. Fifty copies of the procedure need not be fifty different engineering projects. ### F08. Release, host and external-proof gates are mixed with ordinary work Keep V1.0 correctness separate from V1.1 mobile/fiat and V1.2 Metis/Veritas. The operator workbench priority is an owner choice, not proof that those rooms are released. Coverage of a deferred route's refusal remains useful; a full feature journey into that room waits for its release. Phase 182 has seven ready items despite some requiring a consented corpus or publicly fetchable reference assets. Separate packaging and fixture-driven contract tests from real likeness, fairness, performance and release evidence. Use the existing Isis infrastructure contract for delivery, and add the human-video-specific consent and wipe constraints; do not create another GPU control plane. OYA.G1 loads an admitted model from G2, while G2 asks to measure through G1. This is a sequencing knot in the prose even though no graph edge records it. Split G2 into static license/hash admission, G1 into the bounded runtime using one admitted fixture, and then G2's measured performance admission. Apply the same “contract → implement → measure → promote” distinction to GPU and training tasks elsewhere. Hardware-specific captures, full-duration soaks, signing and human review remain real acceptance work. A software Vulkan pass proves functional behavior, not physical-device frame time. A hosted Windows browser test does not prove interactive UAC, GPU capture or certificate-backed distribution. Installable tools are setup steps; account rights, physical devices and people remain explicitly owned dependencies. ### F09. Non-board plans contain both useful intent and stale prescriptions The broad `reference-docs` family includes implementation/migration notes, Psyche security and code-quality audits, Nyx's caching strategy and Yemaya's known limitations. Classification as a reference is not evidence their findings were resolved. Reconcile these documents by source path and current caller; promote surviving defects with a canonical ID. Do not blindly adopt January security prescriptions or numerical targets without checking the live design. Two concrete inline gaps survive source inspection: - `apps/psyche/api-gateway/src/api_gateway/routers/health.py:129` returns healthy database/Redis checks without connecting to either. The router is mounted by `api_gateway/app.py:188`. Add dependency-aware readiness and tests for unavailable/unconfigured dependencies; retain liveness separately. - `apps/aphrodite/streaming/src/routes/metrics.ts` returns constant zero metrics and empty diagnostic results; `/metrics` is mounted in `src/app.ts:228`. Wire actual bounded telemetry or expose unavailable measurements explicitly. Do not count absent measurement as zero traffic/errors. The notification test's rate-limiting TODO is a test-determinism follow-up. Most Iris/Neith marker hits are generated examples or parser fixtures; preserve those examples instead of “fixing” their intended placeholder strings. ### F10. Historical plans and actual product acceptance need separate retirement rules Phase snapshots, the Neith combined proposal and its parts, P2 target inventories and the Antigravity plan are already classified outside live work. Preserve their provenance and link to current owners; do not resurrect them as a second backlog. The Sophia convergence proposal names moved service paths and should be superseded by a current ownership inventory if further convergence is wanted. The two older `AGENTIC_CONTENT_*` trackers still hold 25 open items. Some remain useful, including generation integration, engine import and calibrated quality. Move only their unique residue into the current Isis/content/evaluation owners, then retire the competing ledger authority. A completed function in an older tracker is not proof that an end-to-end generation lane exists today. Other proposal-scale plans need explicit treatment as well: | Source | Treatment | | -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `docs/proposals/SOVEREIGN_STACK_PROPOSAL.md` | Preserve sovereignty and substitutable-provider intent as options. Its proposed wholesale OS/browser/engine replacement is not an adopted prerequisite for current product slices. Reconcile old hosting/mobile assumptions before any bounded experiment. | | `docs/proposals/GALATEA_DOMAIN_PROPOSAL.md` | Domain libraries already exist under `libs/galatea`; do not repeat “create the domain” wholesale. Inventory actual runtime consumers, preserve unique robotics requirements, and separate simulation, physical hardware and training investments. | | `docs/proposals/OYA_DOMAIN_PROPOSAL.md` | Use C22 and the current Oya build tracker as execution authority; retain unmatched concept requirements as options, not a parallel build plan. | | Telegram V1.0 surface plan | Carry surviving channel gaps into C13/C14 and its 42-item C17 acceptance set. Preserve the recorded transport decision; do not reinterpret web/PWA-first as excluding Telegram. | The V1–V9 ledger and phase 180 intentionally use pinned procedures. Their new re-audit/Windows-attempt trackers are evidence-producing feeders, not replacement sources of completion. A retirement or consolidation must update the ledger, manifest and synchronized documents together. The previous audit demonstrated that cosmetic checkbox rewrites can break real release gates. ## 4. Disposition of every implementation family Counts are open entries, including blocked and deferred items. C-numbers refer to the canonical execution groups in §6. The machine crosswalk supplies every individual key; the tables below supply the reasoning for the groups. | Family | Open | Findings and rationalization | Canonical home | | --------------------------------- | ----: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | | Eve task board | 1 | ETB.9.01 is remaining account-dependent live proof; do not rebuild the shipped CLI. Separate this from new scheduler defects. | C12; new C01 | | Presentation redesign | 1,561 | Keep landed EI.3.06/3.07 navigation and responsive integration. Sequence 56 open Phase-0 items by read, notes, authoring and artifacts. Consolidate chapter procedures without dropping slide evidence. | C03–C07 | | Presentation companion | 422 | Keep 32 track plans as content briefs, navigation/address/link work as integration, and sections 6/9/10 as acceptance. Redesign governs; no second pilot or hosting solution. | C07 | | Isis Chroma/RunPod | 249 | Split existing-lane closure, admitted 3D slices, and film. Expand ADR reconciliation; retire optional parked implementations to an option register. | C08–C11 | | Eve SOTA | 111 | Keep the security/eval/reliability admission gates. Share generation/DCC owners and artifact lifecycle. Separate local contract proof from live/corpus/human proof. | C08, C12, C13 | | V1 domain workbenches | 8,451 | Keep 104 scope/baseline cells, 43 dependency cells, 39 shared-platform residue, 830 Isis cells and 147 Metis cells only with code-grounded outputs. Treat 727 contract cells as acceptance; phase the five large deferred domains. | C08, C18, C19 | | Safety automation | 8 | SA.2/3 fix premises already implemented; SA.4/6 partly implemented. Auth, durable storage and stronger route/lifecycle verification remain. | C15 | | Controlled human video, phase 182 | 30 | Package/test locally; release demonstrations require consented references, usable object storage and calibrated corpus evidence. Reuse media delivery infrastructure. | C26 | | Demeter, phase 29 | 161 | Preserve newly specified page-to-API wiring and test-harness repair. Deliver one complete gardening flow before AR/VR/watch/partner expansion. Keep platform/release gates separate. | C19 | | Open world, phase 79 | 166 | Existing crate names are not new implementation work. Finish real rendering/simulation consumers and benchmark them on named targets; avoid inventing a second general engine. | C20 | | Phase 180 synchronized tracker | 23 | Preserve synchronized checklist/tracker/audit ownership. Host parity, signing and usability remain distinct gates. | C25 | | Phase 180 Windows attempt | 6 | Retain bounded CI/browser/fixture attempts; carry results back through the phase's procedure. No automatic workstation-parity claim. | C25 | | Other phases | 400 | Group disposition by capability and host below; do not let an arbitrary phase number create another owner. | C08, C14, C16, C24 | | V1–V9 ledger re-audit | 6 | Preserve changed-assumption probes LRA.1–5 and final LRA.6; consolidate with the real producer tasks rather than perform duplicate live runs. | C23 | | V1–V9 autonomous content | 145 | Preserve pinned standing rules, portfolio gates and external proof. Unpark only the specific obligations released by fresh evidence. | C23 | | V1 P2 backlog | 439 | Reconcile 261 pre-§59 items with residual/domain/platform owners; replace 178 §59–72 mass re-verification items by current acceptance crosswalks where redundant. | C16, C17 | | V2 | 232 | V2.VS.1–7 is the useful first milestone: a playable cooked slice. Later gates, signature checks and launch proof consume it. | C20 | | V5 | 154 | Existing descriptor/function libraries need runtime consumers. Validate a representative content path before bulk assets, campaign quantities or VO commitments. | C20 | | V10 ambient rail | 41 | Deliver missing RC producer simulations, then rail consumption. Share runtime/identity/control contracts; retain true device and release gates. | C21 | | Yemaya study workspace | 19 | Reuse the substantially built source/quarantine/anchor contracts in Y2. Keep remaining accessibility, gold-set and external acceptance; no second intake system. | C19 | | Oya | 142 | Keep tested Rust cores. Split the G1/G2 admission knot; then runtime, SITL/replay, language seam and durable store before hardware claims. | C22 | | V-series/Isis residue | 190 | Per-product disposition below; source-specific assertions remain until matched to canonical acceptance. | C09, C14, C20, C21 | | Eve small-model excellence | 2 | One shared label exercise with Eve 12.3, not three independently commissioned corpora. Preserve separate statistical/acceptance clauses. | C12 | | Tara content workbench | 2 | Keep registry-source refresh; launch sign-off stays a gate. Do not edit the generated capability matrix by hand. | C14 | | Small trackers | 7 | Four Docs Center audit sections and three Yemaya audit residue items: fold into document/acceptance truth with existing source owners. | C27 | | Audit remediation | 351 | Decompose by current defect and release scope below. Do not count parent roll-ups and their children as independent deliverables. | C14, C16, C19, C21, C23 | The workbench totals also include 126 cross-domain integration cells and 115 rollout/final-definition cells. Keep them as explicit cross-consumer acceptance, not an excuse to defer integration tests until every domain is complete. ### Other phase files: complete logical-group disposition All 36 open files in the generic `phases` family are covered here. Source lines, IDs and current blockers remain in the crosswalk. | Files | Open | Recommended treatment | | --------------------------------- | ---: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 14, 19, 24 | 8 | Affected build/test/lint and platform/provider/deployment residue belong to C16. Retain independent phase-specific checks, not full-repo runs per cell. | | 28 | 17 | Merge Arete API flow evidence with C14; separate native builds and release gates from V1.0 web/PWA proof. | | 71, 78 | 8 | Bind mesh/rig/preview and engine integration to C08's capability crosswalk and C10/C20 producers. Retired benchmark alternatives stay retired. | | 125 | 2 | Keep the revised measurable Monte Carlo benchmark and Rust/TS binding parity; use the actual kernel/host and accuracy contract. Do not revive the superseded impossible target. | | 137 | 62 | Separate functional Linux anti-cheat/crash reporting from NDA SDKs, signing, physical GPU dumps and unsupported OS drivers. Share telemetry/case contracts with the game platform. | | 143, 144 | 74 | Consolidate DCC live-link, import/export and material/render contracts with C08. Keep specialized Neith viewport/CAD behavior only where a real consumer requires it. | | 147, 148 | 81 | Color/media/DJ work retains its signal-processing and interchange criteria. Reuse F-track audio/timeline/asset contracts where applicable; per-device latency and 6/24-hour soaks remain distinct acceptance. | | 149, 150, 151, 152 | 23 | Native identity/vault/endpoint-security residue: source/license/entitlement admission first, then OS-specific implementation and actual platform qualification. Do not infer signing or store readiness from emulator tests. | | 154, 155, 156, 157, 158 | 16 | Specialized modeling/hair/cloth/simulation/editing proof: concrete consumer, correctness fixtures and target-host measurements. No generic “GPU complete” checkbox. | | 160, 161, 163, 166, 167, 168, 169 | 40 | Profiling/VFX/compute/audio and device/soak proof. Bind dogfood to a runnable consumer; distinguish software-device correctness from physical performance. | | 172, 174, 179 | 3 | Preserve remaining integration/dogfood/external acceptance against an actual named product, not the unadopted Obsidian production plan. | | 97, 175, 176, 177, 181 | 66 | Runtime/tool discovery and pretrained inference may be bounded implementation. Frontier training, new corpora and specialist research need separate hypothesis, budget, data and promotion gates. | ### V-series residue and audit-remediation files | Source | Open | Correction | | ------------------------------- | ---: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ISIS_GAPS/ISIS_GAPS_TODOS.md` | 3 | C09 owns real end-to-end, load and gallery-lineage evidence; link to existing Isis job/output paths. | | `V1/TODOS.md` | 17 | C14/C17: current release acceptance and studio entitlement boundaries; native presence work is V1.1. | | V3 | 39 | Package/cook/chunk/stream real assets before store/device launch gates. Reuse current delivery infrastructure. | | V4 | 33 | Keep the real WebRTC SFU residue and platform gates; do not rebuild shared identity/economy. | | V6 | 8 | Keep remaining product/hardware acceptance; share V7/GPS interfaces, retain V6 cognition/simulation ownership. | | V7 | 76 | RR.1–8 establish session transport, probe client, durability, resource artifact, process stack, UE binding, local orchestration and identity. Sequence creator UX and distribution after those foundations. | | V8 | 3 | Keep case/corpus acceptance; consume V5/content-ledger production rather than authoring another parallel corpus pipeline. | | V9 | 11 | Grounded question → lesson → mastery is one first slice. Avatar, game bridges and broad localization follow measured utility and real providers. | | Agentic autonomy June 17 | 9 | Merge surviving tool-use, image/media, audio inference and rig-analysis obligations with their current capability owners. | | Agentic gap closure June 14 | 16 | Merge the 3DGS/import/quality/volume/case residue; preserve deliberate fail-loud or excluded capability outcomes. | | Euterpe remaining work | 10 | Merge engine/runtime/UI residue with domain E and relevant Neith audio tasks; API presence alone is not audible runtime proof. | | Metis gap closure | 3 | Merge deployment and graph-ML residue into the Metis milestone, honoring V1.2 exposure. | | V1 remaining-work checklist | 34 | One activation register for providers, stores, signing and workers; local integration and external production activation remain separate receipts. | | V1 residual backlog | 266 | Preserve the newly grounded child tasks under H/T/P/Q. Prioritize V1.0 honesty, permissions, deletion and persistence; merge P2's overlapping i18n, quotas, observability and acceptance. | | V-series platform consolidation | 13 | GPS.M1's domain contracts need a first consumer and reuse inventory. Distinguish tenant/account/game IDs; `gameId` alone must not imply tenant isolation. Preserve per-game simulation/netcode. | ### Coverage and gates: all eleven families | Family | Open | Disposition | | ------------------------ | ----: | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Studio walkthrough | 5,224 | Attach to owning workbench/product slices; retire only routes proven removed, preserve entitlement/tenant negatives. | | Customer walkthrough | 2,140 | V1.0 critical journeys first; retain deferred-room refusal tests and defer full V1.2 journeys. | | Other web walkthrough | 1,330 | Use journeys, shell, operator/workspace and result evidence as shared acceptance, not separate feature implementations. | | Admin walkthrough | 706 | Attach to operator changes, including deck context, notes and governed operations. | | Tenant-admin walkthrough | 198 | Preserve tenant isolation and role coverage with the relevant product increment. | | Mobile walkthrough | 264 | V1.1 release gate; retain hermetic development/test setup work separately. | | Telegram walkthrough | 42 | First channel uses the existing chosen transport; contract/replay tests can precede live bot credentials. | | V2 signature checklists | 300 | Require a playable build and versioned balance evidence; not 300 new gameplay features. | | Store submission | 697 | Resolve the shipping binary once, then product/store-specific gates. Do not submit both historical standalone apps and a unified app by default. | | Launch gates | 553 | Trigger on a release candidate and named operator; engineering readiness work does not wait for launch day. | | Compliance readiness | 49 | Preserve named evidence and accountable review; do not interpret passing engineering tests as certification. | ## 5. Retirements, consolidations and preserved alternatives “Retire” means remove duplicate execution authority while retaining a source link and disposition. It never means checking an unimplemented task as done. The following changes are recommendations for adoption, not edits made here. | Candidate | Recommendation | Reason / retained intent | | ----------------------------------------------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | SA.2 and SA.3's old implementation fixes | Retire the reimplementation premise; fold residual tests into C15 | Requested behavior already exists and its current tests pass. | | SA.6's “mount eleven routes” premise | Retire that subtask; retain contract/auth/failure verification | Routes exist; acceptance gaps may remain. | | P2 §§59–72, 178 open re-verification boxes | Replace with a route/capability/release acceptance crosswalk, retiring only matched duplicates | Old ID-lineage sweeps overlap the current residual backlog and walkthroughs. Unmatched obligations must be retained. | | Presentation companion's duplicate delivery authority | Consolidate into redesign C07 plus reusable acceptance definitions | One edition and chapter plan, one hosting decision, preserved coverage charter. | | Repeated chapter procedure prose | Replace copied procedure definitions by parameterized chapter delivery checklists | Preserve every chapter's sources, narration, screenshots, PDF and evidence receipt. | | Old `AGENTIC_CONTENT_*` live ledgers | Retire after migrating unique residue | Current Isis/content/Eve owners already govern most of the same system. | | Isis A.03.05, E.01.07, E.04.05, E.06.04, F.03.05 | Move to an option register with explicit activation conditions | “Listed, not pulled,” user-go-only, conditional training and optional Kitsu are not unconditional unfinished commitments. | | Isis L.07.01 | Convert to a dated/usage-triggered operational review | A four-week real-use review should be scheduled when its input exists. | | Legacy AWS/ECS/EKS recipes | Retire as deployment instructions; retain portability intent only when separately adopted | Current delivery uses Hetzner plus declared RunPod lanes. Yesterday already corrected many instances; do not rewrite them again. | | Neith proposals, phase feature snapshots, Antigravity | Preserve as historical/superseded references | Already excluded from the board; copies must not become new work. | | Sophia January convergence plan | Supersede stale paths and unchecked success statements; carry over only current owner/caller gaps | Target libraries exist; existence does not prove every consumer migrated. | | Obsidian production checklist | Keep as an unadopted product/production proposal | Film crews, deals, devices and a new game are not a hidden engineering release requirement. | | General full-repo re-audits after every item | Replace with affected acceptance plus scheduled release/portfolio checks | Preserve coverage; avoid redundant sweeps and resource-unsafe build instructions. | Do not retire human calibration, consent, licensed data, recovery, mobile/device, signing or release obligations merely because an agent cannot complete them in one session. Keep alternatives such as a future paid DCC, model lane or research training run as options with triggers, not permanently ready tasks. ## 6. Proposed canonical execution backlog These are bounded execution groups with explicit acceptance and predecessors. The TSV maps existing leaf tasks into them; it does not replace their unique requirements with a vague epic or authorize bulk closure. Before a group is claimed, its next leaf deliverable must name an existing owner/path, observable result, relevant acceptance set and required environment. Parent and acceptance rows close from evidence, not from an arbitrary percentage of child checkboxes. Waves express priority, not a requirement to finish every group before starting the next wave. A dependency on a named contract or producer means that specific leaf deliverable, not its owner's entire portfolio. In particular, define the C13 artifact contract alongside C05 so C06 need not wait for all retrieval, channels or creative tooling. Capability-specific C12 admission travels with the capability it guards. ### Wave 0 — trustworthy scheduling and a limited verification baseline | ID | Deliverable | Depends on | Acceptance | | --- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | C01 | Explicit cross-family/section dependency support; reconcile the eight unresolved links, prose `later` labels, IDs/aliases, board help and workbench synchronization | Review of this plan | `next` refuses unavailable predecessors; no ambiguous/missing prerequisite is assumed complete; import/pull/merge preserves identity, claims and evidence; docs match real commands. | | C02 | Per-owner acceptance manifest and baseline receipts, including existing failed/missing-setup checks and warning-sensitive CLI tests | C01 metadata contract | Each execution group has bounded commands and evidence requirements; known baseline failures are named, not silently waived. No full-repo build is made a prerequisite for every task. | ### Wave 1 — finish the first-priority presentation experience | ID | Deliverable | Depends on | Acceptance | | --- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | C03 | Finish bounded trusted slide context, source reads, citations and operator-only tools (EI.4–6); retain landed EI.3 regression coverage and record threat gaps | C01; existing EI host contracts | Real-server grounded slide question and citation navigation; malformed/spoofed/stale context and member access refused; keyboard/mobile/axe coverage consistent with viewport admission. | | C04 | Slide notes with scoped Postgres persistence and erasure | C03 identifiers/context; existing persistence | CRUD survives reload/restart; cross-tenant/operator denial; stale-note behavior and erasure; UI works without a model. | | C05 | Isolated proposal/validate/preview/apply/revert/render/publish workflow | C03; worker/deployment design; receipt schema coordinated with C04 | Container-backed end-to-end path, no uncontrolled shared-checkout writes, concurrency and crash recovery, stale-approval refusal, atomic publication, accurate narration/PDF status. | | C06 | Ad hoc presentation artifacts as a consumer of the shared artifact lifecycle | C05; C13 artifact contract | Owner-scoped saved/recent decks, revision history, deletion, narration interruption/resume and approved library promotion; no duplicated storage authority. | | C07 | Reusable chapter delivery process, phased content migration, screenshot/narration/PDF and source-link acceptance | C03 for integration docs; C05/06 only for claims about those features; each chapter's producer | Deliver supported chapters individually. No claims about unbuilt film/3D capability. One edition, per-slide evidence, working reader/deep links, fresh generated output. | C03 is the next product milestone. C01 should be a small enabling repair, not an excuse for another board rewrite. Do not require all presentation chapters to finish before the next product lane can make useful progress. ### Wave 2 — a single creative capability path | ID | Deliverable | Depends on | Acceptance | | --- | ----------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | C08 | Resolve all eleven ADR-0008 questions; I0.20/T.21.07 crosswalk; canonical DCC operations with headless/live adapters and governed Eve consumers | C01; current owner decisions | One implementation owner and one policy/job/asset path per capability; current consumers mapped before retirement; transport conformance and negative authority/session tests. | | C09 | Existing image/video lane closure and hardening; shared proof/cost/model register; resolve unique old Isis gap items | C08 for shared ownership decisions; per-lane admission | One measured receipt per admitted profile, actual output bytes, cancel/retry/retention and gallery lineage; obsolete flavors removed only after caller proof; optional expansion is triggered by measured need. | | C10 | One admitted 3D asset slice, then rig/motion/scene/engine increments | C08; T.01 admission; worker/asset schemas; C09 where image input is needed | Prompt/image → real worker → verified stored asset → actual importer; internal-only output blocked from tenant/catalog delivery; device/profile matrix honest. Expand one capability at a time. | | C11 | Film vertical slice and pilot, then department breadth | C08, required C10 producers, existing film decisions | Script → shots → editable scene → render → cut/audio → deliverable with revisions, provenance and cost. Use the pilot to prioritize F.01–20 breadth; do not build every department before the first film. | ### Wave 3 — governed Eve and current-release correctness | ID | Deliverable | Depends on | Acceptance | | --- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | C12 | Capability-specific evaluation/security/reliability admission, shared SMX labels, ETB.9.01 live proof and charter capstones | Existing Phase-4 controls; human/account/staging inputs where required | Missing/stale families, unvalidated graders, exceeded budgets and unsafe execution fail closed. Fixture, integration, live, human and production evidence are reported separately. | | C13 | Eve composer/replies/control/artifacts, retrieval/memory, channels/watchers and modality delivery through existing ports | C12 before live external/destructive admission; C08–10 for corresponding tools | Release-scoped real-server journeys, cancellation/replay/retention/erasure, ACL-before-retrieval, measured relevance/abstention and costs; no second ungoverned vector or generation plane. | | C14 | V1.0 residual honesty, entitlements, data rights and persistent flows; Tara registry refresh and Arete integration residue | Per-feature contracts; C02 | Current H/T/P/Q child findings reproduced or retired with evidence, then resolved; V1.1/1.2 residue separately scheduled; no fixture success on live paths. | | C15 | Safety automation residual hardening | Fresh service baseline; existing service auth/store conventions | Authorization and secret configuration enforced, typed responses, durable records/schedules, real HTTP lifecycle, dependency failure and restart tests. Retire only the disproven build premises. | | C16 | Shared deployment, security, recovery, cost and observability work; truthful Psyche readiness and Aphrodite metrics | Current Hetzner/RunPod ownership; C02 | Real dependency failure visible, real metrics or explicit absence, tested recovery/rollback, one activation register, current runbooks and cost receipts. No repeated vendor or cloud provisioning plan. | | C17 | Release-scoped accessibility, i18n, performance and critical-journey acceptance | Owning C03–16/C18–26 implementation; actual release scope | Reuse route-level Playwright/mobile coverage; automate important missing flows; merge duplicate sweeps while preserving every unmatched requirement. Manual assistive-tech/device gates remain explicit. | These groups may proceed independently where their own dependencies are met. Do not make a licensed After Effects path block text retrieval, and do not use text-only success to admit the After Effects path. If the safety service or false-ready endpoint is exposed, its remediation precedes expansion of that exposure; this is a concrete service defect, not a reason to stop unrelated read-only work. ### Wave 4 — grounded domain and product increments | ID | Deliverable | Depends on | Acceptance | | --- | --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | C18 | Shared workbench baseline and residual S/I integration; requirements-to-evidence matrix | C08 crosswalk before I6–9; current shared kit | Actual hosts/routes/providers classified; reuse existing job/assets; one working author/review/publish slice; UX/STD/CAP and integration cells trace to real acceptance. | | C19 | Separate Metis, Yemaya, Veritas, Euterpe, Aja, Bellona and Demeter increments | C18 shared primitives only where consumed; C08/C10 for media; release scope | Each domain begins with its own current inventory and one complete workflow. Yemaya reuses study intake; audio uses actual engines; Bellona console consumes adapters; Demeter connects real APIs. No automatic simultaneous build-out of all seven domains. | | C20 | V2 playable slice; V3/4/5/6/8/9 and phase-79 product-specific residuals | Required C09/10 assets, C21 shared identity where consumed | Cook/play/import/runtime proof precedes bulk content and launch certification. Each product keeps its gameplay and platform acceptance; generated descriptors alone do not satisfy runtime behavior. | | C21 | V7 RR foundations and GPS first-consumer contracts, then ambient rail and other game adoption | Current identity/economy owners; real producer simulations | Two real processes exchange scoped sessions/state; durability and resource execution proven; shared identity/social/economy reused; V10 consumes real events; game-specific simulation stays local to the title. | | C22 | Oya admission → runtime → SITL/replay → durable state → hardware qualification | Static model admission before G1; measurements after G1 | Differential parity plus live runtime evidence, fail-loud absent model, restart-safe missions, bounded simulation; physical qualification stays distinct. | | C23 | Content-ledger re-audit and unique old agentic-content residue | Applicable C09/10/20 producers and model/consent gates | LRA probes update pinned profiles and manifests through their procedure; source tasks reference the same receipts; rules and portfolio gates remain distinct from production jobs. | | C24 | Specialist Neith/scientific/research residue | A named consuming product, admitted model/data and target host | Separate functional implementation, research hypothesis and hardware/soak qualification; no unfunded frontier training disguised as a ready engineering checkbox. | | C25 | Remote-host Windows attempts and remaining cross-platform qualification | Existing remote-host capability/security contracts | Bounded hosted-runner proof, no overclaim about interactive hardware or signing; synchronized phase-180 documents and verifier updated together. | | C26 | Controlled human-video delivery | C09 delivery infrastructure; consented corpus and source access for live evidence | Reference/object-store path works; exact approved audio, identity/sync/quality evidence and explicit feature flags; consent/revocation/retention remain enforced. | C19 and C20 are portfolio containers for separate product milestones, not one multi-domain implementation task. Their inherited leaf IDs remain addressable. After the common prerequisites, pick the next domain or product by the current owner priority and readiness; do not assign speculative dates or manufacture a total order between independent products. ### Ongoing evidence and release work | ID | Deliverable | Depends on | Acceptance | | --- | ------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | C27 | Source-document ownership, hidden-plan/debt reconciliation, historical aliases and generated-doc truth | C01 identities; current callers | Every surviving implementation obligation has an owner; superseded plans link to replacements; templates and generated examples do not create spurious tasks. | | C28 | External inputs and release/store/compliance acceptance | Actual release candidate, selected binary and named accountable actor | One owner/input/trigger/expiry/receipt per gate; no paid run, signing, legal sign-off, launch or submission implied by this audit. | ## 7. Important missing or incomplete tasks to add on adoption These are proposed additions or explicit residuals, not newly inserted board rows. 1. **C01 prerequisite conformance:** cross-family references, section/range prerequisites, unresolved IDs, later-label reconciliation and stale blocker detection, with real examples from Isis/EI/P14.b/phase 182. 2. **C01 lifecycle conformance:** import/pull/claim/verify/merge round trips, stable aliases for rewritten tasks, and clear visibility of unfinished work in a closed family. Do not assume isolated command tests cover the workflow. 3. **C02 evidence consumers:** an acceptance manifest mapping changed tracker families to their pinned-text/schema/generator/release checks. Preserve the existing append/procedure policies and make missing setup visible. 4. **C05 deployment qualification:** renderer image/toolchain, isolated checkout, shared artifact visibility, worker identity, atomic publish, bounded storage, cancellation and crash recovery across file and database state. 5. **C06/C13 shared artifact contract:** align decks and other generated artifacts on identity, revisions, ownership, erasure and receipts before implementing separate saved/recent stores. 6. **C08 ADR completeness:** add Q10/Q11 and a consumer-aware retirement list. Consolidate workflow catalog/capability states rather than adding a third registry. 7. **C15 safety-service negative and durable-path coverage:** replace permissive success assertions with contract assertions; require actual persistence and authorization. The current passing suite leaves both gaps. 8. **C16 truthful health and metrics:** the two mounted source gaps above, coordinated with existing observability tasks and actual deployment reachability. 9. **C18/C19 requirements traceability:** map contract/acceptance cells to concrete domain increments, including the V1.0 rooms absent from the large workbench authoring ledger when those rooms actually require authoring work. 10. **C22 staged admission:** break Oya's admission/runtime/measurement knot; apply the same explicit ordering to media/ML worker profiles. 11. **C27 hidden-plan adjudication and language policy:** review the reference catch-all, retain current findings, and reconcile the Rust recommendation with active contributor instructions before initiating a migration. 12. **C28 external-input register:** reuse existing owner-action records for label sheets, regional model routing, Telegram credentials, selected store binary, licenses/corpora, signing and staging access. Record prerequisite, owner and expiry; do not ask again for choices already recorded. ## 8. Adoption, verification and limitations Adoption should be a separate change after review: 1. Accept or amend the architecture boundaries and ordered groups above. 2. Add stable canonical/alias fields and explicit edges before relocating or rewriting source tasks. Preserve all evidence and current blockers. 3. Apply source-specific policies: ordinary trackers through Eve; append-only and procedure trackers through their declared evidence/digest workflows. 4. Reconcile duplicate requirements item by item, retaining unmatched acceptance. Retire with a reason and replacement link, never a false completion checkbox. 5. Regenerate dependent catalogs/manifests, import then regenerate the board, and verify the small next-work queue actually respects the adopted graph. 6. Execute the first scoped product slice; reassess the next batch from its evidence. Fresh verification during this audit: | Check | Result / interpretation | | ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `./eve check --json` | Clean database integrity, foreign keys, family/key/claim checks, graph cycle check, size and registry. Does not establish semantic dependency completeness. | | `./eve drift --json` | No edited, checked or unknown drift; 24,822 open items across 1,149 work-kind files scanned. | | Board scanner/dependency/next/check suites | 76 tests pass with `NODE_NO_WARNINGS=1`. First invocation without it had 75 pass / 1 fail: the CLI stderr line-count assertion included Node's experimental SQLite warning. Preserve this harness fragility as C02; no production code was changed. | | Safety automation suite | Five files, 156 tests pass, no skipped tests; one worker, no file parallelism. Existing tests allow unauthenticated calls; they are not a production admission receipt. | | Audit accounting | Every open key maps once; scanner open counts equal database counts; source hashes retained; checker opens SQLite read-only and proves its hash unchanged. | | Report/bundle checks | Targeted formatting, JavaScript syntax, artifact reproduction, source references and Git whitespace checks; final receipts in the bundle. | No task was claimed, completed, parked, unparked, rejected or promoted. No application implementation, tracker, registry or committed board database was changed. This deliverable consists only of the report and its audit evidence. No paid generation, live production changes, external messages or credential access were needed. The host has approximately 15 GiB RAM with swap and another agent process was active. Verification therefore stayed targeted and sequential. No full Nx, Next production, native packaging, GPU, broad Playwright or mobile matrix was run. This report does not claim those products are green. The prior audit's known unrelated V2/V6, inventory and charter-generation failures were not rerun or relabeled as fixed. They belong in C02's owner-specific baseline. The review decision is whether to adopt this canonical organization and its boundaries. Hardware access, paid spend, human labels and release decisions remain separate prerequisites, not implied approvals to execute them.