How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

wow-viewer M2 Runtime 04 Scene Submission And Batching - Prompt

Name: wow-viewer M2 Runtime 04 Scene Submission And Batching
Author: akspa0

Prompt file imported from akspa0/parp-tools (.codex/prompts/wow-viewer-m2-runtime/04-scene-submission-and-batching.md). Copyright stays with the author.

Implement or plan the M2 runtime slice that owns classified scene submission and batching policy in wow-viewer.

Current Validated Baseline

section/pass/material routing is already real enough to provide structured runtime input
animated block parsing/evaluation and inspect-time animated runtime output already exist
this slice should assume those inputs are available and focus on render-entry families, queues, sorting, and batching

Read First

gillijimproject_refactor/memory-bank/activeContext.md
gillijimproject_refactor/memory-bank/progress.md
wow-viewer/docs/architecture/m2-native-client-research-2026-03-31.md
gillijimproject_refactor/plans/wow_viewer_m2_runtime_plan_2026-03-31.md
gillijimproject_refactor/src/MdxViewer/Terrain/WorldScene.cs
gillijimproject_refactor/src/MdxViewer/Rendering/ModelRenderer.cs
wow-viewer/src/core/WowViewer.Core.Runtime/World/WorldRenderFrameStats.cs
wow-viewer/README.md
AGENTS.md

Goal

Create an explicit wow-viewer-owned M2 scene/submission model that can express:

render-entry family classification
family-specific submission paths for doodads, particles, ribbons, and special callbacks
state-aware sort/batch grouping
explicit runtime flags/policies such as clip planes, z-fill, doodad batching, particle batching, and additive particle sorting

Non-Negotiable Constraints

Do not turn this slice into the full world-runtime extraction; use the world-runtime prompt set if the real problem is broader WorldScene ownership.
Do not hide every M2 draw behind one generic model renderer abstraction.
Keep batch boundaries and runtime knobs explicit.
Do not claim full render parity from one coordinator/batcher seam.
Keep family-specific behavior concrete instead of introducing a speculative backend abstraction.
Do not spend this slice redoing parser/evaluator work that already belongs to slices 01-03.

What The Work Must Produce

the exact render-entry family/coordinator seam to add
the exact files that should own batching and runtime policy in wow-viewer
the narrowest proof that classified submission is real
the temporary host/compatibility code that can remain in MdxViewer
the follow-on boundary for consumer cutover in slice 05

Deliverables

Return all items:

the exact scene-submission/batching seam to implement
why it is the correct fourth slice
exact files to change
exact validation to run
what should stay out of scope
what still remains consumer-owned afterward

First Output

Start with:

the scene-submission boundary you are assuming now
the single first coordinator/batching seam you would land
the narrowest proof that would make that seam real
what you are explicitly not claiming yet

Install wow-viewer M2 Runtime 04 Scene Submission And Batching and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

Implement or plan the M2 runtime slice that owns classified scene submission and batching policy in wow-viewer. ## Current Validated Baseline - section/pass/material routing is already real enough to provide structured runtime input - animated block parsing/evaluation and inspect-time animated runtime output already exist - this slice should assume those inputs are available and focus on render-entry families, queues, sorting, and batching ## Read First 1. `gillijimproject_refactor/memory-bank/activeContext.md` 2. `gillijimproject_refactor/memory-bank/progress.md` 3. `wow-viewer/docs/architecture/m2-native-client-research-2026-03-31.md` 4. `gillijimproject_refactor/plans/wow_viewer_m2_runtime_plan_2026-03-31.md` 5. `gillijimproject_refactor/src/MdxViewer/Terrain/WorldScene.cs` 6. `gillijimproject_refactor/src/MdxViewer/Rendering/ModelRenderer.cs` 7. `wow-viewer/src/core/WowViewer.Core.Runtime/World/WorldRenderFrameStats.cs` 8. `wow-viewer/README.md` 9. `AGENTS.md` ## Goal Create an explicit wow-viewer-owned M2 scene/submission model that can express: - render-entry family classification - family-specific submission paths for doodads, particles, ribbons, and special callbacks - state-aware sort/batch grouping - explicit runtime flags/policies such as clip planes, z-fill, doodad batching, particle batching, and additive particle sorting ## Non-Negotiable Constraints - Do not turn this slice into the full world-runtime extraction; use the world-runtime prompt set if the real problem is broader `WorldScene` ownership. - Do not hide every M2 draw behind one generic model renderer abstraction. - Keep batch boundaries and runtime knobs explicit. - Do not claim full render parity from one coordinator/batcher seam. - Keep family-specific behavior concrete instead of introducing a speculative backend abstraction. - Do not spend this slice redoing parser/evaluator work that already belongs to slices 01-03. ## What The Work Must Produce 1. the exact render-entry family/coordinator seam to add 2. the exact files that should own batching and runtime policy in wow-viewer 3. the narrowest proof that classified submission is real 4. the temporary host/compatibility code that can remain in `MdxViewer` 5. the follow-on boundary for consumer cutover in slice 05 ## Deliverables Return all items: 1. the exact scene-submission/batching seam to implement 2. why it is the correct fourth slice 3. exact files to change 4. exact validation to run 5. what should stay out of scope 6. what still remains consumer-owned afterward ## First Output Start with: 1. the scene-submission boundary you are assuming now 2. the single first coordinator/batching seam you would land 3. the narrowest proof that would make that seam real 4. what you are explicitly not claiming yet

{ "prompt": "Implement or plan the M2 runtime slice that owns classified scene submission and batching policy in wow-viewer.\n\n## Current Validated Baseline\n\n- section/pass/material routing is already real enough to provide structured runtime input\n- animated block parsing/evaluation and inspect-time animated runtime output already exist\n- this slice should assume those inputs are available and focus on render-entry families, queues, sorting, and batching\n\n## Read First\n\n1. `gillijimproject_refactor/memory-bank/activeContext.md`\n2. `gillijimproject_refactor/memory-bank/progress.md`\n3. `wow-viewer/docs/architecture/m2-native-client-research-2026-03-31.md`\n4. `gillijimproject_refactor/plans/wow_viewer_m2_runtime_plan_2026-03-31.md`\n5. `gillijimproject_refactor/src/MdxViewer/Terrain/WorldScene.cs`\n6. `gillijimproject_refactor/src/MdxViewer/Rendering/ModelRenderer.cs`\n7. `wow-viewer/src/core/WowViewer.Core.Runtime/World/WorldRenderFrameStats.cs`\n8. `wow-viewer/README.md`\n9. `AGENTS.md`\n\n## Goal\n\nCreate an explicit wow-viewer-owned M2 scene/submission model that can express:\n\n- render-entry family classification\n- family-specific submission paths for doodads, particles, ribbons, and special callbacks\n- state-aware sort/batch grouping\n- explicit runtime flags/policies such as clip planes, z-fill, doodad batching, particle batching, and additive particle sorting\n\n## Non-Negotiable Constraints\n\n- Do not turn this slice into the full world-runtime extraction; use the world-runtime prompt set if the real problem is broader `WorldScene` ownership.\n- Do not hide every M2 draw behind one generic model renderer abstraction.\n- Keep batch boundaries and runtime knobs explicit.\n- Do not claim full render parity from one coordinator/batcher seam.\n- Keep family-specific behavior concrete instead of introducing a speculative backend abstraction.\n- Do not spend this slice redoing parser/evaluator work that already belongs to slices 01-03.\n\n## What The Work Must Produce\n\n1. the exact render-entry family/coordinator seam to add\n2. the exact files that should own batching and runtime policy in wow-viewer\n3. the narrowest proof that classified submission is real\n4. the temporary host/compatibility code that can remain in `MdxViewer`\n5. the follow-on boundary for consumer cutover in slice 05\n\n## Deliverables\n\nReturn all items:\n\n1. the exact scene-submission/batching seam to implement\n2. why it is the correct fourth slice\n3. exact files to change\n4. exact validation to run\n5. what should stay out of scope\n6. what still remains consumer-owned afterward\n\n## First Output\n\nStart with:\n\n1. the scene-submission boundary you are assuming now\n2. the single first coordinator/batching seam you would land\n3. the narrowest proof that would make that seam real\n4. what you are explicitly not claiming yet", "variables": [], "notes": "Implement or plan the M2 runtime slice for scene submission and batching. Use when render-entry family classification, state-sort ordering, doodad/particle/ribbon path splits, or M2 runtime knobs such as clip planes or additive sort need a wow-viewer-owned coordinator. Arguments: Optional render family, batching hotspot, native comparator seam, or runtime flag to prioritize.", "metadata": { "source": { "provider": "github-codex-prompts", "repository": "https://github.com/akspa0/parp-tools", "path": ".codex/prompts/wow-viewer-m2-runtime/04-scene-submission-and-batching.md", "ref": "4f7fb94cfad6bf6348c55c28ae9361c2d2fd9cb7", "url": "https://github.com/akspa0/parp-tools/blob/4f7fb94cfad6bf6348c55c28ae9361c2d2fd9cb7/.codex/prompts/wow-viewer-m2-runtime/04-scene-submission-and-batching.md", "key": "akspa0/parp-tools/.codex/prompts/wow-viewer-m2-runtime/04-scene-submission-and-batching.md" } } }

wow-viewer M2 Runtime 04 Scene Submission And Batching

About

Current Validated Baseline

Read First

Goal

Non-Negotiable Constraints

What The Work Must Produce

Deliverables

First Output

Install wow-viewer M2 Runtime 04 Scene Submission And Batching and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews