@aswless_854771076/ai_short_studio_cli 0.1.98 → 0.1.100

package/skills/using-vvicat-ai-short-studio-cli/references/hypit/production/script-syntax.md

@@ -0,0 +1,236 @@
+# Script syntax
+
+Read this when writing or correcting `<script>`, including display spelling, pronunciation,
+spaces, Caption grouping and semantic markers. [Script and semantic time](../creation/script-and-time.md)
+owns the creative decisions; [Source syntax](source-syntax.md) owns imports and graph references;
+[Timing](timing.md) explains how components use the resulting identities.
+
+These are the current 0.2 author forms. Package releases and logical Module ABIs are different:
+`@hypit/script@1` remains the import. A syntax error calls for an explicit correction to the source;
+do not reinterpret old bare markers or remove authored spaces to make an inherited example work.
+The installed Script package owns the parser and exact diagnostics.
+
+## Keep the languages distinct
+
+| Where you are writing | Form | Meaning |
+| --- | --- | --- |
+| Structured Source attribute | `narrative={story}` | A whole-value graph reference. |
+| Script prose | `@{reveal!}` | A semantic Moment; contributes no displayed or spoken text. |
+| Script prose | `clear{emphasis}` | An attribute on the preceding display word. |
+| A model's prompt text | `@image1` | That model's reference notation, when its Kit declares it. |
+| A temporal attribute | `instant="moment.cue + 8f"` | The component's explicit time expression. |
+
+Braces and at-signs have no global substitution rule. The receiving Surface owns its body's grammar.
+
+## Structure, grouping and display attributes
+
+The author-facing forms are:
+
+| Form | Meaning |
+| --- | --- |
+| `<opening>...</opening>` | A Segment named `opening`; all spoken prose belongs inside a Segment. |
+| `<pause/>` | A self-closing Segment with identity and boundaries but no words. |
+| `<HOST>` | A Role Cue inside the current Segment; it applies until another Role Cue or the Segment end. |
+| `<display text \| spoken text>` | One Dual Text unit with separate visible and pronounced wording. |
+| `<display text\|>` | One complete display/speech unit using the same wording for both; individual spoken word times remain available. |
+| `< \| spoken text>` | Spoken words that keep semantic timing while contributing no visible Caption words. |
+| `\|\|` | A Caption Cue handoff between complete Alignment Units. |
+| `word{emphasis,keyword}` | Boolean attributes on one complete display word for a Caption family to interpret. |
+| `word{importance=2,tone=warm}` | Named string, number or boolean attribute values on that display word. |
+| `@{proof} ... @{/proof}` | A Selection: one named semantic range. |
+| `@{claim!}` | A Moment: one named semantic point. |
+
+A Script contains one or more uniquely named Segments matching `[a-z][a-z0-9_-]{0,63}`;
+`script` is reserved. A paired Segment can carry prose or be wordless; the self-closing form also
+carries a wordless passage. A Role Cue is a bare turn marker: the next Role Cue begins the next turn,
+and closing the Segment ends the final turn
+and resets its Role. When a Segment uses Roles, place the first Role before that Segment's first
+spoken text. One Segment can contain several Role turns without requiring several generated Takes. A bare tag
+inside a Segment is a Role Cue by context, not by capitalization: `<host>`, `<主持人>` and
+`<진행자>` can name speakers. The label directs the request through dialogue; it selects no voice
+or character asset by itself.
+
+Dual Text can contain several visible or spoken words on either side; its display side feeds Caption
+and its spoken side feeds pronunciation. An empty display side intentionally omits those spoken words
+from Caption while keeping them in the Narrative and semantic timing. Selections and Moments can be
+placed on the spoken side because that side owns the speech anchors. Place Cue Breaks around the
+complete Dual Text unit, not inside it. Attributes for a displayed Dual Text word belong on the
+display side before the pipe. Inside that display side, use `\@` when the visible text itself needs an
+at-sign.
+
+The three Dual forms serve distinct author choices:
+
+| Script fragment | Display | Speech | Use |
+| --- | --- | --- | --- |
+| `<S\|ess>` | `S` | `ess` | Keep the spelling while specifying the letter's spoken name. |
+| `<New York\|>` | `New York` | `New York` | Keep the same words and internal space in one complete correspondence. |
+| `<\|再见>` | No Caption words | `再见` | Retain speech and its semantic anchors without displaying it. |
+
+[Pronunciation choices](../creation/script-and-time.md#choose-the-sound-the-spelling-should-carry)
+shows letter names, abbreviations, coined names and homophonic readings. The spoken side is ordinary
+Text supplied to the selected model, not a separate phonetic language interpreted by Script.
+
+When the wording is identical, `<组件化|>` is shorthand for `<组件化|组件化>`. It can group a name,
+compound or phrase for Caption presentation while leaving its spoken Tokens and timing intact:
+`把<动效|><组件化|>。|| 以后就能<直接复用|>。` Choose groups for the intended expression; ordinary
+Chinese prose does not require word-by-word markup. The group's Style determines its visual response;
+`||` still controls which reading phrases appear as separate Cues.
+
+With speech omitted, the left side supplies both projections, so semantic markers can be placed
+there and Studio writes back there: `<组@{beat!}件化|>`. Display attributes and markers are annotations,
+not spoken words. Attributes still apply to the preceding display word rather than the whole group.
+With an explicit spoken side, markers continue to belong on that right-hand side.
+Either form needs a spoken word: `<API|...>` supplies no speech correspondence for its display.
+
+Script comments contribute no text and do not split a word: `hel<!--note-->lo` remains `hello`.
+In ordinary prose, a comment or zero-width marker also leaves a following attribute attached to its
+word: `hello<!--note-->{emphasis}` and `hello@{beat!}{emphasis}` annotate `hello`.
+An actual space before `{emphasis}` breaks that attachment.
+A comment can also stand between passages:
+
+```svml
+<!-- This note enters no text projection. -->
+<social><HOST> Follow us \@hypit.</social>
+```
+
+Reserved Script punctuation remains literal when escaped: `\@` produces `@`, `\<` produces `<`,
+`\{` produces `{`, `\}` produces `}`, `\|` produces `|`, and `\\` produces `\`. A plain `>` needs
+no escape in ordinary prose; inside Dual Text, `\>` keeps it from closing that unit. A single `|` in
+ordinary prose is literal; `||` is the Caption Cue handoff. Inside Dual Text, the first unescaped `|`
+separates display from pronunciation; write `\|` for a literal pipe and `\|\|` for two literal pipes.
+These escapes belong to Script prose, while structured Source attributes and elements use the Markup
+escaping described in [Source syntax](../production/source-syntax.md).
+
+Script derives speech tokens from words and numbers. Punctuation remains attached to the displayed
+word it belongs with and does not create another speech time unit. CJK prose commonly contributes
+one Han, Hiragana or Katakana character per lexical unit; compounds, decimal numbers and the spoken
+side of Dual Text preserve their own lexical structure. This is why Cue breaks, word attributes and
+semantic markers attach to complete authored units instead of punctuation or visual line positions.
+Character-level timing does not call for character-sized Cues: use `||` for meaningful reading
+phrases. [Caption craft](../playbooks/craft/captions.md#language-changes-the-reading-unit) explains
+Chinese, English and mixed-script grouping, spacing and their fit in the picture.
+
+## Preserve spelling independently of timing
+
+Ordinary whitespace runs become one displayed/spoken space. Leading and trailing whitespace in a
+Turn and padding at the edges of each Dual side are omitted. A Source newline is prose formatting;
+`||` makes a Caption Cue handoff, and the Caption family controls visual line wrapping.
+
+| Script body inside a Segment | Display text | What the author chose |
+| --- | --- | --- |
+| `是的 就是这样` | `是的 就是这样` | A real space in Chinese prose. |
+| `是的@{answer}就是这样@{/answer}` | `是的就是这样` | Joined text with a zero-width semantic range. |
+| `是的 @{answer}就是这样@{/answer}` | `是的 就是这样` | The same range after an authored space. |
+| `Hello @{place}New York.@{/place}` | `Hello New York.` | English spaces and attached punctuation. |
+| `이건 3개월 동안 만든 영상이에요.` | `이건 3개월 동안 만든 영상이에요.` | Korean word spaces; no space inside `3개월`. |
+| `3 개월` | `3 개월` | An explicitly different spelling. |
+| `3D` / `3 D` | `3D` / `3 D` | Numeric/Latin adjacency is also authored. |
+| `<New York\|>` | `New York` | One Alignment Unit with an internal space. |
+| `<API\|A P I>` | `API` | One correspondence to several spoken tokens. |
+| `<\|只说不显示>` | *(no visible words)* | Spoken content and semantic timing remain. |
+
+Do not insert spaces around markers for parsing, strip Chinese spaces, or infer Korean/English gaps
+from speech tokens. A space is display information, not an extra timed token. Caption consumers use
+`separatorBefore` together with each display word's `text`; suppress a leading separator at a displayed
+line/Cue start. [Caption authoring](caption-authoring.md) explains consuming these values in a new family.
+
+The Script source and its projections answer different needs. Source preserves the author's prose;
+display and speech normalize ordinary whitespace as above. Studio moving a marker relocates only
+that annotation and retains unrelated source whitespace. Explicit Script formatting may reindent
+and compact whitespace while preserving the same parsed meaning.
+
+## Use the Script's deliberate projections
+
+One Script publishes the full Narrative and the narrow views needed by the rest of the work:
+
+| Reference | What it carries |
+| --- | --- |
+| `{story}` | The complete authored Narrative. |
+| `{story.segment.hook}` | The `hook` Segment as a NarrativeExcerpt for one SemanticTake. |
+| `{story.segment.hook.dialogue}` | Role-aware dialogue using the spoken side of Dual Text, suitable for a speaking performance request. |
+| `{story.segment.hook.speech}` | Pronunciation-only Text, suitable for `hypit measure` or independent speech. |
+| `{story.caption}` | Display Words, Alignment Units, attributes, Roles, and authored Cue Breaks for Caption. |
+| `{story.selection.proof}` | The named semantic range. |
+| `{story.moment.claim}` | The named semantic point. |
+
+For example, this Segment inside `story` assigns two speaking turns:
+
+```svml
+<exchange>
+  <HOST> Let me show you.
+  <GUEST> That looks much easier.
+</exchange>
+```
+
+`{story.segment.exchange.dialogue}` supplies:
+
+```text
+HOST: Let me show you.
+GUEST: That looks much easier.
+```
+
+Pass that Text to the speaking prompt. In action direction, relate HOST and GUEST to the supplied
+character views and voices. The selected [Prompt Kit](prompt-kits.md) owns its reference
+order; [podcast direction](../playbooks/formats/two-person-podcast.md#direct-conversation-inside-a-take)
+shows how those roles and references form one performed exchange.
+
+These are projections of one authored Script, not copies to maintain. The performance request,
+Caption system, and semantic timing therefore remain connected even when their visible and spoken
+wording differ.
+
+## Bind meaning to Script identities
+
+Every semantic marker is enclosed in `@{...}`, with `/`, `!` and `~` inside. The marker contributes
+no text or whitespace. `是的@{part}就是这样@{/part}` stays joined; `是的 @{part}就是这样@{/part}`
+keeps its authored space. Do not add spaces to make a marker parse. Markers cannot split a speech
+Token or its attached punctuation: write `@{beat!}“测试”`, not `“@{beat!}测试”`.
+`hel@{beat!}lo` and `안@{beat!}녕` also split tokens. Grouping with Dual Text does not make these
+positions legal. Attributes stay attached to their display word: `word{emphasis}@{beat!}`.
+Write literal `@{part}` as `\@\{part\}`.
+
+Selections may overlap, cross, or span Segments; they are named semantic ranges rather than nested
+markup. Selection and Moment names share one namespace and match `[a-z][a-z0-9_-]{0,63}`.
+Inside spoken text, each marker chooses an
+adjacent semantic boundary:
+
+| Marker | Boundary |
+| --- | --- |
+| `@{name}` | Open a Selection at the next word's start. |
+| `@{~name}` | Open a Selection at the previous word's end. |
+| `@{/name}` | Close a Selection at the previous word's end. |
+| `@{/name~}` | Close a Selection at the next word's start. |
+| `@{name!}` | Place a Moment at the next word's start. |
+| `@{~name!}` | Place a Moment at the previous word's end. |
+
+Markers may sit between or outside Segments when the meaning crosses structural passages. For
+example, this Selection owns the complete Script program rather than borrowing the first and last
+word boundaries:
+
+```svml
+@{~whole}
+<opening><HOST>First thought.</opening>
+<answer><HOST>Final answer.</answer>
+@{/whole~}
+```
+
+At a Script or Segment edge, the corresponding structural boundary remains available even when
+there is no neighboring word. Thus `@{videos} videos @{/videos}` covers exactly that word. Adjacent
+visual Windows can share a boundary at either side of the pause between words. To give that pause
+to the incoming picture, meet at the previous word's end:
+
+```svml
+@{coffee} my coffee @{/coffee} @{~smoothie} my smoothie @{/smoothie}
+```
+
+To give it to the outgoing picture, meet at the next word's start:
+
+```svml
+@{coffee} my coffee @{/coffee~} @{smoothie} my smoothie @{/smoothie}
+```
+
+Both Selections now meet at one instant in either example. A `||` between the phrases changes
+Caption grouping, not their visual boundary. [Material-led picture craft](../playbooks/craft/b-roll.md)
+owns whether the edit should meet there, leave a pause visible or let another picture continue.
+
+The marker locates meaning, not an animation's lifetime. A reveal may leave its answer visible;
+a covering picture may occupy the full Selection. [Timing](timing.md) explains those consuming forms.

package/skills/using-vvicat-ai-short-studio-cli/references/hypit/production/snapshots.md

@@ -0,0 +1,90 @@
+# Inspect the current picture
+
+Use `hypit snapshot` first when the question concerns an existing production's visible state,
+layout or motion sequence. It captures selected frames of the current picture through the
+Profile's `render-frames` Endpoint. Studio playback supplies motion with sound; an encoded video
+supplies evidence about the delivered file. Choose the view that establishes the relationship.
+
+## Capture the work already open in Studio
+
+Open the actual Run using [Studio](studio.md). After its current preview is ready:
+
+```bash
+hypit snapshot --studio http://localhost:5191 \
+  --at-frame 240 --to evidence/comparison-detail
+
+hypit snapshot --studio http://localhost:5191 \
+  --at-frame 240,255,269 --grid 3x1 --cell 480 --to evidence/comparison-states
+
+hypit snapshot --studio http://localhost:5191 \
+  --start-frame 240 --end-frame-exclusive 270 --step-frames 1 \
+  --grid 4x3 --cell 480 --to evidence/comparison-motion
+```
+
+Use the address of the existing Studio session and frames located in that programme. The examples
+demonstrate the options. Locate meaningful events through Script, Timeline or the Studio playhead;
+pass their resulting frame positions to the observation command. Frame selection does not change
+the authored timing relationship.
+
+Studio supplies its already compiled `HyperframesDocument` and the material selected by the Run.
+This preserves declared fonts, images, video sampling, transparent Surfaces and resources used
+inside a component's browser program. The command sends one immediate request, keeping the original
+programme clock and component-local clocks. It writes images directly into the chosen directory.
+There is no new Build, material generation or video encoding in this call.
+
+Use `--runtime <profile>` and `--workspace <project>` when the invocation needs an explicit selection;
+otherwise run in the project that already selected its Profile. The command names the selected
+Endpoint before execution. If several Endpoints offer frame capture, select one with the Profile's
+`@hypit/render-hyperframes@1#render-frames` binding. Browser preparation remains with that Provider:
+[local tools](../environment/local-tools.md#prepare-the-local-rendering-browser).
+
+## Read frames at the scale the question needs
+
+- `--at-frame` chooses one frame or a strictly increasing list of frames.
+- A range includes `--start-frame` and excludes `--end-frame-exclusive`. `--step-frames 1` retains
+  every frame. Frame indices start at zero on the original programme clock.
+- Every selected frame is saved as a full-size PNG. Open one for typography, edges and geometry.
+- `--grid columnsxrows` adds paginated contact sheets. `--cell` chooses the width of each picture;
+  labels sit below it and give its original frame index and time. The full-size PNGs remain available.
+- `--json` reports the output paths and frame positions for subsequent inspection.
+
+Widen the interval to understand a handoff, follow every frame to understand a movement, and enlarge
+the image to judge small detail. Compare the corresponding event in reference and production;
+different performances can put that event at different seconds. Revisit the whole passage in Studio
+to hear and feel how the observed states work together.
+
+## Existing HTML and source video
+
+An already materialized HyperFrames HTML file can also be the input:
+
+```bash
+hypit snapshot ./picture/index.html --at-frame 240 --to evidence/html-detail
+```
+
+The HTML carries its compiled frame clock and frame-sampling declarations. Its directly referenced
+media and fonts travel with the request; scripts and styles are inline. An HTML URL is accepted too.
+For a current Studio work, prefer `--studio`: its compiled document also retains resource declarations
+inside JavaScript data and the full typed Surface input. Snapshot is a programme-frame operation;
+[browser capture](browser-capture.md) owns screenshots of ordinary websites and applications.
+
+For an existing source video or encoded Result, use the media commands. Native-frame extraction
+decodes each chosen interval once and retains the source's actual timestamps, including variable
+frame rates:
+
+```bash
+hypit media tiles reference.mp4 --start 8 --end 9 --every-frame \
+  --columns 4 --rows 3 --cell 480 --to evidence/reference-motion
+```
+
+`media frames --every-frame` saves individual images; `media tiles --ranges ranges.json
+--every-frame` follows several selected intervals. `--transcript` adds the words around each
+actual frame. [Reference understanding](../creation/reference-video.md) connects these views to
+coarse and fine observation.
+
+## After a composition change
+
+Keep accepted material selected in the Run, let Studio compile the updated Source, then capture the
+affected states and their handoffs. Carry discoveries back to the owning Source, component or
+Treatment. This is the preferred picture-review path. Use a
+[range render](rendering.md#choose-a-render-interval-in-frames) when a short encoded video with sound
+is the evidence or deliverable needed; render and inspect the full file for final export.

package/skills/using-vvicat-ai-short-studio-cli/references/hypit/production/sound.md

@@ -0,0 +1,75 @@
+# Presenting existing sound
+
+Use Sound to present audio from Takes already placed on the [Timeline](timeline.md). Use
+[Audio Track](audio-presentation.md) for independently supplied sound. Sound chooses how existing sources are heard; [Performance](performance.md)
+chooses how their pictures appear. Neither changes the Script or the Take placements.
+
+## Broad treatment and local Uses
+
+```svml
+<import as="sound" from="@hypit/sound@1"/>
+<sound:Style id="normal"/>
+<sound:Style id="opening" gain="0" end-gain="1"/>
+<sound:Style id="silent" gain="0"/>
+<sound:Track id="voice" timeline={program.timeline}>
+  <sound:Use style={normal}/>
+  <sound:Use at="0f" for="2s" style={opening}/>
+  <sound:Use during={story.selection.demonstration} style={silent}/>
+</sound:Track>
+```
+
+Select `voice.audio` in Film to hear this presentation. Timeline retains source material; Sound
+chooses how it is heard. Independent music and effects remain separate Film contributions.
+
+The first Use sets a broad treatment. The last matching Use replaces it locally, including when
+the winner is silent. A later normal Use can restore sound inside a muted passage. No matching
+Use means no sound from this Track. This is the same broad/local presentation rule as Performance
+and Caption, with time Windows as Sound's domain.
+
+The ordinary Style chooses the last Timeline-declared active source with audio. A Take without an
+audio member contributes no candidate. No Take means no original sound; it does not affect separate
+music or effects. A recording that contains silence is still an audio source.
+
+`gain` is a linear amplitude multiplier, normally 1; `end-gain` defaults to the same value. Different
+values create a linear change over the Use's full Window. Use `gain="0"` for silence, or
+`gain="1" end-gain="0"` for a fade-out. A leading Timeline gap has no source to fade: attach an
+opening fade to the first Take's actual start when it begins later than the program.
+
+All shared time forms apply: `during`, `at` + `for`, `until` + `for`, and `start` + `end`. Word-related
+changes can follow Selections or Moments; independently timed changes can use seconds or frames.
+The Window governs treatment progress, while the Take placement governs source playback. After a
+local override, both resume at the progress appropriate to the current time.
+
+## Explicit source relationships
+
+For a crossfade, a project Style selects its outgoing and incoming Segments explicitly. An ordinary
+Use then selects the overlap Window. A Style declaration might look like:
+
+```svml
+<mix:Crossfade id="handoff"
+  outgoing={story.segment.first} incoming={story.segment.second}/>
+<sound:Track id="voice" timeline={program.timeline}>
+  <sound:Use style={normal}/>
+  <sound:Use style={handoff}
+    start-source={story.segment.second} start="segment.start"
+    end-source={story.segment.first} end="segment.end"/>
+</sound:Track>
+```
+
+Here `mix:Crossfade` is a project-defined Style, not a built-in Sound tag. Its complete example ships
+at `examples/semantic-composition/packages/sound-styles/` in the Hypit Distribution. The interval
+locates the effect; the bound sources determine its roles. Sound does not infer a mix from a visual
+transition. A family for intentional simultaneous speech can retain both sources at full gain.
+
+## Author a new sound Style
+
+Use `soundStyle(fragment, bindings)` from `@hypit/hypit/sound`. Its fragment receives `timeline` and
+the original `window`, plus the family's typed bindings, and exports `audio: AudioTrack`. A Surface
+publishes this definition as an inline `soundTypes.style` value. Each Use expands normal graph edges.
+
+`sourceSound(timeline, window, segment, { gain, endGain })` selects one existing source, and
+`ordinarySound(timeline, window, { gain, endGain })` provides the usual last-source behavior. Known
+sources without audio return no clips. A custom family can combine explicit sources or author a
+richer gain envelope using ordinary AudioClip data. No new renderer mode is needed.
+See [component authoring](track-authoring.md) for packaging and [sound direction](../playbooks/craft/sound-mix.md)
+for deciding what the audible change contributes to the work.

package/skills/using-vvicat-ai-short-studio-cli/references/hypit/production/source-syntax.md

@@ -0,0 +1,163 @@
+# Reading and writing Source syntax
+
+Read this for the language around a production: imports, references, literal values, Recipes and
+Run choices. [Script syntax](script-syntax.md) owns prose, Roles, Dual Text, Cue breaks, display
+attributes and markers. [Timing](timing.md) explains how components consume those identities.
+[System relationships](system.md) explains authored values and computed Outputs.
+
+## Three documents, three decisions
+
+A `.svml` normally describes the work, a `.svs` holds reusable authored values, and a `.svrun`
+chooses what to execute and reuse. Each document's Header selects its parser; the filename extension
+is the convention used to recognize its role.
+
+This small Author Source produces Text and Script values; it makes no media request:
+
+```svml
+<?svml using="@hypit/markup@1"?>
+<svml>
+  <import from="@hypit/script@1"/>
+  <import as="copy" from="@hypit/text@1"/>
+  <import as="kit" source="./direction.svs"/>
+
+  <script id="story">
+    <opening><HOST>Here is @{proof}the useful part.@{/proof}</opening>
+  </script>
+  <copy:Value id="direction">She leans in slightly, amused by her own observation.</copy:Value>
+  <copy:Render id="prompt" template={kit.performance}>
+    <copy:Set name="dialogue" text={story.segment.opening.dialogue}/>
+    <copy:Set name="direction" text={direction}/>
+  </copy:Render>
+</svml>
+```
+
+Package imports expose vocabulary under a local alias. Source imports expose a document's public
+values: `<import as="look" source="./look.svs"/>`. A data package can expose the same kind of Source,
+for example `<import as="ugc" source="@hypit/gpt-image-kits/phone-ugc-v1"/>`; its own relative imports
+and assets stay inside that package. Put imports in the leading prologue, before body declarations.
+Use a package's logical Module ABI, such as `@hypit/text@1`, in `from`; installed package versions
+belong to ordinary package management. Reading a packaged Source does not activate its JavaScript.
+
+A Source alias qualifies public bindings; it does not rename a Narrative's authored identity.
+Two imported Sources declaring different Scripts both named `story` therefore conflict. Share the
+one Script that owns the work, or give genuinely separate Narratives distinct ids.
+
+## Braces connect values
+
+`duration="5"` is literal attribute text interpreted by the receiving Surface.
+`prompt={direction}` is a whole-value graph reference, checked against the declared input Type.
+`prompt="direction"` is a string, not that reference. Braces contain whole-value graph references.
+Use `copy:Render` with a TextTemplate and explicit bindings to assemble text; use the receiving
+package's expression syntax where it declares one, such as temporal offsets.
+
+Output paths are package vocabulary, not inferred from the element's tag:
+
+- `copy:Value id="direction"` publishes `{direction}`;
+- an imported `media:Image id="logo"` publishes `{logo}`;
+- `gpt:Image id="portrait"` publishes `{portrait.image}`;
+- `pipeline:Normalize id="prepared"` publishes `{prepared.media}`;
+- `time:Timeline id="speech"` publishes `{speech.timeline}`. Performance and Sound separately publish the picture and sound contributions selected in Film.
+
+Inspect `hypit vocabulary` for the actual Surface's exports and use the published path it reports.
+Public bindings can be authored Records or realizable Logical Outputs. Script,
+Recipes and literal Text already exist as authored data; they are not Run Targets. The computed
+`prompt` from `copy:Render` is a Logical Output that can be targeted or satisfied by a Candidate.
+Name declarations before the structured Surfaces that resolve their inputs; the current Markup
+handlers inspect imported values and earlier declarations during decoding. Graph edges, rather than
+XML body order, schedule execution.
+
+Different bodies have different readers. Script uses its own prose grammar; structured components
+declare their permitted attributes and children; Text has its own literal/template forms. In
+structured Markup, use the receiving Surface's declared attributes, children, literals, Recipes and
+reference expressions, and escape `&`, `<`, `>`, `"`, and `'` as `&amp;`, `&lt;`, `&gt;`,
+`&quot;`, and `&apos;`; comments use `<!-- ... -->` outside raw bodies. Script owns the punctuation
+inside its raw body, as described in [Script syntax](script-syntax.md).
+
+## Recipes are named values
+
+```svs
+<?svml using="@hypit/svs@1"?>
+<sheet version="1">
+  media.cover {
+    fit: cover;
+    stack-order: 10;
+  }
+</sheet>
+```
+
+Imported as `look`, this rule is `{look.media.cover}`. Recipe rule names use dotted paths, such as
+`media.cover`. Rules do not inherit or cascade. Scalars, strict JSON arrays and strict JSON objects are
+supported; each consumer owns the allowed properties, defaults and units. A Caption Style's Recipe
+is not interchangeable with Media appearance merely because both have a color or size.
+
+Every property ends with `;`. `null`, booleans, finite numbers, and simple bare words are scalar
+values. Quote strings whose punctuation could be read as SVS syntax. Arrays and objects use strict
+JSON, including quoted keys and strings:
+
+```svs
+caption.host {
+  enabled: true;
+  color: "#ff6f61";
+  padding: [12, 18];
+  motion: {"kind":"spring","amount":0.12};
+  enter: 8f;
+}
+```
+
+Units such as `8f`, `250ms`, and `50%` remain strings until the consuming package interprets them.
+Recipe values do not evaluate graph references. Media, fonts, semantic ranges, and other graph
+values remain explicit Source inputs to the component that consumes them.
+
+Some packages, such as TextTemplate, explicitly define parameter precedence. That local behavior
+does not create global SVS inheritance. A Prompt Kit remains a reusable text program; image
+references, voice references, model parameters and generated Outputs stay explicit in Author Source.
+
+The `direction.svs` used above selects Text's own Recipe Frontend to produce a TextTemplate rather
+than ordinary Recipes. This is the same file-extension convention with a different explicit Header:
+
+```svs
+<?svml using="@hypit/text/svs@1"?>
+<sheet version="1" id="performance">
+  text-template.performance { separator: paragraph; }
+  text-template.performance.block.dialogue {
+    kind: slot;
+    order: 10;
+    slot: dialogue;
+  }
+  text-template.performance.block.direction {
+    kind: slot;
+    order: 20;
+    slot: direction;
+  }
+</sheet>
+```
+
+This small Kit just joins two Text inputs. It does not generate a video. Fixed blocks and variable
+axes can be added when they express reusable direction; `@hypit/text` owns that template grammar.
+
+## Runs demand Outputs and choose Candidates
+
+For the Text example saved as `main.svml`, beside `direction.svs`:
+
+```svml
+<?svml using="@hypit/run-markup@1"?>
+<svrun version="1">
+  <author source="./main.svml"/>
+  <target output="prompt"/>
+</svrun>
+```
+
+A video Run usually targets the renderer's public video Output. Several Targets are valid when
+several deliverables are wanted. Targets are public Output names; requests outside the demanded graph
+are not executed.
+
+To reuse a prior Output, declare a `build-record` Candidate and select it with `satisfy`; the prior
+Result name and the current Logical Output name can differ. A raw MP4 file is a Blob Artifact, not
+an aligned SemanticTake. Select Candidates by their real nominal Type and creative meaning, retaining
+normalization or alignment where still needed. [Runs](runs.md) explains complete Candidate forms,
+Fragment inputs and exports; [Authoring](authoring.md) owns the creative reuse decisions;
+the installed Fragment package owns its own input and export names.
+
+`hypit check <run>` checks Source and graph legality. `hypit plan <run> --runtime <profile>` exposes
+the selected graph and external requests without submitting them. A legal document can still describe a
+poor image, a misplaced Caption or an unhelpful cut; those remain directing questions.