Eve library

ADR-0008: Open 3D Studio Capability Ownership, Registries and Provider Boundary

ADR

Revision 17

On this page

Status: Proposed (2026-09-14); section 8 answered 2026-09-21 (T.00.06). All eleven questions were delegated by the owner on 2026-09-18 ("where decisions are needed from me you can make the decision based on what you think is best"). The agent took Q5 that day under the delegation (the tracker's 2026-09-18 decisions record) and answered Q1–Q4 and Q6–Q11 on 2026-09-21 under task isis-chroma-runpod:T.00.06 and its journal. On 2026-10-03 the owner chose to bring Q7 into line with ADR-0006 §6. The owners of gaps G2 and G6 were decided by the owner on 2026-10-01; G1 stays pending T.21.07
Date: 2026-09-14
Owner: @GreyChimp (assigns implementation work per phase)
Authors: Isis Runtime Engineering (tracker item T.00.01)
Related ADRs: ADR-0001 (job envelope), ADR-0002 (workflow schema), ADR-0003/ADR-0004 and ADR-0005 slim worker (RunPod execution), ADR-0006 §6 (where a type lives)

Sources in Eve (2026-10-01): the T.00.02 trace, cited below as docs/agents/isis-3d-studio-evidence.md, is Eve document 25fb428c-23ff-8eaf-88a8-290a0d6a1b37 ("Isis 3D studio — evidence and decision records"). The tracker is the isis-chroma-runpod board family. The answers to section 8 and the owner's delegation are recorded on task isis-chroma-runpod:T.00.06. TODOS/phase-71.md was retired from the repository, and its items are board tasks phases:71.*. None of these documents is approved yet, so this ADR names them without pinning them. Attached for review: an export of the evidence document at revision 5, with its content hash, and a board snapshot taken 2026-10-03T20:23Z (sha256 7eda9c33…f132) of T.00.06 (the section 8 answers, the 2026-09-18 delegation and, as its 2026-10-03T19:17:37Z journal note, the owner's 2026-10-03 Q7 decision and the Q5 attribution correction), T.08.07 at version 2 (the rewritten Q7 task, with the edit's before and after in its journal), T.04.08 at version 1 (the scene document's move to @oshun/contracts), T.17.07 and T.21.07 (journal notes recording the owner's 2026-10-01 gap-owner decisions) and T.10.09. It supersedes the 2026-10-01 snapshot.

1. Context and Problem Statement#

The tracker ISIS_CHROMA_RUNPOD_MVP_TODOS_2026-09-11.md, section "Open 3D studio architecture and review (added 2026-09-13)", adds a 3D creation and scene workspace inside Isis. It must use Isis's existing dashboard, API, jobs, output registry, model governance and RunPod infrastructure. Its ownership map names about twenty libraries across eight rows, several per capability, and states that "this is an ownership map, not a claim that these packages are production-ready".

The T.00.02 trace (docs/agents/isis-3d-studio-evidence.md, section T.00.02) followed 38 paths through 30 libraries:

  • 5 runnable: the T.00.03 package builder, which nothing live feeds, and four local calculations.
  • 2 partially wired, 6 simulated and 25 dead.
  • 20 defects (D1–D20).
  • No path takes a prompt or image to a stored, verified mesh.
  • No apps/isis/* app imports any 3D library. Eleven libraries are reached only from Oshun or Yemaya apps (evidence §3, closing list).

Each library has a reuse, repair, replace or retire decision.

Without one owner per capability, the plan invites the pattern the trace found repeatedly: parallel wrappers for the same thing. Examples are two 3D provider clients (3d-generation, 3d-inference-local), a second LRU cache manager (D17), a Redis job channel outside the job API (scene-from-image-composer), an orchestration graph with no engine (3d-post-pipeline/orchestration) and a GPU queue nobody produces for (P15–P17).

T.00.01 asks for:

  • one canonical implementation owner per capability;
  • a crosswalk to earlier 3D TODOs, phase work and the Eve tool/provider contracts;
  • a list of obsolete wrappers;
  • proof that every T.17 matrix capability maps to a package, a task and a release gate, with no second public job or asset registry.

2. Decision: one owner per capability#

Rules for reading the table:

  • Canonical owner. Exactly one package is accountable for the capability's implementation and its evidence. Other packages named in the notes are contributors. A contributor may not grow a parallel implementation of the same capability.
  • Release gate. The T.17.06 acceptance-matrix row (tracker T.17, matrix under T.17.06) must pass for the named release scope, followed by T.18.01 staged flags. Milestones M0–M4 are from the tracker's delivery table.
  • Current state. Verdicts are quoted from T.00.02 §1 (P-numbers) and §2 (D-numbers). "Absent" means T.00.02 traced no path for it.
  • §3 decision. This is the T.00.02 per-library decision. Where this ADR differs from it, the note says why.

2.1 Capability table (the twelve T.17.06 matrix rows)#

# Capability (T.17.06 row) Canonical owner T items (matrix → owned sub-items) Release gate Current state (T.00.02) Notes
C1 Image/text/multi-image -> 3D libs/isis/3d-inference-local T.05, T.07 → T.05.01–T.05.06, T.07.01, T.07.02 (admission T.01.01, worker T.02.01) T.17.06 row "Image/text/multi-image -> 3D"; M1 exit (image -> textured GLB -> dashboard preview/download -> re-import, measured cost); T.18.01 per model/profile dead: P1–P4, P19, P21–P23. partial: P20 (TRELLIS.2 shape worker, no caller, TRELLIS_REF=main unpinned). Multi-image: absent (P4 stable-zero123 is excluded and non-commercial) §3 repair, followed. The TRELLIS.2 shape and texturing runners and the TripoSG runner become the inside of the dedicated 3D worker kind. API dispatch stays in apps/isis/generation-api as a new worker kind. Contributors, not owners, get the D1–D4 and D6 fixes: apps/isis/generation-api and libs/isis/ai-providers (runpod-adapter.ts). Concept images (T.05.02) come from existing libs/isis/workflows Chroma/arsenal workflows. @isis/3d-generation's TRELLIS client is not the adapter (§4 W1).
C2 Procedural/CAD and hybrid assemblies libs/isis/3d-scene-assembly T.06 → T.06.01–T.06.06 T.17.06 row "Procedural/CAD and hybrid assemblies"; M2; the T.20 headless runner gates applicable Blender work in M1/M2 (tracker, text after the milestone table) absent. No Blender builder, CadQuery or OpenSCAD path exists: rg -il 'cadquery|openscad' over libs apps docker infra scripts finds only an unrelated libs/nyx CAD client (2026-09-14). No app imports the library (§3) Differs from §3 by extension. §3 decided reuse of the scene-graph and collision contracts for T.04/T.14 and did not assess T.06. The library already holds procedural-assembly-recipes.ts, connector-taxonomy.ts, scene-unit-normalization.ts and symmetry-placement.ts, which match T.06.01/T.06.05. T.00.02 did not read those modules, so they are read before reuse. Executable Blender/CadQuery/OpenSCAD builders run in the DCC/CAD worker image (T.02.01), not in this library. The ownership map has no row for this lane (Q1).
C3 Real-photo and multi-object reconstruction libs/isis/video-to-mesh T.07 → T.07.03–T.07.06 T.17.06 row "Real-photo and multi-object reconstruction"; M2; custom-license (SAM 3D, T.01.03) and open profiles qualify separately dead: P14, P16 (splat job and worker, no producer). The video-to-mesh runners have no importer (§3). simulated: D13 point-cloud fallback in gaussian-splatting §3 reuse once T.01 clears the SAM2 and Depth Anything V2 weights (COLMAP SfM/MVS, depth, SAM2, Poisson runners), followed. libs/isis/gaussian-splatting (§3 repair) contributes splat outputs only (gap G4). T.00.02 does not place the SAM 3D runner (T.07.03) (Q3).
C4 PBR/text/image retexturing libs/isis/3d-post-pipeline T.10 → T.10.01–T.10.06 T.17.06 row "PBR/text/image retexturing"; M2 dead: P32 (lib-only), P21 (TRELLIS.2 texturing runner, lib-only). mislabelled: D12 (classical algorithms labelled neural or AI) §3 replace, followed: under Q6 (2026-09-21) libs/isis/3d-post-pipeline owns the capability, where T.10.01 and T.10.03–T.10.06 already live (src/materials/). libs/isis/ai-texturing keeps only the Hunyuan3D-Paint modules and the D12 labels and retires under T.10.09, which also moves the catalog owner in libs/isis/workflows/src/three-d-capabilities/registry.ts (still libs/isis/ai-texturing on 2026-10-01). Texture generation runs in the worker from the 3d-inference-local TRELLIS.2 texturing runner and admitted Paint3D/TEXGen/Step1X stages. 3d-post-pipeline owns channel normalisation, baking and material QA (T.10.01, T.10.04, T.10.05). The Hunyuan3D-Paint modules retire (§4 W4). Seam and UDIM helpers may be kept once renamed. Q6 settled the name: the capability leaves ai-texturing.
C5 Smart-topology-class usability libs/isis/3d-post-pipeline T.09, T.11 → T.09.01–T.09.06 (T.11.04 deformation evidence comes from C6) T.17.06 row "Smart-topology-class usability"; baseline T.09 checks gate M1 runnable local compute, not connected to assets: P28. dead: P13, P15, P31. simulated statistics: D9 (3d-generation mesh-processor) §3 reuse of topology analysis and manifold repair, followed. Meshes are parsed with the T.00.03 reader (apps/isis/generation-api/src/services/glb-probe.ts). Contributors: the apps/isis/gpu-worker trimesh/open3d pipeline once D11 is fixed (queue ownership is Q4), and libs/isis/3d-quality-gates (§3 reuse) for gate-profile shapes in T.09.06, with measured inputs only.
C6 Auto-rigging and skin weights libs/isis/universal-rigging T.11 → T.11.01–T.11.05 T.17.06 row "Auto-rigging and skin weights"; M3 dead: P24 (UniRig runner, lib-only). simulated: P25 demo sessions, D16 predicted "after" metrics §3 replace, followed. The SkinTokens/TokenRig runner goes in the rig/motion worker image (T.02.01). The UniRig stage runner stays in 3d-inference-local pending admission. The skeleton and skin data contracts are reused. The per-class heuristics and the "ML skeleton prediction" statistical prior are not the base.
C7 Text animation/presets/retargeting libs/isis/universal-rigging T.12, T.13 → T.12.01–T.12.06, T.13.01–T.13.06 T.17.06 row "Text animation/presets/retargeting"; M3. Per T.12.06, the matrix must tell preset motion apart from generated text-to-motion simulated: P26 catalog (D15). absent: text-to-motion, retargeting and motion QA The ownership map assigns the motion library, retargeting and deformation QA here. §3 reuses the Mixamo-compatible bone-name mapping for T.13.01 after review and retires the synthesized catalog (§4 W5), both followed. Blender retargeting executes in the DCC worker. libs/isis/motion-camera-control (P27) produces camera paths only and contributes to C9, not here.
C8 Agent/closed-loop/selective edits apps/isis/generation-api T.08, T.14 → T.08.01–T.08.06, T.14.02, T.14.03, T.14.06 T.17.06 row "Agent/closed-loop/selective edits"; M4; T.21 comparison and failure tests gate agent-enabled profiles before T.18 rollout (tracker, text after the milestone table) absent: no director or critic path exists. P29 builds a prompt string (local compute). The selective-edit libraries are dead: 3d-semantic-editing, part-level-3d and text-mesh-editing have no importer (§3) The director and critics run on the existing CPU control plane (tracker worker-profile row "API/director/scheduler"). Their tools are generation-api operations with artifact IDs and revision preconditions (T.08.02), and their spend comes from T.03.03 reservations. Provider calls cross the @oshun/ai boundary (§6). 3d-semantic-editing (§3 replace) contributes T.14.02 part identity. The ownership map lists llm-providers/ai-providers for "controller integration", which §6 reconciles; neither owns the director. The code home is Q7.
C9 Scene/workspace/timeline/API apps/isis/generation-api T.03, T.04, T.14, T.15 → T.03.01–T.03.06, T.04.01–T.04.05, T.14.01, T.14.04, T.15.01–T.15.06 T.17.06 row "Scene/workspace/timeline/API"; M1 (dashboard preview and download), M2 (scene portions) runnable unit: P5. partial: P6. dead: P1, P7, P8, P9, P13, P18. simulated: P10, P11, P12. local compute on demo data: P27, P30 The other T items depend on the server-side state: contracts, stage DAGs, revisions, locks and roles. apps/isis/web and libs/isis/3d-browser (§3 repair: keep the viewer and statistics, retire in-browser generation) implement T.15 and display only persisted API results (T.15.05 verify). Asset records live in apps/isis/output-registry (§3 of this ADR). Other contributors: 3d-scene-assembly scene graph (T.04.03, T.14.01), motion-camera-control camera paths (T.14.04, §3 reuse), scene-from-image-composer alignment and placement math (§3 repair), 3d-asset-library revisions (T.04.02, §3 repair). T.14.05 rendering is gap G2 and T.04.06 is gap G5.
C10 Mesh/CAD/print exports libs/isis/3d-post-pipeline T.16.01, T.16.02 T.17.06 row "Mesh/CAD/print exports"; M2 (print delivery) dead (lib-only): P33 GLB/glTF, P34 FBX, P35 USD/USDZ, P37 STL/3MF/OBJ/.blend. simulated: P10 export center (operator-typed URLs, D20) §3, followed: reuse the GLB/glTF exporter; repair the FBX, USD, 3MF and STL writers, which are listed only after round-trip import evidence. CAD STEP sources come from C2 (T.06.03) and do not exist today. export/blend-export.ts is reused only after the runtime audit. Its fixtures mention Blender 4.2 (tracker "Execution contract and integration boundaries").
C11 Three.js/Godot/Unity/Unreal libs/isis/3d-post-pipeline T.16.03–T.16.06 T.17.06 row "Three.js/Godot/Unity/Unreal"; Unity certification also needs T.19 but does not block a Blender/Three.js/Godot-only release (tracker) dead (lib-only): P36. Engine import is unverified §3 repair, followed: the engine writers are candidates pending runtime evidence. Engine runners (Unity CLI in T.19, UE commandlets in T.16.05) are execution environments. They do not own package writing and do not create a second export implementation.
C12 Self-hosting, reliability and economics apps/isis/generation-api T.01–T.03, T.17, T.18 → T.01.03, T.02.03, T.02.06, T.03.03, T.03.04, T.17.04, T.17.05, T.18.01–T.18.04 T.17.06 row "Self-hosting, reliability and economics" (hosted APIs disabled for open-profile proof, recovery tests, measured cost per accepted asset); T.18 needs passing T.17 gates partial. The RunPod dispatch record, cost ledger and budget guardrails exist (evidence §4 item 1, executor.ts:4684-4729, :4937-4978), but no 3D job reaches dispatch. Wrong admission row (D14); second cache evictor (D17); excluded model baked and oversized three-d endpoint (D7) Enforcement lives in the API: admission at submission, retry and fallback (T.01.03); the cache lease authority (apps/isis/generation-api/src/services/runpod-model-cache/, L.03); budgets and the global governor (T.03.03, T.03.04); receipts. Contributors: libs/isis/model-governance-3d (§3 repair; registry data for T.01.01–T.01.05), libs/isis/3d-generation-benchmarks (§3 repair; T.17.01/T.17.02 harness; hosted runners are optional references), libs/isis/3d-quality-gates (§3 reuse), and infra/runpod, docker/runpod and scripts/isis (T.02 builds and provisioning). The ownership map puts "admission … release gates" with governance and benchmarks. This ADR keeps their data and harness roles there and puts enforcement in the API, which already enforces spend and cache admission for image and video.

Counts: 12 matrix rows, 12 owners. Six distinct owner packages (after Q6):

  • apps/isis/generation-api ×3
  • libs/isis/3d-post-pipeline ×4
  • libs/isis/universal-rigging ×2
  • 3d-inference-local, 3d-scene-assembly and video-to-mesh ×1 each

All paths exist (checked with ls on 2026-09-14).

2.2 Gaps: capabilities the plan adds that T.17.06's matrix does not gate#

These come from the scope decisions, the architecture diagram, the Unity/Blender review and T items whose deliverable no matrix row's "required evidence" covers. None has a gate. Each is repeated under open question Q2.

# Capability Where the plan adds it Proposed owner T items Release gate Current state (T.00.02)
G1 Agent-tool transports: Unity CLI/Pipeline, Unity MCP, Blender headless, Blender Lab MCP "Unity and Blender agent tool review (2026-09-13)"; T.21.06 says it will extend the matrix Pending (owner, 2026-10-01): no single owner yet. T.21.07's audit of libs/bellona/blender-agent, unity-agent and cross-dcc-consistency decides it. Under Q5 every Blender operation itself lives in libs/isis/3d-post-pipeline. The tracker's route table names official tools and two community bridges T.19.01–T.19.08, T.20.01–T.20.08, T.21.01–T.21.06 no gate defined in the current matrix absent (tracker: "No software is installed"). P37 .blend export and P17 Blender render worker are dead
G2 Deterministic scene stills, turntables, MP4 and Isis audio/video handoff Architecture diagram line "browser scene/timeline + still/video rendering through Isis"; T.14.05 libs/isis/3d-post-pipeline (owner, 2026-10-01): under Q5 it is the only home of Blender operations, render operations included. Contributors: generation-api dispatches them as 3D worker kinds (Q4); the 3d-asset-library turntable renderer and the apps/isis/gpu-worker render executor (P17) move onto it T.14.05, T.20.05 no gate defined. The scene row names playback, not rendered output dead: P17 (no producer); turntable renderer lib-only
G3 Facial blendshapes, eyes, fingers, clothing/hair binding T.11.06 ("explicit additional capabilities") libs/isis/universal-rigging T.11.06, T.13.04 (cloth) no gate defined. The rigging row covers body rigs absent
G4 Gaussian-splat outputs as a distinct output kind Candidate table, SAM 3D row ("Keep mesh and Gaussian-splat outputs distinct"); T.07.03 verify libs/isis/gaussian-splatting (§3: "Splats stay a T.07 output kind handled by gaussian-splatting") T.07.03, T.07.04 no gate defined. The reconstruction row names object, layout and scale only dead: P14, P16. simulated: D13
G5 Asset library search, tags, variants and reusable collections with per-asset rights T.04.06; T.01.05 (rights survive library reuse) libs/isis/3d-asset-library (§3 repair). It indexes output-registry records and is never a store of record (§3 of this ADR) T.04.06, T.01.05 no gate defined. The scene row names roles, not library reuse or rights propagation simulated: P38 (D10 hash embeddings labelled CLIP)
G6 Import and script sandboxing Scope decision 7 ("Scripts run in isolated workers …"); T.03.06, T.21.03 apps/isis/generation-api (owner, 2026-10-01): it validates imports before dispatch and selects the isolated worker profile. Contributor: the docker/runpod 3D worker images, which provide the process isolation T.03.06, T.20.03, T.21.03 no gate defined. The self-hosting row names recovery and cost, not isolation not traced by T.00.02

3. Registry rule: no second public job, asset or workflow registry#

The only public registries for 3D work are the existing ones:

Concern Registry of record 3D extension (T item)
Jobs and stages apps/isis/generation-api job store. services/job.service.ts writes jobs and job_outbox rows (:767, :851). Routes are POST /api/v1/jobs (routes/jobs.ts:8271, evidence P1) and POST /api/v1/jobs/chain (routes/jobs.ts:8478). Chains are a linked list in job metadata (services/job-chain.service.ts:1-16), "rather than a new store" T.03.02 builds persisted stage DAGs on these jobs and chains: dependency hashes, provider IDs, leases, cancellation, resume. A 3D stage is a job with a 3D worker kind. T.03.05 events and webhooks extend routes/webhook-subscriptions.ts
Assets and revisions apps/isis/output-registry: POST /api/v1/outputs (routes/outputs.ts:191), hash verification and lineage policy (services/output.service.ts:215, :222). Bytes are stored by generation-api's output store (services/output-store.service.ts, services/output-persistence.service.ts). That is storage, not a second registry T.04.01/T.04.02 add the manifest and revisions to output-registry records. Two fixes are prerequisites: the missing job → registry producer (P9: generation-api never calls the registry) and D4/D5. T.04.05 extends the existing upload/download routes
Workflows and catalog libs/isis/workflows catalog (src/workflows/**), served by generation-api GET /api/v1/workflows/catalog (routes/workflows.ts:5069); apps/isis/workflow-registry (app.ts:204-210: /workflows, /templates, /staging-recipes) 3D catalog entries and T.00.04 capability states extend these. How the two existing surfaces relate is not decided here (Q10)
Model weights and cache Hetzner library manifest plus the L.03 cache planner and admission (apps/isis/generation-api/src/services/runpod-model-cache/admission.ts, planner.ts); rights in libs/isis/model-governance-3d and the A.04 register T.02.02/T.02.03 add 3D families to the same 400 GB cache under one eviction authority

Binding rules:

  1. No new public API, job queue, job channel, asset store or cache evictor for 3D. The tracker's ownership map says "add worker kinds rather than a second public API". The Unity/Blender review says to integrate "through T.02/T.08 rather than creating another asset or job registry".

  2. 3D stage DAGs reuse jobs and chains (T.03.02). A DAG node is a job, and a parent job completes only when its persisted children do.

  3. Libraries hold no records of their own. The asset library's index (3d-asset-library), the scene graph (3d-scene-assembly) and benchmark results (3d-generation-benchmarks) are computed over, or written to, the registries above. They never keep a separate persistent catalogue that a client can read as the truth.

  4. DCC and engine bridges are execution routes, not registries. Blender and Unity sessions and MCP servers (T.19/T.20) receive artifact IDs and revision preconditions and return persisted revisions through the job API.

  5. Forbidden as public entry points:

    • the scene-from-image-composer Redis job channel (src/dispatch/redis-job-channel.ts);
    • the apps/isis/gpu-worker BullMQ gpu-jobs queue (P15);
    • the 3d-inference-local REST provider server;
    • the 3d-post-pipeline/orchestration graph descriptors;
    • 3d-inference-local registry eviction (D17).

    §4 lists how each one is removed or folded in.

No row in §2.1 or §2.2 proposes a new registry.

4. Obsolete wrappers: retire or fold in#

Evidence citations are from docs/agents/isis-3d-studio-evidence.md (§1 paths, §2 defects, §3 libraries). "Retire" means removed from the Isis 3D path. Where an Oshun or Yemaya app still imports the module, that consumer is named, and the decision on it is Q9.

# Library / module Disposition Evidence Removing T item
W1 @isis/3d-generation: hosted clients (Meshy, Tripo, Rodin, 3DFY, Hunyuan), the TRELLIS client and processing/mesh-processor.ts Retire the clients from the open profile; replace the processor P19: trellis-provider.ts:99-153 sends mode: 'text' to a server that returns 422 (docker/runpod/trellis3d/server.py:345-349). D9: mesh-processor.ts:262-282, :427-440, :530-539, :892-908, :1180. Consumer: apps/oshun/bff/src/generation/sky-briefing-provider-env.ts:20-24 T.05.01 (worker contract), T.09.02, T.01.04
W2 @isis/3d-inference-local: registry eviction, REST provider server and GPU node-pool managers Delete eviction; retire server and managers D17: registry/model-registry.ts:146-191, :303-334, :336-420; config/defaults.ts:46-54. §3: "retired in favour of the existing API and RunPod scheduling" T.02.03 (one eviction authority), T.02.05
W3 @isis/3d-inference-local: Hunyuan3D, SF3D, SPAR3D, Sparc3D and Pixal3D modules Retire unless admitted §3; D7 (infra/runpod/endpoints/image-build-config.json:289-299, inventory/three-d.json:29-31); sparc3d-loader.ts:767 T.01.01, T.01.03
W4 @isis/ai-texturing: Hunyuan3D-Paint modules and the modules D12 mislabels Retire the package (Q6, T.10.09); consumers move to 3d-post-pipeline D12: ai-based-texture-baking.ts:47, :141, :154-230, :477; pbr_texture_super_resolution_core.py:1-7, :85-213 T.10.01, T.10.02
W5 @isis/universal-rigging: synthesized animation catalog, predicted after-metrics and demo sessions Retire catalog and demos; relabel or compute metrics D15: humanoid-animation-library.ts:105, :251-300, :351-380. D16: guided-skin-weight-refinement.ts:684, :1106-1150. P25 consumer: apps/oshun/web/src/components/studio/StudioIsisAutoRiggingWorkspace.tsx:2 T.12.03, T.11.05
W6 @isis/3d-browser: in-browser SF3D and TripoSR generation loaders Retire (keep the viewer) D19: src/inference/sf3d-wasm.ts:351, :360; triposr-wasm.ts:262, :271 (int8, unadmitted) T.01.01, T.15.02
W7 @isis/3d-post-pipeline: orchestration/index.ts graph descriptors and presets Retire §3: descriptors "without an execution engine" (:1498-2568) T.03.02
W8 @isis/3d-product-parity Retire from the 3D matrix; the prompt builder may move P29: apps/oshun/bff/src/isis/three-d-prompt-store.ts:43-70 builds a string only. Route names overstate it T.08.01
W9 @isis/three-d-pipelines Retire from the Isis 3D path §3: topology.ts:33-50 checks caller-asserted counts; provider enums list tripo-comfy and meshy-comfy (provider.ts:11-25). Consumer: Oshun BFF sky-briefing T.09.01
W10 @isis/3d-comfyui-nodes Retire §3: TS node specs calling 3d-inference-local over HTTP (nodes/trellis-2-node.ts:1661-1697) that the worker cannot load T.02.01 (dedicated 3D worker kind)
W11 @isis/mesh-transformers and the dashboard page MeshTransformerAbComparisonPage.tsx Retire library; remove page P11 and D8: apps/isis/web/src/pages/MeshTransformerAbComparisonPage.tsx:51-122 hardcoded metrics; §3: no model runtime T.15.01 (routes), none for the library
W12 Dashboard page InteractiveGenerationPage.tsx and export-center manual bundles Remove page; list only produced files P12 and D8: InteractiveGenerationPage.tsx:89-110. P10 and D20: output-export-center-utils.ts:378-423 T.15.02, T.16.01
W13 @isis/quad-mesh-gen Retire; keep computeIsisQuadMeshTopologyStats only if needed §3: quadgpt-generation.ts:163-318, no candidate model T.09.03
W14 @isis/3d-video-diffusion Retire §3: SV3D and Zero123 are non-commercial; gates check configuration strings (sv3d-video-to-3d.ts:312-335) T.07.02
W15 @isis/gigascale-3d Retire §3: benchmark is profile arithmetic (trellis2.ts:260-296) T.01.01, T.17.02
W16 @isis/part-level-3d, @isis/text-mesh-editing Retire §3: plan records over injected ports with no runtime. Plan item 5 promises no masked 3D regeneration T.14.02
W17 @isis/3d-control Retire §3: conditioning belongs to the concept-image stage or T.05 adapter parameters T.05.02
W18 @isis/3dgs-advanced, @isis/3dgs-diffusion-editing, @isis/3dgs-relighting-pbr Retire §3: research-method plans, no trainer or runtime T.07.03 (splats via gaussian-splatting)
W19 @isis/scene-from-image-composer dispatch handlers and Redis job channel Register through the job API or remove (library otherwise repaired) P18: no app registers the handlers (src/index.ts:1-12); dispatch/redis-job-channel.ts:14-48 T.03.02
W20 @isis/3d-semantic-editing heuristic part labelling Replace §3: semantic-part-segmentation.ts:1-17, :246; heuristic labels with no correspondence measure T.14.02
W21 @isis/gaussian-splatting synthetic point-cloud fallback Delete the fallback (library repaired) D13: src/nerf/nerf-manager.ts:1134-1185 T.07.03
W22 Excluded and non-commercial 3D workflows and infra: artifact-reconstruction default, hunyuan3d-asset.json, stable-zero123.json, three-d endpoint Remove system default; retire or re-type workflows; mark class planned; do not create endpoint D6: executor.ts:2202, job.service.ts:111, graph ends in SaveImage. D7: desired-state.json:68-80, jobs.ts:6739-6745. P3/P4 T.05.01, T.01.03, T.02.05
W23 Test double that certifies any 3D job Return only what the requested graph can emit; rename specs D6: workflows/test-comfyui-service.ts:44-54; executor.spec.ts:2055-2131, :3649-3680 T.00.04 (fixture-only work cannot reach live-ready)

Kept, not obsolete, and outside the T plan: @isis/3d-marketplace-ops (§3, "reuse unchanged outside 3D generation").

Repaired rather than retired, and so not listed above: output-registry ThreeDPackageSchema (D5, T.04.01), the worker adapter base64 and S3 branches (D2/D3, T.05.01), the output store MIME tables (D4, T.04.05), CLI and API parameter validation (D18, T.03.01), 3d-asset-library and benchmark embedding defaults (D10, T.04.06/T.17.02), and the model-governance-3d TRELLIS.2 row (D14, T.01.01).

5. Crosswalk: earlier Isis 3D TODOs and phase work → T items#

Status key:

  • superseded: the T item replaces the earlier item. Per the tracker, "No milestone inherits completion from an older checkbox or a passing mock."
  • merged: code worth keeping from the earlier item is folded into the T item under the §3 reuse/repair decision.
  • independent: outside the T scope. It stays separate and confers nothing.

Every earlier item below is checked [x] in its source file. T.00.02 found none of them on a live path that produces a verified mesh.

# Earlier item Source T item(s) Status Note
X1 71.1.1, 71.1.2, 71.1.5 model serving, TRELLIS.2, TripoSG TODOS/phase-71.md §71.1 T.01.01, T.02.01, T.05.01, T.05.03 merged Runners reused (§3 3d-inference-local repair); serving layer retired (W2)
X2 71.1.3 Hunyuan3D 2.1 TODOS/phase-71.md §71.1.3 T.01.03 superseded Excluded (A.04.04; scope decision 3)
X3 71.1.4 SF3D/SPAR3D, 71.1.6 Sparc3D TODOS/phase-71.md §71.1.4, §71.1.6 T.01.01 superseded Retire unless admitted (W3)
X4 71.1.7 MeshAnything V2, 71.1.8 FlexiCubes TODOS/phase-71.md §71.1.7, §71.1.8 none independent Not in the candidate table and not assessed by T.00.02 (Q5)
X5 71.1.9 intelligent model routing TODOS/phase-71.md §71.1.9 T.05.06 superseded Policy-, resource- and quality-aware fallback that never silently drops constraints
X6 71.2 AI-native PBR texturing TODOS/phase-71.md §71.2 T.10.01–T.10.06 superseded §3 replace; W4
X7 71.3 universal auto-rigging TODOS/phase-71.md §71.3 T.11, T.12, T.13 superseded §3 replace; skeleton/skin contracts and the bone-name map merged into T.11.03/T.13.01; W5
X8 71.4.1 monocular video to 3D, 71.4.2 multi-view reconstruction TODOS/phase-71.md §71.4 T.07.04, T.07.06 merged §3 video-to-mesh reuse after weight admission
X9 71.4.3 4DGS to animated mesh, 71.4.4 SLAM scanning TODOS/phase-71.md §71.4 none independent No T item
X10 71.5.1 WebGPU viewer, 71.5.3 browser editing TODOS/phase-71.md §71.5 T.15.02, T.15.03 merged §3 3d-browser repair
X11 71.5.2 WebGPU 3DGS viewer TODOS/phase-71.md §71.5.2 none (see G4) independent T.15.02 viewer modes do not name splats
X12 71.5.4 browser inference (WASM) TODOS/phase-71.md §71.5.4 T.01.01 superseded D19; W6
X13 71.6.1–71.6.3 asset library core, variation, style TODOS/phase-71.md §71.6 T.04.02, T.04.06 merged §3 repair (D10); indexes registry records only (§3 rule 3)
X14 71.6.4 asset provenance and licensing TODOS/phase-71.md §71.6.4 T.01.05, T.04.02 merged Rights re-derived in T.01
X15 71.6.5 community and sharing TODOS/phase-71.md §71.6.5 T.04.06 (roles only) independent Project roles use existing sharing primitives; community features have no T item
X16 71.7 quality benchmarking suite TODOS/phase-71.md §71.7 T.17.01, T.17.02 merged §3 repair; hosted runners are optional references
X17 71.8.1 pipeline orchestration TODOS/phase-71.md §71.8.1 T.03.02 superseded W7
X18 71.8.2 mesh optimization steps TODOS/phase-71.md §71.8.2 T.09.02–T.09.05 merged Measured against parsed meshes
X19 71.8.3 format export TODOS/phase-71.md §71.8.3 T.16.01–T.16.03 merged Round-trip evidence before a format is listed
X20 71.9 ComfyUI 3D nodes TODOS/phase-71.md §71.9 T.02.01 superseded W10
X21 71.10 GPU infrastructure for self-hosted 3D TODOS/phase-71.md §71.10 T.02.03–T.02.05 superseded RunPod endpoints plus the L.03 cache; W2
X22 71.11 part-aware semantic editing TODOS/phase-71.md §71.11 T.14.02 superseded W20
X23 71.12 @bellona/blender-agent Blender MCP server TODOS/phase-71.md §71.12 T.20 independent Not audited by T.00.02. T.20 names Blender Lab MCP and ahujasid/blender-mcp only (Q5)
X24 71.13 quality gates and active learning TODOS/phase-71.md §71.13 T.09.06, T.17.06 merged §3 reuse of taxonomy and gate profiles, with measured inputs only
X25 71.14 model governance and compliance TODOS/phase-71.md §71.14 T.01.01–T.01.05 merged §3 repair (D14)
X26 71.15 marketplace trust and operations TODOS/phase-71.md §71.15 none independent §3: outside the T plan
X27 71.16 product parity and workflow UX TODOS/phase-71.md §71.16 T.08.01 superseded W8
X28 71.17 scene graph and kitbash assembly TODOS/phase-71.md §71.17 T.04.03, T.06.01, T.06.05, T.14.01 merged C2 owner; §3 reuse
X29 71.18 DCC ecosystem parity (Maya, 3ds Max, Unity/Unreal/Godot bridges) TODOS/phase-71.md §71.18 T.16.03–T.16.05, T.19 superseded (engines); independent (Maya, 3ds Max) No T item covers Maya or 3ds Max
X30 71.19 @bellona/unity-agent Unity MCP server (219 tasks) TODOS/phase-71.md §71.19 T.19 independent Not audited by T.00.02. T.19 selects the official CLI, Pipeline and unity mcp, and evaluates CoplayDev only (Q5)
X31 71.20 3DGS diffusion editing, 71.21 3DGS relighting, 71.32 advanced GS TODOS/phase-71.md §71.20, §71.21, §71.32 T.07.03 superseded W18
X32 71.22 autoregressive mesh generation TODOS/phase-71.md §71.22 none superseded Scope candidate table; W11
X33 71.23 score distillation, 71.24 flow matching/consistency, 71.28 hash encoding TODOS/phase-71.md §71.23, §71.24, §71.28 none independent libs/isis/{score-distillation,fast-generation,hash-encoding} exist but were not among the 30 libraries T.00.02 audited (Q5)
X34 71.25 ControlNet and IP-Adapter for 3D TODOS/phase-71.md §71.25 T.05.02 superseded W17
X35 71.26 text-guided mesh editing, 71.30 part-level 3D TODOS/phase-71.md §71.26, §71.30 T.14.02 superseded W16
X36 71.27 3D from video diffusion TODOS/phase-71.md §71.27 T.07.02 superseded W14
X37 71.29 native quad mesh generation TODOS/phase-71.md §71.29 T.09.03 superseded W13
X38 71.31 gigascale and next-gen models TODOS/phase-71.md §71.31 T.01.01, T.17.02 superseded W15
X39 5.5.1–5.5.6 3d-generation library, text-to-3D and image-to-3D pipelines TODOS/phase-5.md §5.5 T.05 superseded P1 and P19 dead; W1
X40 5.6 gaussian-splatting library TODOS/phase-5.md §5.6 T.07.03, T.07.04 merged §3 repair (D13)
X41 5.10.7 and 5.10.9 GPU worker executors and images (mesh-processing, blender-render, gaussian-splatting) TODOS/phase-5.md §5.10 T.02.01, T.03.02 merged Executors reusable after D11, but no producer exists (P15–P17). Queue ownership is Q4
X42 18.2.4.1 audit-remediation note on 3D preview, GPU mesh retrieval and texture outputs TODOS/phase-18.md (note under 18.2.4.1) T.00.02, T.00.05 superseded Evidence: T.00.02 found the GPU worker paths have no producer
X43 WF-001 3d-texture certification ISIS_TODOS.md Workstream 20 T.10.02 superseded Catalog registry entry only (libs/isis/workflows/src/utils/registry.ts:1174); T.00.02 found no texture path (P32)
X44 WF-003 artifact-reconstruction certification ISIS_TODOS.md Workstream 20 T.05.01, T.00.04 superseded D6: the graph ends in SaveImage; the certification rests on the test double (W23)
X45 WF-041 stable-zero123 certification ISIS_TODOS.md Workstream 20 T.01.02, T.07.02 superseded P4: non-commercial, not on the volume
X46 WS06-001 3D output package contract ISIS_TODOS_2.md WS06 T.04.01 superseded D5; T.00.03 rebuilt the generation-api package
X47 WS06-002 mesh quality validators ISIS_TODOS_2.md WS06 T.09.01 superseded Implementation location not traced; no validator is on a live path (P28 is local compute)
X48 WS06-003 PBR texture set validators ISIS_TODOS_2.md WS06 T.10.01, T.10.05 superseded
X49 WS06-004 UV and texel density checks ISIS_TODOS_2.md WS06 T.09.04 superseded
X50 WS06-005 LOD generation and validation ISIS_TODOS_2.md WS06 T.09.05 superseded
X51 WS06-006 rig-readiness checks ISIS_TODOS_2.md WS06 T.11.01, T.11.04 superseded
X52 WS06-007 Unreal/Unity/Godot export bundles ISIS_TODOS_2.md WS06 T.16.03–T.16.05 superseded T.00.03 removed the fabricated engine bundles
X53 WS06-008 Blender/Maya DCC bundles ISIS_TODOS_2.md WS06 T.16.01 superseded
X54 WS06-009 3D provenance records ISIS_TODOS_2.md WS06 T.04.02 superseded T.00.03 removed eight provenance steps that never ran
X55 WS06-010 geometry, texture and engine-ingest benchmark suites ISIS_TODOS_2.md WS06 T.17.01, T.17.02 superseded
X56 MXC-0012, 0028, 0044, 0060, 0076, 0092, 0108, 0124, 0140, 0156, 0172, 0188, 0204, 0220 (control support for 3d-reconstruction) ISIS_TODOS_2.md T.05.02, T.07.06 superseded §3 3d-control decision: conditioning belongs to the concept-image stage or adapter parameters; no 3D workflow returns a mesh (P2–P4)
X57 "3D Generation Pipeline" (six hosted/open providers) docs/domains/isis/features.md (section "3D Generation Pipeline") T.18.05 superseded Hosted services are references, not runtime dependencies (scope decision 2)
X58 ISIS_V2_3D_OUTPUT_PACKAGE_CONTRACT, ISIS_V2_3D_PIPELINE_BENCHMARK_SUITE, ISIS_V2_3D_PROVENANCE_INTEGRATION, ISIS_V2_FBX_* certifications docs/domains/isis/remediation-v2/ T.00.05, T.16.01 superseded T.00.05: no historical count or status badge is implementation proof

6. Eve and provider boundary#

The shared boundary is @oshun/ai (libs/shared/ai, path mapping tsconfig.base.json:1548). It provides:

  • LLMProviderInterface (src/types.ts:424);
  • ToolDefinition (:94) and ImageContent (:43) for rendered critic views;
  • ModelInfo.supportsVision and supportsTools (:455-457);
  • the providers: OpenRouter (src/providers/openai.ts:771), native OpenAI, native Anthropic and Ollama (src/providers/ollama.ts:322);
  • the agent loop: AgentLoop (src/agent-loop/loop.ts:160), ToolRegistry with ajv input validation (tool-registry.ts:46), AgentBudget (budget.ts:14) and runStructuredOutput (structured-output.ts:97).

Eve's agent binds a provider through it in apps/oshun/bff/src/assistant/agent-provider-config.ts:

  • OSHUN_ASSISTANT_PROVIDER resolution at :238;
  • fail-closed agent_not_configured per the header at :1-20;
  • Eve's tools use the same ToolDefinition (agent-tools.ts:12).

Two Isis LLM layers exist beside it:

  • @isis/ai-providers src/providers/llm/openai.ts and anthropic.ts delegate traffic to @oshun/ai (:1-18 in each). They re-declare their own LLMProviderInterface (src/types/llm.types.ts:266) for historical callers.
  • @isis/llm-providers has its own fetch-based client adapters with hardcoded base URLs (src/client/llm-client.ts:141-142). Its only non-spec from importers are in libs/metis/*, not any Isis app. libs/contracts/src/llm mentions it only in comments.

Decision:

  1. Director and critic calls cross @oshun/ai's LLMProviderInterface directly, from the generation-api control plane (C8).
    • They do not use @isis/llm-providers client adapters (a second transport).
    • They do not add director code to the @isis/ai-providers compatibility layer (a second interface).
    • Neither package is retired by this ADR, because Metis and historical Isis callers still use them.
    • This settles the ownership map's instruction to "reconcile with the shared Eve provider boundary in T.00".
  2. Typed 3D tools (T.08.02) are ToolDefinitions in a ToolRegistry.
    • Handlers call generation-api operations with artifact IDs, revision preconditions and idempotency keys (tracker "Execution contract and integration boundaries").
    • They never take URLs, shell strings or BFF services.
    • If Eve or another agent later exposes 3D actions, it calls the same API operations through @isis/client. There is no second 3D tool implementation.
    • T.19/T.20 transports sit behind these same operations.
  3. Structured plans and role outputs (T.08.01) use runStructuredOutput with the T.08.01 schemas. Schema-invalid output is rejected, not repaired into acceptance.
  4. Spend. AgentBudget is a run-scoped cap only. Project spend is the T.03.03 reservation in generation-api. Controller calls reserve before they run, like GPU stages. Critics cannot override deterministic validators (scope decision 7).
  5. What must not be duplicated. Provider selection and credential resolution, the agent loop, tool-input validation, structured-output handling, provider cost accounting, and the Eve assistant's tool surface. Director code does not import apps/oshun/bff.

What the fully self-hosted profile needs (scope decision 2; T.08.03):

  • Local models. An admitted local text/tool model and an admitted local vision model, each reachable through an LLMProviderInterface implementation: the existing OllamaProvider, or the OpenAI-compatible path with a configured base URL (providers/openai.ts:133). Both report measured supportsTools and supportsVision.
  • Admission. The controller runtime, weights and licences are admitted under T.01.04 like any other dependency.
  • No hosted fallback. Hosted providers are disabled by configuration. Unavailable controller capabilities stay visible, and nothing falls back to a paid API. Otherwise the profile discloses reduced autonomy, and deterministic manual operation remains available.
  • Capacity. The controller runs on its own capacity (worker-profile row "API/director/scheduler"), so GPU mesh workers never idle waiting for an LLM.
  • Optional hosted models. GPT-6 Astra, if enabled, runs only on the Codex subscription, signed in with ChatGPT: through codex exec (CodexExecProvider, libs/shared/ai/src/providers/codex-exec.ts) or the Codex subscription provider (providers/codex-subscription.ts). It never goes through the OpenAI API, OpenRouter, an API key in the child environment or purchased credits (Elikem's decision of 2026-09-18, recorded in CLAUDE.md and Isis ADR-0011). When the allowance runs out, the job stops and reports the reset time; it does not fall back to a billed route. Modalities are discovered rather than hardcoded. No Astra model id exists in libs/shared/ai/src today (rg -i astra, 2026-10-01). A profile that depends on it is never called fully self-hosted.
  • Test binding. Routine tests and harnesses keep the CLAUDE.md binding (OpenRouter deepseek/deepseek-v4-flash-0731, OPENROUTER_PROVIDER_SORT=price). Only the open-profile release proof runs with hosted providers disabled.

7. Consequences#

  • The T.17.06 matrix can be filled row by row against one accountable package each. Contributors cannot claim a row's evidence.
  • Concentration in apps/isis/generation-api. It owns C8, C9 and C12, because spend, cache admission, revisions and dispatch already live there, and a second deployable would split them. The cost is concentration: the director and scene contracts become shared contracts in @oshun/contracts once another deployable needs them (Q7, ADR-0006 §6).
  • 23 wrapper retirements or fold-ins (W1–W23). Five of them (W1, W5, W6, W8, W9) touch libraries that Oshun apps import. Retiring them from the Isis path does not by itself remove those Oshun surfaces (Q9).
  • Output-registry becomes the 3D asset record. That forces the job → registry producer that does not exist today (P9), and the D4/D5 fixes before T.04.
  • A checked phase-71 item is not T progress. 58 crosswalk rows record that: 13 merged, 36 superseded, 8 independent and 1 split (X29).
  • Release gates stay nominal until T.00.04 states exist. Until then, no capability can be release-qualified, whatever the T.17.06 row says.

8. Open questions for the owner (@GreyChimp)#

  1. Q1: procedural/CAD ownership. The tracker's ownership map has no row for the procedural/CAD lane. This ADR assigns libs/isis/3d-scene-assembly. Confirm or name another package. Also decide where the versioned Blender Python operation modules shared by headless and live routes (T.20.02) live.

    Answer (2026-09-21, delegated): Confirmed: libs/isis/3d-scene-assembly owns the procedural/CAD lane, where all six T.06 items shipped (assembly plans and builds, CAD and OpenSCAD parts, details, evaluation). The versioned Blender Python operation modules live in libs/isis/3d-post-pipeline/src/blender/ops/, which T.20.02 shipped and T.20.04's live session imports. The Q5 decision (taken under the owner's delegation) makes that the only place a Blender operation is implemented, so the twelve bpy scripts still in apps/isis/gpu-worker/src/assets/scripts/ move onto it under T.20.09.

  2. Q2: ungated capabilities. Gaps G1–G6 have no T.17.06 row and no gate. For each, add a matrix row with required evidence, or declare it outside the named release scope. G1 is already promised by T.21.06.

    Answer (2026-09-21, delegated): G1 gets its row under T.21.06. G2, G3, G5 and G6 get matrix rows with required evidence: each already has shipped, measurable work a row can gate (T.14.05, T.11.06, T.04.06, T.03.06), and G6 is also a security precondition. G4 is declared outside the named release scope, because it has no admitted runtime and its splat worker was deleted under T.01.10, so a row would be a gate nothing can pass. T.17.07 adds the rows, widens the T.17.06:C1–C12 gate pattern and records G4's exclusion.

  3. Q3: SAM 3D runner placement (T.07.03). Options are beside the 3d-inference-local runners or inside video-to-mesh. The custom licence must stay isolated from the open-core release either way.

    Answer (2026-09-21, delegated): Inside video-to-mesh. Section 2.1 makes video-to-mesh the single owner of C3 (T.07.03–T.07.06), and the open alternative (T.07.04, COLMAP/OpenMVS) already sits there. The custom licence is isolated by admission (the gated sam-3d family, T.01.03) and the separate reconstruction worker profile, not by package placement. Implemented by T.07.03, parked upstream until the vendor grants access.

  4. Q4: apps/isis/gpu-worker queue.

    • The BullMQ gpu-jobs queue has no producer (P15–P17).
    • Its default name matches the one apps/infra/gpu-dispatcher/src/config.ts:30 consumes for RunPod dispatch.
    • Options: fold the mesh, splat and render executors into 3D worker kinds dispatched from generation-api jobs (T.03.02), or retire the queue.
    • Separately, the T.00.02 evidence refers to a "§3 gpu-worker" subsection that does not exist (last bullet of defect D11).

    Answer (2026-09-21, delegated): Fold the executors into 3D worker kinds dispatched from generation-api jobs. The shipped Blender work (T.06, T.09, T.10, T.13, T.14) runs on those executors, and T.03.02's stage graph already names their job types, so retiring the queue would strand them. What is missing is the dispatch link and a queue name that does not collide with the RunPod dispatcher's gpu-jobs. Both are T.03.07. The missing "§3 gpu-worker" subsection cited by D11 is superseded by this answer.

  5. Q5: libraries T.00.02 did not audit.

    • libs/isis/score-distillation, libs/isis/fast-generation and libs/isis/hash-encoding (phase 71.23/71.24/71.28).
    • libs/bellona/blender-agent, libs/bellona/unity-agent and libs/bellona/cross-dcc-consistency (71.12/71.19/71.18).
    • Also 71.1.7 MeshAnything V2 and 71.1.8 FlexiCubes.
    • T.19 and T.20 do not mention the bellona agents, although apps/bellona/remote-host imports @bellona/blender-agent.
    • Options: audit each before deciding; evaluate the bellona agents as T.19.08/T.20.07-style alternatives; or record them as independent.

    Answer (2026-09-18, delegated): one Blender operation library. Taken by the agent under the owner's 2026-09-18 delegation and recorded with its reason in the tracker's decisions list that day ("Decisions taken under the owner's delegation on 2026-09-18"; retired tracker, git show d092109ae62^:ISIS_CHROMA_RUNPOD_MVP_TODOS_2026-09-11.md, lines 344–376); one line to reverse. T.20's versioned Python operation modules and headless runner are the only place a Blender operation is implemented. Bellona keeps what Eve's governance needs and calls those modules; libs/bellona/blender-agent, unity-agent and cross-dcc-consistency are audited under T.21.07, which supplies the per-operation table (merged, superseded or independent).

  6. Q6: ai-texturing name. Keep the package name for T.10 after its replacement (the "AI" label sits next to D12), or move T.10 into 3d-post-pipeline.

    Answer (2026-09-21, delegated): Move T.10 into 3d-post-pipeline: every shipped T.10 item already lives in libs/isis/3d-post-pipeline/src/materials/ (T.10.01, T.10.03–T.10.06). libs/isis/ai-texturing has been unchanged since 2026-07-18 and holds only the excluded Hunyuan3D-Paint modules and the D12 labels. T.10.09 retires it and moves its consumers.

  7. Q7: director and scene code home. Director/critic role schemas and scene contracts start in generation-api. Where do they move when a second deployable needs the types (ADR-0006 §6 home test)?

    Answer (corrected 2026-10-03, the owner): to @oshun/contracts. ADR-0006 §6 (git show d092109ae62^:docs/domains/isis/adr/ADR-0006-canonical-human-video-contracts.md, lines 102–126) puts a type that two or more deployables must agree on in @oshun/contracts; an @isis/* library holds only provider- or algorithm-shaped types that no other deployable needs. The 2026-09-21 delegated answer said "an @isis/* library", which contradicted that rule; the owner chose to conform rather than record a 3D exception.

    • Director and critic schemas: one consumer today, so they stay in generation-api. When F.01.08 or F.02 first imports them from another deployable, their wire shapes move to a libs/contracts module in that change (T.08.07, rewritten 2026-10-03). Helpers only generation-api needs stay there.
    • Scene document: a known nonconformity. T.04.03 put scene-document.ts in @isis/3d-scene-assembly, and output-registry, gpu-worker and the Isis web app import it, so its schemas are already a shared wire shape outside @oshun/contracts. T.04.08 moves the schemas, constants and types to @oshun/contracts (schema id and version unchanged, so stored scenes still parse) and leaves the scene algorithms in @isis/3d-scene-assembly.
  8. Q8: controller precision. The initiative forbids quantized generation weights. Does that bind local LLM/VLM controllers? Ollama commonly serves quantized builds, and libs/shared/ai/src/local/quantization.ts exists. T.08.03 admission needs the answer.

    Answer (2026-09-21, delegated): No. The full-precision rule governs generation weights ("All generation weights remain full precision"), which 3D model admission enforces, and a controller's output is a plan or critique that cannot override a measurement (T.08.04). A quantized local controller is admissible when its exact build is recorded (name, revision, quantization, licence) and benchmarked as that build, and it never supplies generation weights. T.08.03 applies this in controller admission.

  9. Q9: Oshun and Yemaya consumers of retired modules.

    • Oshun BFF sky-briefing and "3d-generation" admin routes (W1, W8, W9).
    • Oshun web studio rigging and editing demos (W5, W6).
    • Options: keep as labelled Oshun-owned demos, rename, or remove.

    Answer (2026-09-21, delegated): Remove them. Each surface shows a 3D capability that T.00.04 marks unavailable, and the BFF sky-briefing still calls a Trellis client that always fails (P19). Keeping labelled demos would pin retired libraries into the build and leave a 3D surface outside the capability states. T.00.07 removes them and points Oshun at generation-api's /workflows/catalog/3d-capabilities. No Yemaya runtime importer was found.

  10. Q10: two workflow surfaces. Generation-api's /workflows/catalog and apps/isis/workflow-registry both exist. Which one do 3D catalog entries and T.00.04 states register in? This ADR forbids a third surface but does not merge the two.

Answer (2026-09-21, delegated): Generation-api's /workflows/catalog. T.00.04 registered the 3D capability states there (GET /api/v1/workflows/catalog/3d-capabilities, backed by libs/isis/workflows/src/three-d-capabilities/), with the submit guard beside them. Registering in apps/isis/workflow-registry would copy the catalog and start drift. Implemented by T.00.04; workflow-registry's 3d-generation category is not a third path.

  1. Q11: gates before T.00.04. Should any T.17.06 row be marked release-qualified before T.00.04's capability states ship? This ADR assumes no.

Answer (2026-09-21, delegated): No, as this ADR assumes, and T.00.04 now enforces it. release-qualified is reachable only by climbing the capability ladder with release-gate evidence naming the capability's own T.17.06 row, and a catalog proof level can never grant it. Today three capabilities are candidates and nine are unavailable. Tracked by T.17.06, enforced by T.00.04.

9. T.00.01 verification record (2026-09-14)#

  • Matrix coverage. Every T.17.06 matrix row appears exactly once in §2.1 (C1–C12) with one owner, its T items and its gate row. The six capabilities the matrix omits are in §2.2 with "no gate defined" and are repeated in Q2.
  • Owner paths exist. Checked with ls on 2026-09-14:
    • apps/isis/generation-api
    • libs/isis/3d-inference-local, 3d-scene-assembly, video-to-mesh, ai-texturing, 3d-post-pipeline, universal-rigging
    • gap owners libs/isis/gaussian-splatting, 3d-asset-library
  • No new registry. No row proposes a new public job, asset, workflow or cache registry. §3 names the existing ones and forbids five alternative entry points.
  • Agreement with T.00.02. Owner assignments match the §3 decisions. The one extension (C2) and the one reconciliation of the ownership map (C8/C12 and §6) are stated with reasons.

References#

  • Tracker: ISIS_CHROMA_RUNPOD_MVP_TODOS_2026-09-11.md. Sections: "Open 3D studio architecture and review (added 2026-09-13)" (scope decisions 1–7, candidate table, ownership map, worker profiles, milestones); T.00–T.21; T.17.06 matrix; "Unity and Blender agent tool review (2026-09-13)".
  • Evidence: docs/agents/isis-3d-studio-evidence.md (T.00.02 §1–§5; T.00.03 in the tracker note).
  • Earlier work: TODOS/phase-71.md, TODOS/phase-5.md, TODOS/phase-18.md, ISIS_TODOS.md, ISIS_TODOS_2.md, docs/domains/isis/features.md, docs/domains/isis/remediation-v2/.
  • Provider boundary: libs/shared/ai/src/, apps/oshun/bff/src/assistant/agent-provider-config.ts, libs/isis/ai-providers/src/providers/llm/, libs/isis/llm-providers/src/.