Eve library
ISIS v2 Weapon Pack Operator/Creator Documentation with Troubleshooting
Guide
Revision 1
On this page
Generated: 2026-03-01T07:54:14.405Z Checklist: MXA-0252 (ISIS2-00450) Asset
Family: weapon-pack Phase: Phase 4 | Milestone: M3 Launch (2026-07-27 to
2026-10-30)
Objective#
Publish creator and operator documentation with troubleshooting for weapon-pack
workflows, spanning workflow authoring, guardrail operations, regression
diagnostics, and downstream integration remediation.
Persona Coverage#
Persona
Workflow Focus
Coverage Signals
creator
Workflow authoring, variant controls, typed submission
controls=57, validationRules=32
operator
Guardrails, regression, integration and runbook diagnostics
envKeys=15, troubleshooting=6
Workflow Coverage#
Workflow
Creator UI Documentation
Operator Policy Documentation
Troubleshooting Coverage
weapon-pack-baseline
yes
yes
yes
weapon-pack-image-conditioned
yes
yes
yes
weapon-pack-control-conditioned
yes
yes
yes
weapon-pack-consistency-locked
yes
yes
yes
Troubleshooting Matrix#
Issue
Signal
Persona
Source Coverage
creator-contract-validation-failure
INVALID_WORKFLOW_RUN_REQUEST
creator
yes
budget-hard-limit-exceeded
WEAPON_PACK_BUDGET_GUARDRAIL_LIMIT_EXCEEDED
operator
yes
quality-gate-failed
WEAPON_PACK_QUALITY_GATE_FAILED
operator
yes
regression-quality-drift
regression-weapon-pack-quality-drift
operator
yes
regression-output-package-contract-miss
regression-weapon-pack-package-contract-miss
operator
yes
downstream-trigger-integration-drift
workflow-trigger-endpoint-mismatch
operator
yes
Creator Quickstart#
Select the weapon-pack workflow variant that matches the shot intent and
control profile.
Complete required scene/design/era/room/camera/material/lighting parameters
plus any conditional reference, control-map, or continuity-lock fields before
submit.
Use side-by-side output comparison to verify spatial continuity, composition
stability, and material-lighting consistency before approval.
Export to downstream engine or DCC targets using recipe metadata for
asset-family traceability.
Operator Diagnostics Surface#
X-Weapon-Pack-Estimated-Cost-Usd
X-Weapon-Pack-Budget-Guardrail-Mode
X-Weapon-Pack-Budget-Guardrail-Reason
X-Weapon-Pack-Quality-Gate-Mode
X-Weapon-Pack-Quality-Gate-Reason
X-Weapon-Pack-Quality-Failing-Metrics
Verification Commands#
pnpm --filter @isis/web exec vitest run src/pages/weapon-pack-ui-utils.spec.ts src/pages/WorkflowDetailsPage.spec.tsx
pnpm --filter @isis/generation-api exec vitest run src/routes/weapon-pack-budget-utils.spec.ts src/routes/weapon-pack-quality-gate-utils.spec.ts src/routes/weapon-pack-regression-golden-dataset.spec.ts
pnpm --filter @isis/client exec vitest run src/examples/external-integrations.spec.ts src/examples/weapon-pack.spec.ts
Acceptance Criteria#
Creator documentation covers all weapon-pack workflow variants, required
controls, validation constraints, and typed SDK run paths.
Operator documentation covers budget and quality guardrail policies, required
environment keys, regression diagnostics, and monitoring headers.
Troubleshooting matrix includes creator-input, budget, quality, regression,
and downstream integration remediation flows with concrete source
traceability.
Published documentation remains reproducible through generator/validator
scripts and evidence-linked governance artifacts.
Traceability#
Checklist item: MXA-0252
Ticket key: ISIS2-00450
Linked checklist dependencies: MXA-0245, MXA-0246, MXA-0247, MXA-0248,
MXA-0249, MXA-0250, MXA-0251