Creative Pipeline Runtime

Governed staged production for design, deck, dashboard, media, and rule-pack artifacts

Overview

Creative Pipeline Runtime turns creative requests into Taskcenter-native pipeline manifests, runs, stages, approvals, and work products. It uses OpenMontage-style stage discipline, Penpot-inspired artifact metadata, and Ponytail-inspired rule-pack governance without importing those projects directly.

Entry points

Entry routes

/app chat-driven creative requests, /api/artifact-pipelines, and POST /api/artifact-pipelines/runs/:pipelineRunId/cancel (the chat run card's Stop control).

Status

Partial. The API can list built-in manifests, plan a matching pipeline, start a D1-backed run, advance stages, record work products, read runs, and cancel a run (status cancelled, unfinished stages skipped, the run's work product cancelled, audit event creative-pipeline-runtime.run.cancelled).

Failure state

a planned pipeline whose stage has no live provider (today only Media Production's compose stage: no video/audio renderer or provider adapter exists, an owner decision) is recorded as blocked at that stage from the start, never running; the tool tells the person 'Video rendering needs a media provider; none is configured' and that a platform owner can connect one. Creative artifact requests must produce durable work products before the preview sidebar shows a deliverable.

Data source

Data source: artifact_pipeline_manifests, artifact_pipeline_runs, artifact_pipeline_stages, approvals, runtime_events, and work_products. All pipeline writes must go through the guarded Cloudflare D1 adapter with featureBlock creative-pipeline-runtime and organization-scoped bindings. Work-product metadata must include featureBlock, pipelineRunId, stageId, artifactKind, sourceReferences, license, provider, previewRenderer, exportFormats, and validation where applicable.

Permissions

Required permissions: artifact-pipelines:read for discovery and run reads, artifact-pipelines:write for manifest/run creation, artifact-pipelines:execute for stage advancement and artifact recording. Viewers can inspect allowed metadata but cannot start or advance runs. Members, agents, admins, and owners can execute within their normal workspace scope.

Agent routing

North Star should load artifactPipelines tools and Taskcenter-owned skills before claiming support for staged artifact, deck, design, dashboard, prototype, media, or rule-pack work. Required skills include taskcenter-artifact-pipeline-runtime, taskcenter-design-artifacts, taskcenter-media-production, and taskcenter-agent-rule-packs. Pipeline-backed work should start or reuse a run, update real stage rows, and save work products instead of only answering in chat.

Failure states

Empty state

Creative Studio shows no matching manifests or runs from the API, not static cards.

Failure state

missing D1, sandbox, R2/export worker, provider credentials, or credits must return a clear blocker. Sandbox and media execution stay blocked until the thread is in cloudflare_sandbox mode, package and credit checks pass, and high-risk operations receive approval where required.