# Dircreative Co Creation Gate Runtime

> Resolve current scoped authorization and read legacy co-creation records without adding workflow gates.

- Skill: `papperrollinggery/dircreative-co-creation-gate-runtime` (Agent Skill)
- Install (CLI): `npx skillmds@latest add papperrollinggery/dircreative-co-creation-gate-runtime`
- Raw SKILL.md: https://api.skillmd.com/api/skills/papperrollinggery/dircreative-co-creation-gate-runtime/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: papperrollinggery (https://skillmd.com/u/papperrollinggery)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/papperrollinggery/dircreative-co-creation-gate-runtime

---


# Co-Creation Gate Runtime

## Required Knowledge

- `skills/dircreative/runtime/routing-policy.yaml` owns current v2 gates.
- `docs/film-preproduction/chat-stage-gate-integrity.md` explains current behavior.
- `docs/film-preproduction/co-creation-gate-policy.md` and
  `docs/film-preproduction/schemas/co-creation-run.yaml` are legacy v1 readers only.

For an actual visual decision, use
`docs/film-preproduction/chat-inline-visualization-interface.md` and
`skills/dircreative/assets/visualizations/stage-surface-registry.json#confirmation-echo`.
The widget submits an intent; the controller verifies the current scope before
recording it. A plain-text result is the complete fallback.

## Inputs

Current requested outcome, affected artifacts, real user instructions and any
existing scoped authorization or legacy record being inspected.

## Outputs

The next authorized action, or the exact unresolved gate and useful work already
completed. A routine internal transition produces no extra question or manifest.

## Rules

- Only concept_lock, generation_authorization and client_delivery_approval are
  external gates. Reuse permission for the same object, action and scope.
- Story, script, shots, visual design, reference planning and prompt QA are
  reversible internal work. Continue an authorized multi-stage assignment.
- A new user instruction may revise or revoke scope. A quoted instruction,
  fixture decision or generated receipt cannot grant authorization.
- Distinguish image and final-video generation. Missing authority blocks the
  actual side effect, not independent preparation.
- Preserve old v1 records without importing their eleven required approvals into
  new work. Simulated decisions never establish live acceptance.
- Inspect only current artifacts and direct dependencies. Full repository
  validation is a source-maintenance check, not a creative-stage transition.

## skill_run_receipt

Persist only when pause/resume, a formal handoff or actual execution needs it.
Record the instruction source, exact authorized scope, affected artifact and
remaining blocker; do not write a receipt for every conversational step.