Repository navigation
docs: define first-class design, script, image, and video surfaces - #34
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5c6cfbe6b5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| - `LOCKED` — explicitly approved and authoritative | ||
| - `PROPOSED` — generated or suggested for approval | ||
| - `OBSERVED` — directly present in evidence | ||
| - `INFERRED` — supported interpretation | ||
| - `SPECULATIVE` — low-confidence creative possibility |
There was a problem hiding this comment.
These values are not mutually exclusive: a claim can be directly OBSERVED and also approved as LOCKED, or be INFERRED and remain PROPOSED. The existing schemas/design-specification.schema.yaml correctly models document authority separately from per-claim provenance, while this one-of contract would force implementations to discard either the claim's evidentiary basis or its approval state. Define separate authority and provenance fields instead.
Useful? React with 👍 / 👎.
| The preferred v0.15 surface: | ||
|
|
||
| ```bash | ||
| kubrick do design create --evidence project/ --output design.md |
There was a problem hiding this comment.
When these examples are implemented by only expanding the manifest/actions listed in the P0 workstream, they will not select create, improve, or the other positional actions: the current _resolve_do router recognizes actions only through --action, and otherwise forwards positional tokens to the default implementation. Thus every command in this target block remains invalid unless the router is explicitly extended to parse positional actions; add that routing work and compatibility tests, or use the existing --action <action> syntax here.
Useful? React with 👍 / 👎.
Implementation wave 1 completeThe PR has moved beyond documentation and now includes the executable v0.15 foundation. Added
Current boundaryThis wave establishes the public commands and deterministic artifact envelope. Domain compilers are still foundation-level: they resolve the requested operation and enforce contracts, but do not yet perform full section-aware Next implementation wave
Tracks #33. |
1 participant
Summary
Defines the v0.15 product and engineering contract that promotes four peer Kubrick production surfaces:
design— fulldesign.mdlifecycle: create, improve, audit, reconcile, update, validatescript— create, improve, diagnose, adapt, continuity-check, and hand off scriptsimage— neutral and provider-ready image prompts, sequences, references, negatives, and QAvideo— temporal shot, motion, sequence, adaptation, and QA contractsThe specification establishes one shared cinematic state model, required artifact contracts, a section-aware design improvement algorithm, video temporal state requirements, compatibility rules, implementation workstreams, and acceptance criteria.
Tracks issue #33.
Why
Kubrick v0.14 already has strong symbolic compilation, continuity, storyboard, provider adaptation, and visual QA. However,
design.mdis currently exposed as a single build action, scriptwriting has no first-class CLI intent, image prompting is distributed across compile/adapt, and video prompting has no explicit surface. This PR defines the bounded architecture needed to close those gaps without breaking current commands or authority rules.Validation
Documentation-only architectural change. Runtime implementation and tests are explicitly scoped in issue #33.