# Kling doc set map

Status: active navigation guide
Captured: 2026-03-29

## Purpose
Clarify the role of each Kling-related document in `docs/current/` so future work does not blur together:
- source-of-truth transcription
- field-level reference
- implementation guidance
- work planning
- policy / guardrails
- external blog positioning notes

---

# A. Source-of-truth / reference layer
These documents are closest to structural truth.

## `kling-qingque-full-api-reference.md`
Role:
- broad Qingque-derived source-of-truth layer
- promotes the captured Qingque document into a structured internal reference

Use when:
- deciding whether a field/section exists in SOT
- checking the general shape of the Series 3 API

## `kling-api-reference.md`
Role:
- main integrated API reference
- combines doc-derived structure with live annotations and production notes

Use when:
- checking current best-known contracts
- checking production-relevant API facts

## `kling-api-series-3-spec.md`
Role:
- Series 3 / Qingque-oriented spec note
- good for 3.0-specific structure/context

Use when:
- checking 3.0-series interpretation in a more focused form

---

# B. Field-level detail layer
These documents go deeper than general reference and are meant to prevent payload-shape mistakes.

## `kling-api-field-level-tier1.md`
Role:
- field-level reference for Tier 1 video-critical surfaces

## `kling-api-field-level-tier1-addendum-audio-elements.md`
Role:
- field-level and workflow hints for audio, `video_list`, `element_list`, and adjacent structures

## `kling-api-field-level-tier2-elements.md`
Role:
- field-level reference for General / Element APIs

## `kling-api-field-level-tier3-images.md`
Role:
- field-level reference for image-generation surfaces

## `kling-api-field-status-register.md`
Role:
- compact cross-reference of field confidence state
- fastest place to check whether something is doc-derived, live-confirmed, rejected, or only hypothetical

## `kling-field-extraction-gap-log.md`
Role:
- explicit log of what field-level details are still missing

---

# C. Implementation / execution guidance layer
These documents tell the pipeline what to do with the reference information.

## `kling-pipeline-approved-payload-patterns.md`
Role:
- approved / cautionary / disallowed payload patterns

## `kling-pipeline-action-items-from-blog-and-live-findings.md`
Role:
- high-level execution note translating findings into pipeline actions

## `kling-continuity-test-matrix.md`
Role:
- structured experiment matrix for continuity work

## `kling-docs-to-implementation-workboard.md`
Role:
- operational bridge between docs, code sync, and later live tests

## `kling-priority-todo.md`
Role:
- explicit priority-ordered TODO list
- current top-level sequence: documentation first, code sync second, live tests later

---

# D. Policy / guardrail layer
These documents set non-negotiable operating rules.

## `kling-billable-create-guardrails.md`
Role:
- spend-control rules
- SOT-before-create rule
- no-free-probe rule

## `kling-pipeline-scene-length-policy.md`
Role:
- one scene = one clip
- single-scene ceiling = 15s
- multi-clip chaining reserved for cross-scene continuity

---

# E. Historical / legacy route layer
These should not stay in the current production-facing layer, but may be preserved for provenance.

## `docs/history/20260330_kling-legacy-route-note_reference2video.md`
Role:
- explains why `reference2video` / `multi-image2video` was downgraded out of the current production-facing layer
- preserves provenance without keeping a legacy route in the main current-production guidance

Use when:
- checking why a broader docs-corpus route was removed from current production guidance
- separating current production truth from historical platform surface

---

# F. External-positioning / blog-note layer
These are useful but should not be mistaken for direct contract proof.

## Current blog-note set
- `kling-v3-vs-omni-selection-guide-notes.md`
- `kling-video-3-0-omni-guide-notes.md`
- `kling-video-3-0-overview-guide-notes.md`
- `kling-video-3-0-director-mode-notes.md`
- `kling-educational-videos-guide-notes.md`
- `kling-video-3-0-omni-audio-notes.md`

Use when:
- understanding vendor positioning
- extracting workflow hints
- comparing marketing claims to live behavior

Do not use alone when deciding exact payload shapes.

---

# G. Practical reading order
If you need to implement or verify something, read in this order:
1. `kling-billable-create-guardrails.md` (if a live create may happen)
2. `kling-api-field-status-register.md`
3. relevant Tier field-level doc (`tier1`, `tier2`, or `tier3`)
4. `kling-api-reference.md`
5. `kling-qingque-full-api-reference.md`
6. only then consult historical/legacy notes if a route looks mixed-generation
7. only then consult blog notes for workflow hints

---

# H. Current most important docs for day-to-day work
If only five documents are open at once, prefer:
1. `kling-api-reference.md`
2. `kling-api-field-level-tier1.md`
3. `kling-api-field-status-register.md`
4. `kling-billable-create-guardrails.md`
5. `kling-priority-todo.md`