---
title: "Qingpu Studio Projects and Compliance"
canonical_url: "https://ainode.run/docs/qingpu-studio"
type: "doc"
locale: "en"
description: "Project recovery and evidence-based compliance read APIs for Qingpu Studio."
---

# Qingpu Studio Projects and Compliance
> Project recovery and evidence-based compliance read APIs for Qingpu Studio.

# Qingpu Studio Projects, Image Generation, and Compliance

Studio and Listing are separate products. Studio projects organize professional image and video planning around a shared product identity; they do not copy Listing workspaces, assets, or channel drafts. The P0 execution contract currently supports Ozon product-image suites; single-image editing and professional product-video execution remain separate capabilities.

## Image-suite generation contract

The project page exposes two explicit mutations at `POST /api/qingpu/studio/projects/:id/generation`:

- `{"action":"quote","planId":"...","strategyId":"...","productRevision":12}` returns the selected slot count, blocked slots, server-resolved model summary, and `pricingUnavailable: true`.
- `{"action":"confirm","planId":"...","strategyId":"...","productRevision":12}` freezes the strategy's server-built `ImageGenerationTaskSpec`, creates or reuses the idempotent parent task, and returns its item ledger.

The client may send only `planId`, `strategyId`, and `productRevision` (plus the action). It must not send a prompt, model/provider override, API key, credential, reference URL, frozen task spec, `asyncSubmissionKey`, or `remoteTaskId`. The server reloads the authenticated project, product revision, brief, strategy card, and evidence before constructing each slot specification.

`POST /api/qingpu/studio/projects/:id/generation/retry` accepts a failed item's `taskId` and/or `itemKey`. A failed item gets a new paid attempt only after its prior attempt is an explicit terminal failure. An unknown remote state resumes the original remote task and does not rotate the submission key.

The parent dedupe key is `studio:image-suite:::` and is unique per user and task type. Refreshing or repeating confirmation therefore returns the same parent task instead of creating a second charge. Each slot keeps a stable asset identity `generated-plan:`, its frozen specification, submission key, remote task ID, result URL, and review status.

## Pricing and deployment prerequisites

There is currently no authoritative image price or balance-reservation fact source. Quotes therefore return `pricingUnavailable: true` with `currency`, `estimatedTotal`, `availableBalance`, and `sufficient` all set to `null`; the API never claims that a charge or balance deduction succeeded.

Before a confirmation can enqueue work, the server must pass the AINode asynchronous image-task capability preflight at `/v1/images/generations/tasks`. A deployment that returns `404` or an unsupported-endpoint response is blocked. Studio does not safely fall back to a synchronous image endpoint, because retrying an uncertain request could submit a second paid generation. Operators must deploy the async gateway and verify it before enabling confirmation.

Execution is resumable: `queued` and `running` states survive a process restart; an item with an unknown remote state remains attached to its original remote task; explicit terminal failures can be retried individually. Outcomes are `succeeded`, `partial`, or `failed`; successful items are retained when another slot fails. Text QA uses the engine verdicts `ok`, `warn`, and `failed`, and does not invent a separate review `block` verdict.

## Project history

`GET /api/qingpu/studio/projects` accepts `search`, `status`, `page`, and `limit`. It returns project summaries plus `total`, `page`, and `limit`. Summaries include product-fact revision state, asset and running-task counts, evidence risks, review counts, and a conservative compliance status.

The user route `/user/studio/projects` preserves search, status, and page in the URL so a filtered view can be refreshed or shared within the same authenticated account. `/user/studio/projects/:id` restores product evidence and strategy state.

## Compliance read model

`GET /api/qingpu/studio/compliance` accepts `search`, `status`, `page`, and `limit`. Add `projectId` to retrieve one project with its compliance issues.

The endpoint is read-only. It derives results only from:

- `CreativeBrief.missingFacts`, reported as product-evidence risks;
- `qingpu_task_items.review_status`, reported as recorded asset-review states;
- current product revision, assets, and task ownership already linked by `user_id + product_id`.

Supported summary states are `evidence_block`, `review_failed`, `warning`, `pending`, `partial`, `passed`, and `unreviewed`. `passed` means recorded review items are `ok`; it never means that every marketplace rule has been checked. Missing review records remain `unreviewed`. The current system does not produce a persisted asset-review `block`, so the API does not fabricate one.

This endpoint does not create review tasks, consume credits, modify Listing, or publish assets. Studio generation writes only Studio-owned assets, tasks, task items, and project status; it does not write Listing workspace or channel-draft tables.
