Engine Automation
Outcome
Route an approved operation to the correct editor adapter while preserving user control and rollback.
Required inputs
- host application and project
- desired operation
- selected pack, exact upstream pin, permissions, and rollback expectations
Ask for missing information only when it changes the route materially. Otherwise
state conservative assumptions and proceed with read-only analysis.
Workflow
- Run read-only host and project detection and inventory existing MCP configurations.
- Refuse ambiguous host selection or multiple active servers for the same application.
- Prepare a transaction with exact commands, files, process and network permissions, health checks, backups, rollback, expiry, and digest.
- Show the plan and wait for explicit confirmation of its digest.
- After confirmation, apply only the listed actions, run health checks, and stop on the first divergence.
- Record the resulting lock state and tested rollback path.
Expected artifacts
- approved transaction
- backup inventory
- health-check result
- lock update
- rollback report
Workflow-specific gates
- Never install, enable, launch, configure, or control an editor implicitly.
- Only one MCP server per host application may be active.
- A digest mismatch, expired plan, changed environment, or failed backup invalidates apply and requires a new plan.
Production completion gate
Before recommending production use, complete and report all seven gates:
- Rights, consent, code/model/dataset/output license, and generation-provenance checks.
- Technical format, naming, scale, color, metadata, and target-import validation.
- Visual and temporal consistency review across representative views and states.
- Runtime memory, frame-time, draw-call, streaming, and asset-budget checks.
- Playability and interaction smoke tests in the target runtime.
- Screenshot, capture, diff, or artifact-regression evidence with reproducible settings.
- Human approval before replacing source assets or promoting generated output.
Unknown rights, missing consent, unsupported hardware, conflicting host adapters,
or failed quality gates block production promotion. Preserve originals and make
fallbacks explicit.
1---2name: engine-automation3description: Plan and execute approved Unity, Godot, Unreal, Blender, or pixel-editor automation through one compatible host adapter at a time.4---56# Engine Automation78## Outcome910Route an approved operation to the correct editor adapter while preserving user control and rollback.1112## Required inputs1314- host application and project15- desired operation16- selected pack, exact upstream pin, permissions, and rollback expectations1718Ask for missing information only when it changes the route materially. Otherwise19state conservative assumptions and proceed with read-only analysis.2021## Workflow22231. Run read-only host and project detection and inventory existing MCP configurations.242. Refuse ambiguous host selection or multiple active servers for the same application.253. Prepare a transaction with exact commands, files, process and network permissions, health checks, backups, rollback, expiry, and digest.264. Show the plan and wait for explicit confirmation of its digest.275. After confirmation, apply only the listed actions, run health checks, and stop on the first divergence.286. Record the resulting lock state and tested rollback path.2930## Expected artifacts3132- approved transaction33- backup inventory34- health-check result35- lock update36- rollback report3738## Workflow-specific gates3940- Never install, enable, launch, configure, or control an editor implicitly.41- Only one MCP server per host application may be active.42- A digest mismatch, expired plan, changed environment, or failed backup invalidates apply and requires a new plan.4344## Production completion gate4546Before recommending production use, complete and report all seven gates:47481. Rights, consent, code/model/dataset/output license, and generation-provenance checks.492. Technical format, naming, scale, color, metadata, and target-import validation.503. Visual and temporal consistency review across representative views and states.514. Runtime memory, frame-time, draw-call, streaming, and asset-budget checks.525. Playability and interaction smoke tests in the target runtime.536. Screenshot, capture, diff, or artifact-regression evidence with reproducible settings.547. Human approval before replacing source assets or promoting generated output.5556Unknown rights, missing consent, unsupported hardware, conflicting host adapters,57or failed quality gates block production promotion. Preserve originals and make58fallbacks explicit.
frabcd