Skip to content

armgit / hypit

Public Imported from GitHub
0

Clone any viral video with AI agents. Not just a script, the whole workflow: swap the face, the words, the B-roll, ship 100 variants in one command, and get your 100M views.

docs: teach the 0.3 production model in the Hypit skill

kashorin436bb27310fb
diff --git a/skills/hypit/references/creation/project-files.md b/skills/hypit/references/creation/project-files.md
index 1c6920d4..2f59ad56 100644
--- a/skills/hypit/references/creation/project-files.md
+++ b/skills/hypit/references/creation/project-files.md
@@ -43,26 +43,28 @@ can later hold the project's component dependencies:
"name": "workshop-video",
"version": "0.0.0",
"private": true,
- "type": "module"
+ "type": "module",
+ "hypit": { "project": true }
}
```
-The CLI uses the nearest `package.json` above the command's working directory, or that directory
-itself when none exists. Passing a Source or Runtime path does not select a different project.
+The CLI searches upward for a `package.json` whose `hypit.project` field is `true`. It does not turn
+the nearest component package or an arbitrary working directory into a project. Passing a Source or
+Runtime path does not select a different project.
Sources can live below the root, with file and Source imports relative to the declaring file.
| Boundary | When to set it explicitly |
| --- | --- |
-| `--workspace <directory>` | Choose the project root for Sources, Runtime selection, project packages and Results when running from another directory |
+| `--project <directory>` | Choose the project root for Sources, Runtime selection, project packages and Results when running from another directory |
| `--asset-root <directory>` | Admit assets stored elsewhere while keeping Source imports in their workspace |
| `--package-root <directory>` | Resolve project packages from another installation location |
-Relative command-line paths start at the shell's current directory. `--workspace` selects the project
+Relative command-line paths start at the shell's current directory. `--project` selects the project
without rebasing the Run, Source or `--runtime` argument. For example, from outside a project:
```bash
-hypit paths --workspace /path/to/video-project
-hypit studio --run /path/to/video-project/build.svrun --workspace /path/to/video-project
+hypit paths --project /path/to/video-project
+hypit studio --run /path/to/video-project/build.svrun --project /path/to/video-project
```
`paths` shows the resolved project and where its Runtime selection came from. Source imports and asset
@@ -70,8 +72,9 @@ references inside files remain relative to their declaring file.
For example, `hypit check authors/main.svml --asset-root /path/to/shared-media` admits intentionally
referenced shared media. Keep the same relevant boundaries for subsequent commands. An ordinary
-project uses its own package installation; reserved `@hypit/*` packages come from the selected
-Distribution. [Distribution](../environment/distribution.md) explains locating that executable,
+project uses its own package installation. Exact packages embedded in the selected Distribution come
+from that Distribution; independently distributed packages, including `@hypit/*` packages, remain
+ordinary project dependencies. [Distribution](../environment/distribution.md) explains locating that executable,
and [component vocabulary](../production/vocabulary.md#let-ordinary-package-management-own-distribution)
explains installing project packages.
@@ -184,15 +187,15 @@ authored work and the produced values that its Runs select:
- project component source or installed-release dependencies, `package.json`, its lockfile and any
tarballs referenced by `file:` dependencies;
- the completed Results used by `build-record` Candidates, including their media and Composite value
- documents, plus the project Result repository selection;
+ documents;
- the intended Runtime configuration, with account access configured on the receiving machine through
its own Credential Store.
For the default filesystem repository, preserving `.hypit/results/` intact with the project is the
straightforward handoff. Include the hidden directory and keep its date/Build subdirectories. Some
Results forward an Output to its original owning Build, so copying only the latest Build directory
-can omit media still in use. A custom filesystem or S3 repository needs the corresponding files or
-access and an explicit destination selection; changing `hypit.results.json` does not move them.
+can omit media still in use. Archive or migrate completed Results explicitly when they should live
+outside the project.
External input files remain live dependencies, including when referenced inside structured Outputs.
The Node workspace records their resolved file addresses. When moving to another machine, provide
diff --git a/skills/hypit/references/creation/reference-video.md b/skills/hypit/references/creation/reference-video.md
index 819d67bd..dc90ef86 100644
--- a/skills/hypit/references/creation/reference-video.md
+++ b/skills/hypit/references/creation/reference-video.md
@@ -5,7 +5,7 @@ from. The useful result is a timecode-level semantic reading: what the piece com
its exact audiovisual choices make that communication work.
For a reference supplied as a link, [video download](../production/video-downloads.md) explains
-`hypit media fetch`, its local preparation and the saved source file used by the tools below.
+`hypit download`, its explicit preparation and the saved source file used by the tools below.
## Read the whole through its details
diff --git a/skills/hypit/references/creation/script-and-time.md b/skills/hypit/references/creation/script-and-time.md
index 06676e53..073737fe 100644
--- a/skills/hypit/references/creation/script-and-time.md
+++ b/skills/hypit/references/creation/script-and-time.md
@@ -1,7 +1,7 @@
# Script and semantic time
Read this when deciding the target wording, pronunciation, performable passages and the meanings
-that picture and sound should follow. It also covers measured delivery and wordless passages.
+that picture and sound should follow. It also covers estimated delivery duration and wordless passages.
[Script syntax](../production/script-syntax.md) owns the authoring forms;
[Timing](../production/timing.md) owns their projection into the work.
@@ -87,7 +87,7 @@ the whole expression rather than inserting artificial pauses between every lette
Phonetic notation, including IPA, can guide a model that understands it. Script forwards the written
form literally; it does not interpret IPA or expose a phoneme-control API. The spoken projection also
-feeds measurement and semantic preparation, so choose a representation usable by that production's
+feeds duration estimation and semantic preparation, so choose a representation usable by that production's
speech path. Any model-specific pronunciation feature belongs to that model's documented inputs.
Keep a reading aid such as `ess` on the spoken side; prose instructions such as “pronounce this as”
belong in performance direction when needed, not among the words the Script asks the character to say.
@@ -108,12 +108,12 @@ belong in performance direction when needed, not among the words the Script asks
Each pair applies to that occurrence. Carry the chosen spoken form into every occurrence of the
name, including other Segments, so separately generated performances receive the same direction.
The right-hand wording reaches the model through the Segment's `.dialogue`; Caption keeps the
-display spelling. Settle these readings before measuring the Script and requesting its performance.
+display spelling. Settle these readings before estimating the Script's duration and requesting its performance.
The same distinction helps Chinese copy express numbers and names clearly. For example,
`今年<2026|二零二六>年` displays the year compactly while specifying how it is said;
`只要<¥19.9|十九块九>` chooses a conversational price reading. Choose the spoken form for this
-sentence's meaning and delivery. Measuring the Segment with `--language zh` then uses that spoken
+sentence's meaning and delivery. Estimating the Segment with `--language zh` then uses that spoken
wording, including the syllables hidden behind its compact numeric display. Caption retains the
authored simplified or traditional characters; transcription supplies timing rather than rewriting
the displayed Script.
@@ -121,7 +121,7 @@ the displayed Script.
## Choose performable passages
Supply the Segment's `.dialogue` to the speaking prompt; it includes Role labels and the chosen
-pronunciation. `.speech` supplies pronunciation without Role labels for measurement or speech-only
+pronunciation. `.speech` supplies pronunciation without Role labels for duration estimation or speech-only
requests. The Caption view preserves the display wording. These are projections of one Script,
so revising the words does not require maintaining another copy in a prompt or subtitle file.
[Script projections](../production/script-syntax.md#use-the-scripts-deliberate-projections) shows the
@@ -175,27 +175,27 @@ Instant, optionally with an explicit offset, then pass the result to the compone
trigger and its entrance duration are different choices: `at={story-time.answer}` locates the
answer; ten frames can give its arrival a particular character.
-## Measure before choosing durations
+## Estimate before choosing durations
For a new or revised A-roll performance, choose time from the target's words, delivery, and action.
The reference timeline remains useful for understanding rhythm and relationships; the new performance
establishes their actual timing. Even unchanged words may take a different amount of time with a new
speaker or delivery.
-`hypit measure` is the creation-time command for `@hypit/estimate`. It counts pronunciation units and
+`hypit estimate` is the creation-time command for `@hypit/speech-estimate`. It counts pronunciation units and
estimates how many seconds they need at the chosen language and pace, using local computation:
```bash
-hypit measure path/to/source.svml --segment opening --language en --pace normal
-hypit measure --text "You expect me to type every coffee?" --language en --pace normal --rounding ceil
-hypit measure path/to/source.svml --segment opening --language zh --pace fast --rounding round
+hypit estimate path/to/source.svml --segment opening --language en --pace normal
+hypit estimate --text "You expect me to type every coffee?" --language en --pace normal --rounding ceil
+hypit estimate path/to/source.svml --segment opening --language zh --pace fast --rounding round
```
Choose `--pace slow|normal|fast` from the intended delivery: conversational explanation may suit
`normal`, while brisk, tightly cut social delivery often suits `fast`. The CLI prints the actual
units-per-second rate; `--rate` lets you choose it directly. Mandarin counts Han characters as
approximate syllables and embedded English by syllable; English counts syllables rather than words.
-Set `--language zh` for Chinese copy, including copy with English product names, and measure the
+Set `--language zh` for Chinese copy, including copy with English product names, and estimate from the
pronunciation side of Dual Text with `--segment`.
The density includes ordinary phrasing pauses. `--padding` reserves additional time for an intended
@@ -213,11 +213,11 @@ and meaningful padding with the production's direction so later Segments follow
Let that estimate inform the shape of the passage. A short line may belong with the next response,
benefit from a little fuller wording, or leave room for a meaningful action. A long passage may read
better with tighter copy or a split at a natural change of thought. Preserve the intended meaning and
-energy while finding a performable shape, then measure the affected wording again. The
+energy while finding a performable shape, then estimate the affected wording again. The
[Generated video direction](../playbooks/craft/video-direction.md#size-the-request-around-the-delivery)
applies this judgment to the selected model's request range.
-Measurement balances the intended speaking density and sizes generation; it supplies no timeline
+The estimate balances the intended speaking density and sizes generation; it supplies no timeline
anchors. Once a generated clip is accepted, normalize it, align its actual speech to its Script Segment,
construct an equal-length Timeline Window and map the alignment through that domain/Window relation. The literal duration answers how much
media to request. The aligned words answer where Caption, B-roll, MG, and Effects belong in that actual
@@ -225,7 +225,7 @@ media. Alignment measures real word positions inside that media envelope; it doe
estimated distribution of words.
For a wordless Segment, choose the requested duration from the action, music or visual rhythm.
-Speech-rate measurement has no role there; the resulting media still determines its Segment span.
+Speech-rate estimation has no role there; the resulting media still determines its Segment span.
## Bind meaning to Script identities
diff --git a/skills/hypit/references/environment/distribution.md b/skills/hypit/references/environment/distribution.md
index a6b342ce..f1d4d981 100644
--- a/skills/hypit/references/environment/distribution.md
+++ b/skills/hypit/references/environment/distribution.md
@@ -166,10 +166,10 @@ the Distribution or the environment inherited by an active Worker concerns that
Use [configuration changes](profile.md#know-when-a-change-takes-effect) before restarting it, and
preserve active work and accepted Outputs.
-Optional upstream npm tools live in the Host package home reported by `paths`, per exact package
-version, with npm's ordinary download cache. Explicit preparation may acquire these declared
-dependencies. `hypit packages install <package@version>` addresses a reported exact dependency;
-its `install.log` explains progress and failure. Installing a dependency does not start a service.
+Every npm package carries its ordinary code dependencies in its own manifest and lockfile context.
+The package manager installs them with the Distribution or project that owns the package. Runtime
+preparation is reserved for Provider-declared Programs and other runtime materials; it does not create
+a second npm installation plane.
A contributor checkout is an explicit development choice. Use one when the user has selected it;
ordinary production, project components and project Model/Provider extensions use the installed
diff --git a/skills/hypit/references/environment/local-tools.md b/skills/hypit/references/environment/local-tools.md
index ef0245d3..0955e108 100644
--- a/skills/hypit/references/environment/local-tools.md
+++ b/skills/hypit/references/environment/local-tools.md
@@ -79,7 +79,7 @@ uv --version
On Linux, use the distribution package manager or the current official installation method for the
same executables. Keep these machine tools outside the video project. `hypit paths` reports the shared
-Program and npm package homes used by selected Runtime adapters.
+Runtime and Program state locations used by selected Runtime adapters.
### Configure local media tools
@@ -91,7 +91,7 @@ actual paths into the selected Endpoint. For example, replace these illustrative
{
"endpoints": {
"media.local": {
- "use": "@hypit/provider-media-local",
+ "use": "@hypit/media-local",
"config": {
"ffmpegPath": "/opt/media/bin/ffmpeg",
"ffprobePath": "/opt/media/bin/ffprobe"
@@ -104,7 +104,7 @@ actual paths into the selected Endpoint. For example, replace these illustrative
These Provider paths resolve relative to the Runtime `dataRoot` when they are not absolute.
Use forward slashes or JSON-escaped backslashes for Windows paths. The selected media Program
probes its executables; `programs prepare` does not install system FFmpeg through a package manager.
-Hypit's local HyperFrames Provider also accepts `ffmpegPath` and `ffprobePath`: configure that
+Hypit's local HTML renderer Provider also accepts `ffmpegPath` and `ffprobePath`: configure that
Endpoint as well if it needs custom paths. Configuration does not propagate from `media.local`
to an unrelated Endpoint.
@@ -156,15 +156,15 @@ entry point by hand. Contributor/operator commands in a service README are for d
packaged service, not for creating a second project-local installation.
Other tools keep their own entry points. [Video downloading](../production/video-downloads.md)
-uses explicit `hypit media prepare-fetch` followed by `media fetch`, without a Runtime Profile or
+uses explicit `hypit download prepare` followed by `hypit download`, without a Runtime Profile or
Build. [Image operations](../production/image-operations.md) can use the local OpenCV Provider;
its README owns the managed Python environment and optional `pythonExecutable` selection. These
tools follow the same separation of preparation and use without inventing a Profile for every utility.
## Prepare the local rendering browser
-The selected HyperFrames Provider owns the browser used for rendering. Read the installed
-`@hypit/provider-hyperframes-local` README for the configuration supported by that installation;
+The selected HTML renderer Provider owns the browser used for rendering. Read the installed
+`@hypit/provider-html-local` README for the configuration supported by that installation;
a newer Skill does not add options to an older executable. [Distribution updates](distribution.md#check-and-update-the-relevant-installation)
explains how to check and update the relevant installation when a needed option is absent.
@@ -183,8 +183,8 @@ The normal declaration needs no browser version copied into every project:
```json
{
"endpoints": {
- "hyperframes.local": {
- "use": "@hypit/provider-hyperframes-local"
+ "html.local": {
+ "use": "@hypit/provider-html-local"
}
}
}
@@ -341,7 +341,7 @@ Mirrors address particular download clients and hosts:
| Python runtime | uv's `UV_PYTHON_INSTALL_MIRROR` selects a compatible Python-distribution mirror. A PyPI mirror does not supply Python itself. An already compatible installed Python may avoid this download. |
| Hugging Face weights | `HF_ENDPOINT` selects a compatible Hub endpoint; `HF_HOME` / `HF_HUB_CACHE` select reusable cache locations. A model's redirected weight host and its language-alignment download must also be reachable. |
| NLTK sentence data | If preparation reports `NLTK_ALLOW_PROXIED_URLOPEN`, the downloader needs an explicit trust decision for the configured proxy. For a trusted proxy, set that native variable to `1` only on the preparation command; do not switch it on automatically or change inference. |
-| HyperFrames browser | The selected Provider owns the archive source; follow [browser preparation](#prepare-the-local-rendering-browser) and its installed README. |
+| HTML renderer browser | The selected Provider owns the archive source; follow [browser preparation](#prepare-the-local-rendering-browser) and its installed README. |
| FFmpeg and other binaries | Use the selected package manager's binary-download settings or a compatible official prebuilt installation. An npm/PyPI mirror does not generally redirect these downloads. Homebrew bottles and GitHub release assets have their own sources. |
Make a route change explicit: explain the blocked download, the proposed source and which command
@@ -393,10 +393,9 @@ metadata successfully may still redirect large files to another host; diagnose t
## Repair from the narrowest evidence
- A missing executable belongs to host installation and `PATH`.
-- A package dependency declared by a selected adapter belongs to scoped `programs prepare` /
- `programs up`; `runtime up` also starts the Worker. A separately reported exact optional npm
- dependency uses `hypit packages install <package@version>`, as explained in
- [Distribution](distribution.md).
+- An npm dependency declared by a selected adapter belongs to the package manager and lockfile of
+ the Distribution or project that installed that adapter. `programs prepare` / `programs up` prepare
+ only Provider-declared runtime materials; `runtime up` also starts the Worker.
- A down or mismatched Managed Program belongs to its Provider configuration, Program status, and
service log.
- A healthy local Program with a rejected request belongs to the Provider's support or request error,
diff --git a/skills/hypit/references/environment/model-and-provider.md b/skills/hypit/references/environment/model-and-provider.md
index c4ae335c..ec5a3bba 100644
--- a/skills/hypit/references/environment/model-and-provider.md
+++ b/skills/hypit/references/environment/model-and-provider.md
@@ -84,14 +84,14 @@ retain the chosen settings or merge this fragment if HypiHub is the newly select
```json
{
"credentials": {
- "platform": { "use": "@hypit/credential-store-platform" }
+ "local": { "use": "@hypit/credential-store-local" }
},
"endpoints": {
"hypihub.default": {
"use": "@hypit/provider-hypihub",
"config": {
"baseUrl": "https://hypit.ai",
- "apiKey": { "store": "platform", "key": "hypihub.oauth" }
+ "apiKey": { "store": "local", "key": "hypihub.oauth" }
}
}
}
@@ -176,14 +176,14 @@ its Profile fragment has this shape:
```json
{
"credentials": {
- "platform": { "use": "@hypit/credential-store-platform" }
+ "local": { "use": "@hypit/credential-store-local" }
},
"endpoints": {
"videos.personal": {
"use": "@example/provider-videos",
"config": {
"baseUrl": "https://videos.example",
- "apiKey": { "store": "platform", "key": "videos.personal" }
+ "apiKey": { "store": "local", "key": "videos.personal" }
}
}
},
@@ -250,11 +250,11 @@ silently changing an author's request.
| Public import | Accurate interface owner |
| --- | --- |
-| `@hypit/hypit/model-kit` | Model ports and Producer/Need construction |
+| `@hypit/hypit/generation/model` | Model ports and Producer/Need construction |
| `@hypit/hypit/generation` | Generated-media values and request/mapping helpers |
-| `@hypit/hypit/endpoint-kit` | Execution, resources, credentials, support, receipts and capacity |
-| `@hypit/hypit/runtime-kit` | Profile activation, diagnostics and Managed Programs |
-| `@hypit/hypit/author-kit` | Author Module, Surface and Fragment declarations |
+| `@hypit/hypit/endpoint` | Execution, resources, credentials, support, receipts and capacity |
+| `@hypit/runtime-local/extension` | Profile activation, diagnostics and Managed Programs for the official local Runtime |
+| `@hypit/hypit/author`, `producer`, `admission`, `markup` | Author graphs, deterministic Producers, Type admission and Markup Surfaces respectively |
These packages' READMEs ship with the Distribution and own precise APIs. Use the selected
`@hypit/hypit` release as the extension's development dependency; ship compiled JavaScript and normal
diff --git a/skills/hypit/references/environment/profile.md b/skills/hypit/references/environment/profile.md
index 52da5fd0..4c2453b7 100644
--- a/skills/hypit/references/environment/profile.md
+++ b/skills/hypit/references/environment/profile.md
@@ -29,7 +29,7 @@ video. Keep the entries and bindings appropriate to the work and the user's chos
Use `hypit runtime use <profile>` to record an existing Profile for this project.
`--runtime <profile>` selects one for a single invocation. Commands read the project's
`.hypit/runtime` selection file; they do not guess from a familiar filename or another project's
-selection. From elsewhere, `hypit paths --workspace /path/to/project` inspects that project. The same
+selection. From elsewhere, `hypit paths --project /path/to/project` inspects that project. The same
project option applies to environment commands and Build status/control. See the
[project boundary](../creation/project-files.md#establish-the-project-boundary).
@@ -42,7 +42,7 @@ Keep these locations distinct:
| Profile file | Editable execution choices; may be shared intentionally |
| Profile `dataRoot` | Execution data, Worker state and working files; relative to the Profile's directory |
| Host state / Program Home | Machine-level prepared packages and helpers, reported by `hypit paths` |
-| Project Result repository | Finished Results and Outputs; configured separately in `hypit.results.json` |
+| Project `.hypit/results` | Finished Results and Outputs owned by this project |
The selection file and execution directory must be different paths. CLI, Studio and creation
commands address the same project context; there is no second CLI environment to initialize.
@@ -59,7 +59,7 @@ A complete minimal Profile for credential-free local media work is:
"credentials": {},
"endpoints": {
"media.local": {
- "use": "@hypit/provider-media-local"
+ "use": "@hypit/media-local"
}
},
"bindings": {}
@@ -67,7 +67,7 @@ A complete minimal Profile for credential-free local media work is:
```
This selects media processing only. It needs compatible FFmpeg and FFprobe supplied by the host;
-it does not install them, select an image model, or render HyperFrames pictures. Use it when those
+it does not install them, select an image model, or render HTML renderer pictures. Use it when those
are the actual requirements, not as a replacement for a production's existing Profile.
| Field | How to choose it |
@@ -125,14 +125,12 @@ A Profile names a Store and a key. The value stays in that Store.
| Store package | Storage and use |
| --- | --- |
-| `@hypit/credential-store-platform` | Starter policy: macOS Keychain, Windows Credential Locker, or an owner-private unencrypted file on Linux |
-| `@hypit/credential-store-os` | Explicit OS locker selection on supported platforms |
-| `@hypit/credential-store-file` | Explicit unencrypted private file storage outside the project |
+| `@hypit/credential-store-local` | Writable local credentials: macOS Keychain, Windows Credential Locker, or an owner-private file on Linux; set `backend: "file"` to choose files explicitly |
| `@hypit/credential-store-env` | Reads one named environment variable; read-only |
-The platform policy selects by operating system; it is not a sequence of stores to try.
+The local Store selects by operating system; it is not a sequence of stores to try.
A read failure never migrates a secret or falls back to another Store. Preserve an existing choice.
-The platform/file Store's default file directory is under the Host state root shown by `hypit paths`;
+The local Store's default file directory is under the Host state root shown by `hypit paths`;
its optional `config.path` chooses a private directory. Read that Store's installed README for path
and platform rules, including filesystem permissions.
@@ -144,13 +142,13 @@ For example, these are the Store declaration and credential reference used by a
```json
{
"credentials": {
- "platform": { "use": "@hypit/credential-store-platform" }
+ "local": { "use": "@hypit/credential-store-local" }
},
"endpoints": {
"hypihub.default": {
"use": "@hypit/provider-hypihub",
"config": {
- "apiKey": { "store": "platform", "key": "hypihub.oauth" }
+ "apiKey": { "store": "local", "key": "hypihub.oauth" }
}
}
}
@@ -201,7 +199,7 @@ every model. Keep secrets out of Sources, Runs, Profile JSON, command arguments,
## Set capacity at the resource it describes
-The Runtime Worker advances Builds. HyperFrames `workers` counts Chrome processes inside one
+The Runtime Worker advances Builds. HTML renderer `workers` counts Chrome processes inside one
render Need. These are different controls; there is no extra Build-wide model concurrency setting.
| Control | Responsibility |
@@ -209,16 +207,16 @@ render Need. These are different controls; there is no extra Build-wide model co
| Provider request capacity, commonly `config.defaultConcurrency` | Simultaneous Needs across Builds using the resource |
| Provider-specific model/action limits | Model quota or submit/poll/collect concurrency and rate; use that Provider's accepted fields |
| Endpoint `pool` | Shared resource identity for instances consuming the same real quota |
-| HyperFrames `workers`, `maxWorkers` | Per-render Chrome count or automatic ceiling |
-| HyperFrames `browserCapacity` | Shared Chrome budget alongside the whole-request budget |
+| HTML renderer `workers`, `maxWorkers` | Per-render Chrome count or automatic ceiling |
+| HTML renderer `browserCapacity` | Shared Chrome budget alongside the whole-request budget |
For example, merge this Endpoint entry for an intentionally chosen render budget:
```json
{
"endpoints": {
- "hyperframes.local": {
- "use": "@hypit/provider-hyperframes-local",
+ "html.local": {
+ "use": "@hypit/provider-html-local",
"pool": "local-render",
"config": {
"defaultConcurrency": 2,
@@ -231,7 +229,7 @@ For example, merge this Endpoint entry for an intentionally chosen render budget
```
Only one four-browser request fits the six-browser budget at once, even though the request limit is
-two. These numbers illustrate the relationship; choose them for the actual machine. HyperFrames
+two. These numbers illustrate the relationship; choose them for the actual machine. HTML renderer
reserves both budgets until the whole render finishes, including preparation and encoding.
It does not release capacity each time one browser closes.
diff --git a/skills/hypit/references/playbooks/craft/caption-tracking.md b/skills/hypit/references/playbooks/craft/caption-tracking.md
index b96b142f..7097b3e2 100644
--- a/skills/hypit/references/playbooks/craft/caption-tracking.md
+++ b/skills/hypit/references/playbooks/craft/caption-tracking.md
@@ -37,7 +37,7 @@ for this placement task. Use the installed tool or the provider's
[face-detection example](https://docs.cloud.google.com/video-intelligence/docs/samples/video-detect-faces)
for actual invocation and existing authorization for any paid request. Another suitable detector or
manual measurement can supply the same authored data. The stable Hypit input is the resulting
-Region Track, so detector invocation can remain an external, project-side preparation step.
+Region Evidence, so detector invocation can remain an external, project-side preparation step.
GVI's timestamped boxes are observations, not Script Roles or ready-to-use Hypit head tracks. Its
[response schema](https://docs.cloud.google.com/video-intelligence/docs/reference/rest/v1/AnnotateVideoResponse#TimestampedObject)
@@ -85,7 +85,7 @@ Caption ends or uses an authored ordinary placement. Neither a detector track no
of a listening face extends someone's speech.
[Caption presentation](../../production/caption-presentation.md) owns Style coverage and hiding.
-A Role with no region track keeps ordinary Style placement; a `null` inside an existing track hides
+A Role with no region evidence keeps ordinary Style placement; a `null` inside an existing series hides
the Cue rather than switching placement automatically. A deliberate tracked-to-ordinary change can
use explicit Caption Uses or separate Tracks with the same Script and Timeline.
@@ -102,8 +102,8 @@ heads.default {
## Connect the placement to Caption
```svml
-<import as="region" from="@hypit/region-track@1"/>
-<region:Track id="heads" within={vertical.bounds} timeline={speech.timeline}
+<import as="region" from="@hypit/region-evidence@1"/>
+<region:Evidence id="heads" within={vertical.bounds} timeline={speech.timeline}
recipe={tracking.heads.default}/>
<caption-fine:Caption id="captions" document={story.caption} timing={story-captions}
timeline={speech.timeline} within={vertical.bounds} regions={heads}>
@@ -111,11 +111,11 @@ heads.default {
</caption-fine:Caption>
```
-The Region Track series ids match Script Roles. Fine places a single-Role Cue at that region's top
+The Region Evidence series ids match Script Roles. Fine places a single-Role Cue at that region's top
center; `anchor-x: center` and `anchor-y: bottom` put the Cue above it. The Style still owns its width,
font and motion. Supplying `regions` requires every Cue on that Track to have one Script Role, even
when that particular Role uses fixed placement. Author the relevant Role Cues in Script. The
-`@hypit/region-track` and `@hypit/caption-fine` READMEs own the exact data behavior.
+`@hypit/region-evidence` and `@hypit/caption-fine` READMEs own the exact data behavior.
## Inspect the actual placement
diff --git a/skills/hypit/references/playbooks/craft/video-direction.md b/skills/hypit/references/playbooks/craft/video-direction.md
index e831989f..0f9af6d1 100644
--- a/skills/hypit/references/playbooks/craft/video-direction.md
+++ b/skills/hypit/references/playbooks/craft/video-direction.md
@@ -173,7 +173,7 @@ encoder.
## Prepare footage for subject isolation
-When the work needs a moving silhouette, choose a background-removal method that can process the
+When the work needs an isolated moving silhouette, choose a matting method that can process the
actual footage. For new generation, a continuous, evenly lit chroma backdrop can support a chosen
keying workflow. Choose a color separated from the person's hair, clothing and carried objects;
direct the visible body extent, performance and stable backdrop as facts of this recording. This
@@ -280,14 +280,14 @@ alignment remain separate facts.
## Size the request around the delivery
-Use `hypit measure` on a spoken Segment at its intended pace, including time for meaningful
-interaction, pauses and actions. [Script and time](../../creation/script-and-time.md#measure-before-choosing-durations)
+Use `hypit estimate` on a spoken Segment at its intended pace, including time for meaningful
+interaction, pauses and actions. [Script and time](../../creation/script-and-time.md#estimate-before-choosing-durations)
owns the command, rounding and the relationship between estimated duration and real aligned time.
Choose that pace from the intended performance and carry it into the voice and passage direction.
For brisk social delivery with trim cuts, `fast` is a useful starting choice; the name `normal`
does not make it the right rhythm for every piece. A shorter duration gives the words less room,
while the direction still supplies the stresses, attitude and reactions that make them engaging.
-Measurement sizes the words; emphasis, attitude and motivated reactions give their delivery character.
+The estimate sizes the words; emphasis, attitude and motivated reactions give their delivery character.
The target's delivery determines how much generated media the passage needs; the reference video's
seconds help explain its rhythm without becoming the target duration automatically.
diff --git a/skills/hypit/references/playbooks/craft/voice-and-performance.md b/skills/hypit/references/playbooks/craft/voice-and-performance.md
index ae91b79b..e053dd3a 100644
--- a/skills/hypit/references/playbooks/craft/voice-and-performance.md
+++ b/skills/hypit/references/playbooks/craft/voice-and-performance.md
@@ -64,7 +64,7 @@ their visual hierarchy, and [Spatial layout](../../production/spatial.md) owns g
## Let neighboring A-roll performances keep their time
The usual A-roll assembly places Segment performances one after another without consuming either
-side of their duration. This fits how the work is authored: `hypit measure` helps size each request so
+side of their duration. This fits how the work is authored: `hypit estimate` helps size each request so
its words, delivery and action belong naturally in that generated passage, and speaking video models
normally use the requested clip to perform the line. Asking one Take to remain silent for a synthetic
half-second handle at its beginning or end works against both that sizing and the model's performance.
@@ -212,7 +212,7 @@ other relationships.
## Give real performance real semantic time
-`../../creation/script-and-time.md` owns measurement, literal duration, and alignment. Once the
+`../../creation/script-and-time.md` owns duration estimation, literal duration, and alignment. Once the
accepted performance has semantic time, its dependent layers follow the delivery that really
happened.
diff --git a/skills/hypit/references/playbooks/craft/voice-direction.md b/skills/hypit/references/playbooks/craft/voice-direction.md
index 19b4bc4c..b5f868e7 100644
--- a/skills/hypit/references/playbooks/craft/voice-direction.md
+++ b/skills/hypit/references/playbooks/craft/voice-direction.md
@@ -94,6 +94,6 @@ the work.
[Video direction](video-direction.md#direct-the-reason-for-an-action) connects that attitude to gaze,
gesture and interaction. For independent speech, the Script and supported speech-model inputs shape
delivery. Choose time from this intended performance using
-[Script measurement](../../creation/script-and-time.md#measure-before-choosing-durations).
+[Speech-duration estimation](../../creation/script-and-time.md#estimate-before-choosing-durations).
The pace estimate sizes the passage; the voice and performance direction give it character. Fast
speech alone does not establish emphasis, changing attitude or expressive intonation.
diff --git a/skills/hypit/references/playbooks/formats/narration-led-demo.md b/skills/hypit/references/playbooks/formats/narration-led-demo.md
index 92eb48b2..b90617bc 100644
--- a/skills/hypit/references/playbooks/formats/narration-led-demo.md
+++ b/skills/hypit/references/playbooks/formats/narration-led-demo.md
@@ -62,7 +62,7 @@ When new performances are generated for someone who also appears in visible A-ro
Reference can condition both the visible performance and independent narration. The work then
changes sound-picture relationship without changing who is speaking.
-`../../creation/script-and-time.md` owns measurement and alignment. One accepted narration
+`../../creation/script-and-time.md` owns duration estimation and alignment. One accepted narration
performance can carry many picture changes; their semantic relations follow that performance without
forcing new speech seams.
diff --git a/skills/hypit/references/playbooks/formats/presenter-led-explainer.md b/skills/hypit/references/playbooks/formats/presenter-led-explainer.md
index 5252dfcd..d42ddca5 100644
--- a/skills/hypit/references/playbooks/formats/presenter-led-explainer.md
+++ b/skills/hypit/references/playbooks/formats/presenter-led-explainer.md
@@ -122,7 +122,7 @@ in its code. Independence, parameterization and cross-project reuse remain separ
Make frame evaluation describe the current state, including before and after each event. Then a
direct seek, a nearby-frame inspection and a range render can show the same designed behavior.
Derive connected motion from shared layout so moving a target also moves its pointer destination.
-[Drawing](../../production/component-visuals.md) explains the browser-program implementation.
+[Drawing](../../production/component-visuals.md) explains the html-visual implementation.
## Develop the work with visible feedback
diff --git a/skills/hypit/references/playbooks/formats/short-drama.md b/skills/hypit/references/playbooks/formats/short-drama.md
index 8d4fddfe..6d4fbe1d 100644
--- a/skills/hypit/references/playbooks/formats/short-drama.md
+++ b/skills/hypit/references/playbooks/formats/short-drama.md
@@ -16,10 +16,10 @@ can contain several people and cuts; several generated Takes can also reuse the
the passage is better produced in parts. Choose the shape that lets the intended action and exchange
remain legible.
-Measure the Script to understand speaking density, then leave the time that the intended pause,
+Estimate the Script's duration to understand speaking density, then leave the time that the intended pause,
reaction and action need. The selected video model's supported request lengths constrain what can be
-generated together without defining the story's scenes. [Script and time](../../creation/script-and-time.md#measure-before-choosing-durations)
-owns measurement, while [generated video direction](../craft/video-direction.md#size-the-request-around-the-delivery)
+generated together without defining the story's scenes. [Script and time](../../creation/script-and-time.md#estimate-before-choosing-durations)
+owns estimation, while [generated video direction](../craft/video-direction.md#size-the-request-around-the-delivery)
owns how the selected model's request range informs the performable passage.
## Establish the story's useful camera views
diff --git a/skills/hypit/references/playbooks/formats/talking-head.md b/skills/hypit/references/playbooks/formats/talking-head.md
index 824f017b..e6229ca8 100644
--- a/skills/hypit/references/playbooks/formats/talking-head.md
+++ b/skills/hypit/references/playbooks/formats/talking-head.md
@@ -65,7 +65,7 @@ See [Generated video direction](../craft/video-direction.md) for listeners, gest
## Let speech and graphics do different work
-Write natural stages in Script. For newly generated Takes, measure each Segment before choosing a
+Write natural stages in Script. For newly generated Takes, estimate each Segment before choosing a
literal generation duration. When the work retains recorded speech, its edited delivery supplies
the actual duration; [media preparation](../../production/media.md) explains how to prepare and
align it. A Segment can contain several edited shots, Caption Cue Breaks, graphic changes and
diff --git a/skills/hypit/references/production/builds.md b/skills/hypit/references/production/builds.md
index f4b51bf3..a297de83 100644
--- a/skills/hypit/references/production/builds.md
+++ b/skills/hypit/references/production/builds.md
@@ -270,9 +270,8 @@ current Run. `get` exports one named Output to one explicit destination:
- a Resource becomes one streamed file;
- a Composite becomes a directory containing `value.json` and its referenced Resources.
-The destination remains a user-facing export. The original Result stays in the project's selected
-repository. The default filesystem repository lives under the project; `hypit.results.json` may
-select another adapter such as S3 without changing these commands or the Run.
+The destination remains a user-facing export. The original Result stays in the project's
+`.hypit/results` directory on the machine running Hypit.
Give useful Results presentation metadata when it helps people and Studio find them:
@@ -286,22 +285,13 @@ The title, note, and highlights live in that Result manifest. They do not rename
or create a project-wide history index. Reuse still names the exact Build id and Output through the
Run mechanism in `authoring.md`.
-## Select the Result repository deliberately
+## Keep Results with the project
-Result storage belongs to the video project. The official default is the filesystem repository at
-`.hypit/results`. An explicit `hypit.results.json` selects an adapter with the envelope
-`format: "hypit.build-results@1"`, `use` and adapter-owned `config`. Read the installed
-`@hypit/build-result-fs` README for a custom filesystem path, or `@hypit/build-result-s3` for bucket,
-prefix, deployment options and its credential setup. `hypit.results.json` owns Result storage;
-the Runtime Profile owns execution, and the S3 adapter owns its credentials.
+Result storage belongs to the video project at `.hypit/results`. Result listing, export, history and
+Studio's finished library all read that directory. Moving or archiving completed Results is ordinary
+project/file management performed after a Build; it is not a live Runtime repository choice.
-`hypit paths` locates the project; `hypit doctor` checks its selected repository, even without a
-Runtime Profile. Result listing, export, history and Studio's finished library read that repository.
-If expected Results are absent, first check the selected project and Result repository.
-
-A submitted Build retains the repository destination captured at submission. Changing the project
-selection while it runs does not redirect its eventual Result. Use the original destination to
-find that Result; changing a selection does not migrate earlier history. Preserve any Result that
+A submitted Build retains its exact project Result directory. Preserve any Result that
still supplies a Run Candidate: exported files are optional copies, and explicit reuse may still
reference Resources in the original Result.
diff --git a/skills/hypit/references/production/caption-authoring.md b/skills/hypit/references/production/caption-authoring.md
index 09117ee9..4beb7bf7 100644
--- a/skills/hypit/references/production/caption-authoring.md
+++ b/skills/hypit/references/production/caption-authoring.md
@@ -12,9 +12,12 @@ and its fit beside the rest of the video.
## Decide what is actually new
Fine Caption already covers uniform flowing text with exact fonts, Paint, boxes, karaoke states,
-placement and motion. Different colors, Role styles, cue entrances or head tracking may only require
-Source and Recipe changes. A keyword occupying a separate oversized line, words playing different
-visual roles, or a recurring spatial relationship among speakers can justify a new family directly.
+placement and motion. A uniform treatment, or a treatment selected for a Role or Window, may only
+require Source and Recipe changes. A persistent visual role attached to selected display words does
+not: mark those words with Script attributes and let a project Caption family interpret the role.
+Never put keyword search, matching or content selection in a Recipe. A keyword occupying a separate
+oversized line, words playing different visual roles, or a recurring spatial relationship among
+speakers can justify a new family directly.
Creating that family is normal video production. Name the family for the visual relationship it
makes reusable, and name each Style for a particular treatment within it. A project can also own a
single-use caption composition when that is what the video needs.
@@ -39,8 +42,8 @@ owns that interface decision.
The output remains an ordinary VisualTrack. Its Presents can own trees of text, boxes, images and
other visual elements. When words and graphics share layout or motion, they can live in the same
-component. [Component visuals](component-visuals.md#compose-video-and-graphics-in-one-browser-program)
-also describes HTML/CSS browser programs with typed media and text children. That drawing freedom
+component. [Component visuals](component-visuals.md#compose-video-and-graphics-in-one-html-visual)
+also describes HTML/CSS HTML visuals with typed media and text children. That drawing freedom
applies to captions too: give the program the resolved caption schedule and explicit resources,
and evaluate its state at the requested frame. Keep separately useful overlays as peers.
@@ -135,7 +138,7 @@ family handles its own layouts. Each Track is independent, so multiple Tracks ca
show captions together or use complementary coverage. Mixed-family rendering, if useful, belongs
to the component that implements it.
-If this family supports spatial tracking, take an explicit Region Track and map it into the actual
+If this family supports spatial tracking, take an explicit Region Evidence and map it into the actual
composition. Define subject matching and absent-region behavior. Detection belongs to the measurement
step described in [Caption tracking](../playbooks/craft/caption-tracking.md), not to this renderer.
diff --git a/skills/hypit/references/production/component-design.md b/skills/hypit/references/production/component-design.md
index 66f32289..b8b7f580 100644
--- a/skills/hypit/references/production/component-design.md
+++ b/skills/hypit/references/production/component-design.md
@@ -213,6 +213,7 @@ adjustments the user needs, such as Caption position and color, through the exis
An empty parameter panel alone is no reason to widen the component interface.
[Companion authoring](studio-companions.md) owns those bindings.
-For an existing example, read the installed `@hypit/ranking` README and the part of its implementation
-that answers the current question. It connects semantic reveals, settled state, layout and editor
-entities. Carry the relevant relationship into the project component's own design.
+If the current project deliberately installed `@hypit/ranking`, its README is one example of
+semantic reveals, settled state, layout and editor entities. Do not assume that optional package is
+part of the Distribution or install it merely to begin a component. Carry only a relationship that
+answers the current video's need into the project component's own design.
diff --git a/skills/hypit/references/production/component-sharing.md b/skills/hypit/references/production/component-sharing.md
index 7a90fe04..2e496ab7 100644
--- a/skills/hypit/references/production/component-sharing.md
+++ b/skills/hypit/references/production/component-sharing.md
@@ -122,8 +122,8 @@ JavaScript entry. Declare third-party runtime dependencies in `dependencies`. In
an actual Source example, the public outputs, any companion or asset requirements, and the Hypit
release used to check it. Inspect the tarball contents with `npm pack --dry-run`.
-An executable Author Package develops against `@hypit/hypit/author-kit` and the relevant `@hypit/hypit/*` domain
-subpaths, with `@hypit/hypit` as a development dependency. Its release contains its own code and assets;
+An executable Author Package develops against the narrow `@hypit/hypit/author`, `producer`, `admission`
+and `markup` owners it actually needs, plus relevant domain subpaths, with `@hypit/hypit` as a development dependency. Its release contains its own code and assets;
the active Hypit Distribution supplies the framework APIs when loading it. Check the package from a
separate consumer project so local source links do not conceal omitted files or dependencies.
diff --git a/skills/hypit/references/production/component-visuals.md b/skills/hypit/references/production/component-visuals.md
index 677b9349..ad051d16 100644
--- a/skills/hypit/references/production/component-visuals.md
+++ b/skills/hypit/references/production/component-visuals.md
@@ -91,10 +91,10 @@ For an effect that transforms an image, pass that image as an explicit input to
preparation. For a local mask, own the mask and content in the same element tree. These relationships
make the required materials available both in Studio and in a render of any selected interval.
-## Compose video and graphics in one browser program
+## Compose video and graphics in one HTML visual
When a scene's video viewport and graphics share motion or layout, one component can draw them
-together. `browserProgram` from `@hypit/hypit/hyperframes` creates a `program` element's payload. Its HTML
+together. `htmlVisual` from `@hypit/hypit/html-program` creates a `program` element's payload. Its HTML
owns the local structure; CSS supplies layout, stacking, masks, filters and blending; optional
`setup(root, data)` code returns `render(localFrame)`. This function sets the complete state at that
frame synchronously. A range render may start in the middle, so compute state from the frame and authored inputs.
@@ -102,13 +102,13 @@ frame synchronously. A range render may start in the middle, so compute state fr
Prepare stable structure in `setup`: locate elements, construct geometry and retain reusable drawing
objects there. Paint static procedural textures once their resources are ready.
Let `render(localFrame)` update the state that changes with time. This supports both
-fast repeated capture and direct seeking. A program is sampled within its Present's lifetime;
+fast repeated capture and direct seeking. An HTML visual is sampled within its Present's lifetime;
outside it, the renderer may retain the boundary pose. Re-entry and repeated active seeks must
produce the complete requested state, including when an image became ready since the last call.
-Repeated browser-program instances share one document's HTML/SVG ID space even though their CSS
+Repeated `HtmlVisual` instances share one document's HTML/SVG ID space even though their CSS
is scoped. For SVG masks, gradients or filters, derive each required ID from `root.id` in `setup`
-and update its references together. The installed `@hypit/hyperframes` README owns the browser-program
+and update its references together. The installed `@hypit/html-program` README owns the `HtmlVisual`
API and resource-loading behavior.
For a depth or material effect, choose the representation that carries its visible behavior:
@@ -125,7 +125,7 @@ as peer Presents. These are ordinary composition choices within the same renderi
Use ordinary typed children for prepared video, images and exact-font text. A `{{child-id}}` slot in
the HTML places each direct child exactly once. These children retain their declared resources,
video sampling and font handling while participating in the program's HTML layout. Extra artifacts
-used by the program belong in its `artifacts` list; `hyperframesResourceUri` supplies their resource
+used by the program belong in its `artifacts` list; `htmlProgramResourceUri` supplies their resource
URLs. The rendering environment materializes those references.
For time-bearing footage, give the component ordinary normalized media, the absolute Window it needs
@@ -146,6 +146,6 @@ these independently; the Producer receives a Window and an Instant. The installe
`examples/semantic-composition/packages/responsive-explainer` shows this complete package: video
moves from full screen to a side viewport while a diagram enters, with Caption available as a peer.
-The program format belongs to the renderer package. `hypit.browser-program@1` runs in the
-HyperFrames browser; another renderer implements the formats it supports. Core still schedules
+The HTML visual format belongs to the renderer package. `hypit.html-visual@1` runs in the
+HTML renderer browser; another renderer implements the formats it supports. Core still schedules
ordinary Needs and has no knowledge of scenes, video windows or browser layout.
diff --git a/skills/hypit/references/production/examples/detail.svrun b/skills/hypit/references/production/examples/detail.svrun
index 756c2719..22a37309 100644
--- a/skills/hypit/references/production/examples/detail.svrun
+++ b/skills/hypit/references/production/examples/detail.svrun
@@ -1,4 +1,4 @@
-<?svml using="@hypit/run-markup@1"?>
+<?svml using="@hypit/markup/run@1"?>
<svrun version="1">
<author source="./production.svml"/>
<target output="detail.video"/>
diff --git a/skills/hypit/references/production/examples/look.svs b/skills/hypit/references/production/examples/look.svs
index cd3f1682..bde6cfb6 100644
--- a/skills/hypit/references/production/examples/look.svs
+++ b/skills/hypit/references/production/examples/look.svs
@@ -1,4 +1,4 @@
-<?svml using="@hypit/svs@1"?>
+<?svml using="@hypit/recipe@1"?>
<sheet version="1">
text.title { size: 54; weight: 700; stack-order: 20; }
film.main { background: #18212A; }
diff --git a/skills/hypit/references/production/examples/material.svrun b/skills/hypit/references/production/examples/material.svrun
index e62a12e7..d4e702b2 100644
--- a/skills/hypit/references/production/examples/material.svrun
+++ b/skills/hypit/references/production/examples/material.svrun
@@ -1,4 +1,4 @@
-<?svml using="@hypit/run-markup@1"?>
+<?svml using="@hypit/markup/run@1"?>
<svrun version="1">
<author source="./production.svml"/>
<target output="opening-alignment.alignment"/>
diff --git a/skills/hypit/references/production/examples/production.svml b/skills/hypit/references/production/examples/production.svml
index 1986d3ed..34e6aa9d 100644
--- a/skills/hypit/references/production/examples/production.svml
+++ b/skills/hypit/references/production/examples/production.svml
@@ -5,16 +5,16 @@
<import from="@hypit/script@1"/>
<import as="text" from="@hypit/text@1"/>
<import as="seedance" from="@hypit/seedance@1"/>
- <import as="pipeline" from="@hypit/media-pipeline@1"/>
+ <import as="mediaop" from="@hypit/media-operations@1"/>
<import as="whisperx" from="@hypit/whisperx@1"/>
<import as="semantic" from="@hypit/narrative-temporal@1"/>
<import as="media" from="@hypit/media@1"/>
<import as="time" from="@hypit/timeline-author@1"/>
<import as="space" from="@hypit/spatial@1"/>
- <import as="fonts" from="@hypit/fonts-open@1"/>
+ <import as="fonts" from="@hypit/fontsource@1"/>
<import as="typo" from="@hypit/text-fine@1"/>
<import as="film" from="@hypit/film@1"/>
- <import as="render" from="@hypit/render-hyperframes@1"/>
+ <import as="html" from="@hypit/html-video@1"/>
<import as="look" source="./look.svs"/>
<import as="kit" source="./direction.svs"/>
@@ -38,7 +38,7 @@
</text:Render>
<seedance:TextVideo id="performance" model="mini" prompt={prompt}
duration="5" aspect-ratio="9:16" generate-audio="true"/>
- <pipeline:Normalize id="performance-media" source={performance.video} clock={clock}
+ <mediaop:Normalize id="performance-media" source={performance.video} clock={clock}
video="primary-moving" audio="default" span-authority="video"/>
<whisperx:Alignment id="opening-alignment" narrative={story}
segment={story.segment.opening} media={performance-media.media}
@@ -57,7 +57,7 @@
<visual:Clip id="opening-source" media={performance-media.media} during={speech.opening} frame={full} z="10" fit="cover"/>
</visual:Track>
- <fonts:Stack id="title-font" family="inter" weight="700" style="normal" emoji="color"/>
+ <fonts:Face id="title-font" package="@fontsource-variable/inter" weight="700" style="normal"/>
<typo:Style id="title-style" recipe={look.text.title} font={title-font}>
<typo:Fill color="#F1E7D8"/>
</typo:Style>
@@ -68,7 +68,7 @@
<film:Track source={speech-sound.audio}/>
<film:Track source={proof-label.visual}/>
</film:Film>
- <render:Video id="final" composition={main.composition} timeline={speech.timeline}/>
- <render:Video id="detail" composition={main.composition} timeline={speech.timeline}
+ <html:Video id="final" composition={main.composition} timeline={speech.timeline}/>
+ <html:Video id="detail" composition={main.composition} timeline={speech.timeline}
start-frame="30" end-frame-exclusive="90"/>
</svml>
diff --git a/skills/hypit/references/production/examples/production.svrun b/skills/hypit/references/production/examples/production.svrun
index e2ebc6ca..4f981d48 100644
--- a/skills/hypit/references/production/examples/production.svrun
+++ b/skills/hypit/references/production/examples/production.svrun
@@ -1,4 +1,4 @@
-<?svml using="@hypit/run-markup@1"?>
+<?svml using="@hypit/markup/run@1"?>
<svrun version="1">
<author source="./production.svml"/>
<target output="final.video"/>
diff --git a/skills/hypit/references/production/examples/visuals.ts b/skills/hypit/references/production/examples/visuals.ts
index 9fe12241..d16a7f49 100644
--- a/skills/hypit/references/production/examples/visuals.ts
+++ b/skills/hypit/references/production/examples/visuals.ts
@@ -2,7 +2,7 @@ import { sealVisualTrack } from "@hypit/hypit/composition";
import type { FrameSpan } from "@hypit/hypit/composition";
import type { FontArtifactRef } from "@hypit/hypit/media";
import type { Timeline } from "@hypit/hypit/timeline";
-import { VISUAL_IR_V1 } from "@hypit/hypit/visual-ir";
+import { VISUAL_IR_V1 } from "@hypit/hypit/composition";
// The caller supplies its projected Window, resolved Frame and selected font faces.
export function renderCard(input: {
diff --git a/skills/hypit/references/production/fonts-and-text.md b/skills/hypit/references/production/fonts-and-text.md
index b29e96ba..bf494329 100644
--- a/skills/hypit/references/production/fonts-and-text.md
+++ b/skills/hypit/references/production/fonts-and-text.md
@@ -11,25 +11,27 @@ the wording, placement and lifetime. Changing one of these can preserve the othe
## Select a face or a fallback stack
```svml
-<import as="fonts" from="@hypit/fonts-open@1"/>
-
-<fonts:Face id="headline-font" family="archivo-black" weight="400" style="normal"/>
-<fonts:Stack id="body-font" family="inter" weight="700" style="normal" emoji="color">
- <fonts:Fallback family="noto-sans-sc" weight="700" style="normal"/>
-</fonts:Stack>
+<import as="fonts" from="@hypit/fontsource@1"/>
+<import as="media" from="@hypit/media@1"/>
+
+<fonts:Face id="headline-font" package="@fontsource/archivo-black" weight="400" style="normal"/>
+<fonts:Face id="body-latin" package="@fontsource-variable/inter" weight="700" style="normal"/>
+<fonts:Face id="body-han" package="@fontsource-variable/noto-sans-sc" weight="700" style="normal"/>
+<media:FontStack id="body-font" primary={body-latin}>
+ <media:Fallback font={body-han}/>
+</media:FontStack>
```
-The Face is one exact font resource. Stack preserves an ordered set: here Inter, Noto Sans SC,
-then a color Emoji face. Choose fallback faces for the actual writing systems in the video.
-Weight and style must exist in the chosen family. `hypit vocabulary @hypit/fonts-open` and that
-package's README describe the installed catalog and supported combinations.
+Each Face is one exact font resource. FontStack preserves an ordered set: here Inter followed by
+Noto Sans SC. Choose fallback faces for the actual writing systems in the video. Weight and style
+must exist in the selected, project-installed package. The project's `package.json` and lockfile,
+not a Hypit catalog, determine which families and versions exist.
-For Chinese-led speech, start with a face made for the intended script: the installed catalog
-includes `noto-sans-sc` and `noto-serif-sc` for Simplified Chinese, `noto-sans-tc` and `noto-serif-tc`
-for Traditional Chinese, and display faces such as `zcool-kuaile`. Choose their character to suit the
-piece. A compact, clear face is useful for running speech; an expressive display face can suit a
-playful caption or a short title. Inspect the real words at delivery size, including punctuation,
-numbers and any Latin names.
+For Chinese-led speech, start with a face made for the intended script. Fontsource publishes Noto
+families for Simplified and Traditional Chinese as independent packages, alongside more expressive
+display families. Choose their character to suit the piece. A compact, clear face is useful for
+running speech; an expressive display face can suit a playful caption or a short title. Inspect the
+real words at delivery size, including punctuation, numbers and any Latin names.
Fallback order also directs the design. Inter first with Noto Sans SC after it gives Latin letters
Inter's shapes and Chinese Noto's. A Chinese face first can supply both scripts for a more unified
@@ -45,7 +47,7 @@ machine. For example, a project can use a local brand face alongside an explicit
```svml
<import as="asset" from="@hypit/media@1"/>
<asset:Font id="brand-font" src="./assets/fonts/brand-semibold.woff2" weight="600" style="normal"/>
-<fonts:Face id="chinese-font" family="noto-sans-sc" weight="600" style="normal"/>
+<fonts:Face id="chinese-font" package="@fontsource-variable/noto-sans-sc" weight="600" style="normal"/>
<caption-fine:Style id="caption-style" recipe={look.caption.primary} font={brand-font}>
<caption-fine:Fallback font={chinese-font}/>
@@ -66,7 +68,7 @@ face, or export it with a font tool when permitted, before declaring it.
## Find a face when the available choices do not fit
-Start with the user's brand assets and the relevant local or bundled faces. If the work calls for
+Start with the user's brand assets and the relevant project-installed or local faces. If the work calls for
another face, look at the foundry's or an open-font project's official specimen and download. Check
the actual script coverage, available weight/style and intended use, then bring the chosen file into
the project. Keep its source and license with it, especially when sharing the editable project.
@@ -78,9 +80,9 @@ English font-size, spacing or outline recipe suit Chinese text.
## Emoji presentation
-`emoji="color"` adds a color face; `emoji="mono"` chooses monochrome. Some symbols have both text
-and Emoji presentation. Write the intended Unicode sequence, such as `☎️`, when its color form is
-wanted.
+Emoji fonts follow the same rule: install or supply the exact face, then place it explicitly in a
+`media:FontStack`. Some symbols have both text and Emoji presentation. Write the intended Unicode
+sequence, such as `☎️`, when its Emoji form is wanted.
## Give independent text its own placement and lifetime
diff --git a/skills/hypit/references/production/image-operations.md b/skills/hypit/references/production/image-operations.md
index d079b712..2fbee11c 100644
--- a/skills/hypit/references/production/image-operations.md
+++ b/skills/hypit/references/production/image-operations.md
@@ -1,7 +1,7 @@
# Preparing generated images
-Read this when a generated or supplied image needs to be combined, corrected, resized, cropped, or
-cut out before it becomes a model reference or a Track item. [Image direction](../playbooks/craft/image-direction.md)
+Read this when a generated or supplied image needs to be combined, corrected, resized or cropped
+before it becomes a model reference or a Track item. [Image direction](../playbooks/craft/image-direction.md)
owns what the image should communicate; [spatial layout](spatial.md) owns Canvas, Frame and fit.
An image operation publishes another ordinary image Output. The resulting image can feed Seedance,
@@ -18,7 +18,7 @@ Declare the Canvas and every rectangular destination explicitly:
```svml
<import as="space" from="@hypit/spatial@1"/>
-<import as="compose" from="@hypit/image-compose@1"/>
+<import as="image" from="@hypit/image-operations@1"/>
<space:Canvas id="comparison-canvas" width="2048" height="1024"/>
<space:Frame id="before-panel" within={comparison-canvas.bounds}
@@ -26,10 +26,10 @@ Declare the Canvas and every rectangular destination explicitly:
<space:Frame id="after-panel" within={comparison-canvas.bounds}
left="50%" top="0%" right="100%" bottom="100%"/>
-<compose:Image id="comparison" canvas={comparison-canvas.canvas} background="#EEEAE2FF">
- <compose:Layer source={before.image} frame={before-panel} fit="contain"/>
- <compose:Layer source={after.image} frame={after-panel} fit="contain"/>
-</compose:Image>
+<image:Compose id="comparison" canvas={comparison-canvas.canvas} background="#EEEAE2FF">
+ <image:Layer source={before.image} frame={before-panel} fit="contain"/>
+ <image:Layer source={after.image} frame={after-panel} fit="contain"/>
+</image:Compose>
```
Child order is paint order. Each Layer keeps the source image, destination Frame, fit and optional
@@ -47,7 +47,7 @@ must remain independently timed, clipped, moved or revised in the video, keep th
Image Transform separates the ordered correction choices from the image they act on:
```svml
-<import as="image" from="@hypit/image-transform@1"/>
+<import as="image" from="@hypit/image-operations@1"/>
<image:Program id="delivery-crop">
<image:Crop x="0" y="0" width="1080" height="1920" unit="pixel"/>
@@ -60,37 +60,13 @@ Image Transform separates the ordered correction choices from the image they act
Operations run in written order. A Program is authored data and produces no pixels until a
Transform applies it. Crop, resize, rotate, flip, denoise, color, sharpen, blur, alpha handling and
-encoding are available; use `hypit vocabulary @hypit/image-transform --tag Program` for their
+encoding are available; use `hypit vocabulary @hypit/image-operations --tag Program` for their
installed fields and limits. `{prepared-shot.image}` is the transformed image.
Use correction to express a known production choice. A prompt problem remains owned by the image
direction and its Prompt Kit; a different composition remains owned by the shot or reference
relationship.
-## Remove a background
-
-Use Background Removal when the next composition needs a still subject without its original field:
-
-```svml
-<import as="remove" from="@hypit/background-removal@1"/>
-
-<remove:Background id="presenter-cutout" source={portrait.image}/>
-```
-
-`{presenter-cutout.image}` is an image with transparency, ready for a Visual Clip, image composition,
-or another compatible consumer. The Runtime Profile chooses the Endpoint that performs the removal;
-the Source records only the requested visual relationship.
-
-The installed `@hypit/background-removal` operation accepts one image and returns one image.
-Its package README names the implemented Provider binding; `hypit plan` with the selected Runtime
-checks which Endpoint will serve this Source. A service advertising background removal still needs
-a matching Provider capability in the installed Distribution.
-
-For a speaking video cutout, the moving silhouette must be removed across the clip. This image
-operation supplies neither video matting nor a moving mask. [Moving-media preparation](media.md#keep-original-and-processed-material-explicit)
-explains video matting, operation order, retained originals and the processed picture's subsequent use.
-[Spatial layout](spatial.md#shape-the-outer-frame) owns geometric clips such as circular insets.
-
## Keep operation and presentation distinct
Composing or correcting image bytes changes the reusable image itself. A Visual Clip instead places
diff --git a/skills/hypit/references/production/media.md b/skills/hypit/references/production/media.md
index 4e275494..8ba49d81 100644
--- a/skills/hypit/references/production/media.md
+++ b/skills/hypit/references/production/media.md
@@ -32,7 +32,7 @@ the local domain with an equal-length Timeline Window. Neither operation changes
## Files and generated Outputs
-File declarations publish a **BlobArtifact**, a reference to the file's bytes, under their own id:
+File declarations publish a **Blob**, a reference to the file's bytes, under their own id:
```svml
<import as="asset" from="@hypit/media@1"/>
@@ -42,7 +42,7 @@ File declarations publish a **BlobArtifact**, a reference to the file's bytes, u
<asset:Audio id="music" src="./assets/music.wav"/>
```
-Use `{product}`, `{performance}` and `{music}` as inputs that accept these BlobArtifacts. A model
+Use `{product}`, `{performance}` and `{music}` as inputs that accept these Blobs. A model
Surface can publish the same kind of value under an output path, such as `{portrait.image}` or
`{opening.video}`. The package vocabulary gives that path. File paths are relative to their Source;
[project setup](../creation/project-files.md#establish-the-project-boundary) explains the declared project boundaries.
@@ -82,12 +82,12 @@ so their lengths and later playback can be combined precisely.
The following excerpt prepares a performance and an independent soundtrack:
```svml
-<import as="pipeline" from="@hypit/media-pipeline@1"/>
+<import as="mediaop" from="@hypit/media-operations@1"/>
<time:Clock id="clock" frame-rate="30"/>
-<pipeline:Normalize id="performance-media" source={performance} clock={clock}
+<mediaop:Normalize id="performance-media" source={performance} clock={clock}
video="primary-moving" audio="default" span-authority="video"/>
-<pipeline:Normalize id="music-media" source={music} clock={clock}
+<mediaop:Normalize id="music-media" source={music} clock={clock}
video="none" audio="default" span-authority="audio"/>
```
@@ -100,7 +100,7 @@ across Takes that will join one program.
`primary-moving` excludes attached cover art. The default audio selection uses the default or
unambiguous audio stream; select an explicit stream when the container has several intended choices.
-`hypit vocabulary @hypit/media-pipeline --tag Normalize` gives the supported selectors.
+`hypit vocabulary @hypit/media-operations --tag Normalize` gives the supported selectors.
Normalization inspects the bytes and produces `{performance-media.media}`: a SynchronizedMedia value
with an exact local frame count, optional picture and optional audio on the chosen Clock. Audio is
@@ -151,14 +151,14 @@ A still B-roll Clip already occupies an authored Window. To make one or several
time-bearing clip, use StillVideo:
```svml
-<import as="media" from="@hypit/media-pipeline@1"/>
+<import as="mediaop" from="@hypit/media-operations@1"/>
-<media:StillVideo id="opening-still" source={product} duration="6" clock={clock}/>
-<pipeline:Normalize id="opening-media" source={opening-still.video}
+<mediaop:StillVideo id="opening-still" source={product} duration="6s" clock={clock}/>
+<mediaop:Normalize id="opening-media" source={opening-still.video}
video="primary-moving" audio="none" span-authority="video" clock={clock}/>
```
-StillVideo produces a video-only BlobArtifact. Multiple `media:Still` children divide the authored
+StillVideo produces a video-only Blob. Multiple `media:Still` children divide the authored
duration by their optional weights. Normalization then makes that clip usable as prepared moving
media. Choose it when one or more held images need to become a time-bearing video Artifact; its role
is assigned by the downstream Source relationships just like any other video.
@@ -166,24 +166,24 @@ is assigned by the downstream Source relationships just like any other video.
## Edit bytes at an explicit point in the graph
```svml
-<media:Transform id="edited" source={performance-media.media}>
- <media:Trim tail="0.25s"/>
- <media:Retime rate="1.05"/>
-</media:Transform>
-<media:ExtractAudio id="voice-reference" source={edited.video} audio="default"/>
-<media:ExtractFrame id="frame-reference" source={edited.video}
+<mediaop:Transform id="edited" source={performance-media.media}>
+ <mediaop:Trim tail="0.25s"/>
+ <mediaop:Retime rate="1.05"/>
+</mediaop:Transform>
+<mediaop:ExtractAudio id="voice-reference" source={edited.video} audio="default"/>
+<mediaop:ExtractFrame id="frame-reference" source={edited.video}
video="primary-moving" at="last"/>
```
-Transform applies its operations in order. These Outputs are BlobArtifacts; normalize an edited
+Transform applies its operations in order. These Outputs are Blobs; normalize an edited
clip again when feeding it into a prepared-media input, and realign the edited performance when its
timing changed. Extracted audio or a frame can directly feed a compatible model reference port.
`ExtractFrame` also accepts `first`, `frame:<index>` and `time:<seconds>`.
Use graph operations for repeatable preparation belonging to the production. `hypit media` commands
-are useful for inspection and deliberately exported evidence. Image geometry changes, compositing
-and cutouts have separate installed vocabulary in `@hypit/image-transform`, `@hypit/image-compose`
-and `@hypit/background-removal`; select the operation that matches the asset's intended use.
+are useful for inspection and deliberately exported evidence. Image geometry changes and compositing
+have one installed vocabulary in `@hypit/image-operations`; select
+the operation that matches the asset's intended use.
## Keep original and processed material explicit
@@ -202,8 +202,8 @@ For a moving portrait, the installed `@hypit/volcengine-matting` package exposes
transparent formats and current Provider support. Existing transparent material can enter Normalize
directly. Removing a still reference's background does not establish transparency in generated video.
-Choose an operation for the material it actually accepts: [image background removal](image-operations.md#remove-a-background)
-produces a still cutout; a moving silhouette needs a video matte or suitable keying operation.
+Choose an operation for the material it actually accepts: a moving silhouette needs a video matte
+or suitable keying operation; deterministic Image Operations do not silently turn it into one.
[Video direction](../playbooks/craft/video-direction.md#prepare-footage-for-subject-isolation) explains
preparing and judging footage for that use. A fixed flattened arrangement of still images can use
[Image Compose](image-operations.md#flatten-a-fixed-still-image-arrangement) when that is the desired output.
diff --git a/skills/hypit/references/production/prompt-kits.md b/skills/hypit/references/production/prompt-kits.md
index 2c57c513..15986f6e 100644
--- a/skills/hypit/references/production/prompt-kits.md
+++ b/skills/hypit/references/production/prompt-kits.md
@@ -138,7 +138,7 @@ produced elsewhere remains a graph edge rather than being copied into a scalar b
Save the template above as `phone-shot.svs`. For this example, `look.svs` can be:
```svs
-<?svml using="@hypit/svs@1"?>
+<?svml using="@hypit/recipe@1"?>
<sheet version="1">
prompt.main { camera: handheld; }
</sheet>
diff --git a/skills/hypit/references/production/rendering.md b/skills/hypit/references/production/rendering.md
index effcd0c7..122e852d 100644
--- a/skills/hypit/references/production/rendering.md
+++ b/skills/hypit/references/production/rendering.md
@@ -14,7 +14,7 @@ With the named inputs already declared:
```svml
<import as="film" from="@hypit/film@1"/>
-<import as="render" from="@hypit/render-hyperframes@1"/>
+<import as="html" from="@hypit/html-video@1"/>
<film:Film id="main" canvas={canvas.canvas} timeline={speech.timeline}
appearance={look.film.main}>
@@ -24,7 +24,7 @@ With the named inputs already declared:
<film:Track source={captions.visual}/>
<film:Track source={music.audio}/>
</film:Film>
-<render:Video id="final" composition={main.composition} timeline={speech.timeline}/>
+<html:Video id="final" composition={main.composition} timeline={speech.timeline}/>
```
An example Film Recipe is `film.main { background: #18212A; }`. Canvas supplies the picture dimensions;
@@ -60,7 +60,7 @@ explicit end and pass it to the components, Film and Render:
<film:Film id="main" canvas={canvas.canvas} timeline={animation.timeline} appearance={look.film.main}>
<film:Track source={conversation.visual}/>
</film:Film>
-<render:Video id="final" composition={main.composition} timeline={animation.timeline}/>
+<html:Video id="final" composition={main.composition} timeline={animation.timeline}/>
```
The example assumes the Canvas, font, Film Recipe and project package are declared. Timeline's `end`
@@ -78,7 +78,7 @@ code-only composition, including scrolling and arbitrary message arrivals.
## Choose a render interval in frames
```svml
-<render:Video id="detail" composition={main.composition} timeline={speech.timeline}
+<html:Video id="detail" composition={main.composition} timeline={speech.timeline}
start-frame="240" end-frame-exclusive="360"/>
```
@@ -99,7 +99,7 @@ explains choosing the reuse boundary.
## Execution and capacity
-HyperFrames compiles the selected composition and renders its picture. Timeline audio is rendered
+The HTML program compiler lowers the selected Composition, and the selected rasterization Provider produces its picture. Timeline audio is prepared
from the included AudioTracks, then picture and sound are muxed into the delivered file. A Runtime
can bind these capabilities to different compatible Endpoints.
@@ -107,8 +107,8 @@ Before the first local render, or when browser startup reports a missing executa
[browser preparation](../environment/local-tools.md#prepare-the-local-rendering-browser).
That selected Provider owns browser installation and download configuration.
-The local HyperFrames Provider supports range requests and can capture different parts of one
-render with several browser workers. Browser selection, download settings and worker capacity
+The local HTML Provider supports range requests and can capture different parts of one
+program with several browser workers. Browser selection, download settings and worker capacity
belong to that Provider's Profile configuration. [Runtime profiles](../environment/profile.md)
and the selected Provider's README own those choices; the Source retains the same render declaration.
Another Provider declares the request forms its deployment supports.
@@ -119,7 +119,7 @@ preparation and final encoding contribute separately. Reusing media through the
not preserve a previous render's temporary preparation.
For a local composition change, use [snapshot](snapshots.md) first to inspect the changed
-relationship and its handoffs in the current Studio programme. Keep accepted material selected in
+relationship and its handoffs in Studio's current `HtmlProgram`. Keep accepted material selected in
the Run. Range rendering supplies an encoded clip when that is needed; render the complete
deliverable when the composition is ready.
While rendering, communicate the current phase and meaningful progress. The Provider reports
diff --git a/skills/hypit/references/production/review.md b/skills/hypit/references/production/review.md
index 17137fb6..0e860790 100644
--- a/skills/hypit/references/production/review.md
+++ b/skills/hypit/references/production/review.md
@@ -78,7 +78,7 @@ location remains an open question.
Use whichever view can answer the current question:
-- Once frame positions are known, use [snapshot](snapshots.md) to inspect the existing programme
+- Once frame positions are known, use [snapshot](snapshots.md) to inspect the existing `HtmlProgram`
directly. Select individual states or continuous frames; keep the surrounding handoffs visible.
The locations can come from semantic events, the playhead or authored clock time.
- On an encoded Result, focused media operations such as frames, cut, and tile can expose exact
diff --git a/skills/hypit/references/production/runs.md b/skills/hypit/references/production/runs.md
index a9a22649..d8e0b839 100644
--- a/skills/hypit/references/production/runs.md
+++ b/skills/hypit/references/production/runs.md
@@ -16,7 +16,7 @@ One Run uses these author-facing declarations:
| Declaration | Role |
| --- | --- |
| `<author source="./main.svml"/>` | Select the Run's one Author entry. |
-| `<import as="media" from="@hypit/media-pipeline@1"/>` | Make one installed Run Fragment library available. |
+| `<import as="media" from="@hypit/media-operations@1"/>` | Make one installed Run Fragment library available. |
| `<target output="final.video"/>` | Demand one public Author Output; several Targets may be declared. |
| `<file .../>` | Admit one project file as a typed zero-input Candidate. |
| `<build-record .../>` | Admit one exact public Output from one earlier Build Result. |
@@ -31,7 +31,7 @@ not Run declarations.
## Select the Output that the current work needs
```svrun
-<?svml using="@hypit/run-markup@1"?>
+<?svml using="@hypit/markup/run@1"?>
<svrun version="1">
<author source="./production.svml"/>
<target output="final.video"/>
@@ -60,7 +60,7 @@ The selected graph includes the dependencies needed to complete those Outputs.
A file can replace a byte-producing Output:
```svrun
-<file id="supplied-performance" type="@hypit/artifact@1#BlobArtifact"
+<file id="supplied-performance" type="@hypit/blob@1#Blob"
from="./assets/performance.mp4" media-type="video/mp4"/>
<satisfy output="performance.video" candidate="supplied-performance"/>
```
@@ -73,10 +73,10 @@ matches what should stay; the receiving Type identifies which kind of value fits
## Use a Fragment when a Candidate needs computation
A Run Fragment connects computations that produce a Candidate. For example, an authored still image
-can become a timed video through Media Pipeline's ordinary `still-video` Fragment:
+can become a timed video through Media Operations's ordinary `still-video` Fragment:
```svrun
-<import as="media" from="@hypit/media-pipeline@1"/>
+<import as="media" from="@hypit/media-operations@1"/>
<fragment id="product-hold" using="media:still-video">
<input name="duration" value="5"/>
<input name="clock" from="clock"/>
@@ -86,7 +86,7 @@ can become a timed video through Media Pipeline's ordinary `still-video` Fragmen
<satisfy output="product-clip.video" candidate="product-hold.video"/>
```
-Here `product-layout` is an Author value of Type `@hypit/media-pipeline@1#StillVideoLayout`,
+Here `product-layout` is an Author value of Type `@hypit/media-operations@1#StillVideoLayout`,
containing `{"weights":[1]}`; `product-image` is an authored image Blob. The package README owns the
Fragment's exact inputs. [Media](media.md#give-a-still-a-duration-when-that-is-its-role) shows the
simpler `StillVideo` Surface for authoring this directly in the Source.
diff --git a/skills/hypit/references/production/script-syntax.md b/skills/hypit/references/production/script-syntax.md
index 5012c712..6d4c41be 100644
--- a/skills/hypit/references/production/script-syntax.md
+++ b/skills/hypit/references/production/script-syntax.md
@@ -148,7 +148,7 @@ One Script publishes the full Narrative and the narrow views needed by the rest
| `{story}` | The complete authored Narrative. |
| `{story.segment.hook}` | The `hook` Segment as a NarrativeSegmentRef for generation, alignment or another semantic consumer. |
| `{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.segment.hook.speech}` | Pronunciation-only Text, suitable for `hypit estimate` 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. |
diff --git a/skills/hypit/references/production/snapshots.md b/skills/hypit/references/production/snapshots.md
index b3af50b2..b500b5ab 100644
--- a/skills/hypit/references/production/snapshots.md
+++ b/skills/hypit/references/production/snapshots.md
@@ -2,7 +2,7 @@
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
+Profile's `rasterize-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
@@ -21,28 +21,28 @@ hypit snapshot --studio http://localhost:5191 \
--grid 4x3 --cell 480 --to evidence/comparison-motion
```
-Use the address of the existing Studio session and frames located in that programme. The examples
+Use the address of the existing Studio session and frames located in its current `HtmlProgram`. 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.
+Studio supplies its already compiled `HtmlProgram` 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.
+inside a component's HTML visual. The command sends one immediate request, keeping the original
+`HtmlProgram` 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;
+Use `--runtime <profile>` and `--project <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:
+`@hypit/html-program@1#rasterize-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 frame. Frame indices start at zero on that `HtmlProgram` 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.
@@ -55,7 +55,7 @@ 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:
+An already materialized HTML renderer HTML file can also be the input:
```bash
hypit snapshot ./picture/index.html --at-frame 240 --to evidence/html-detail
@@ -64,7 +64,7 @@ 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;
+inside JavaScript data and the full typed Surface input. Snapshot is an `HtmlProgram` 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
diff --git a/skills/hypit/references/production/source-syntax.md b/skills/hypit/references/production/source-syntax.md
index 058a2d0f..d352c6dd 100644
--- a/skills/hypit/references/production/source-syntax.md
+++ b/skills/hypit/references/production/source-syntax.md
@@ -81,7 +81,7 @@ inside its raw body, as described in [Script syntax](script-syntax.md).
## Recipes are named values
```svs
-<?svml using="@hypit/svs@1"?>
+<?svml using="@hypit/recipe@1"?>
<sheet version="1">
media.cover {
fit: cover;
@@ -145,7 +145,7 @@ axes can be added when they express reusable direction; `@hypit/text` owns that
For the Text example saved as `main.svml`, beside `direction.svs`:
```svml
-<?svml using="@hypit/run-markup@1"?>
+<?svml using="@hypit/markup/run@1"?>
<svrun version="1">
<author source="./main.svml"/>
<target output="prompt"/>
diff --git a/skills/hypit/references/production/spatial.md b/skills/hypit/references/production/spatial.md
index 9ddb97e6..0081cbc2 100644
--- a/skills/hypit/references/production/spatial.md
+++ b/skills/hypit/references/production/spatial.md
@@ -186,14 +186,14 @@ Frame. Choose the crop and motion together for the intended coverage.
[Visual Track](visual-clips.md) places explicit footage through Clips. A scene that
coordinates the viewport with surrounding graphics can own the shared motion in its
-[component program](component-visuals.md#compose-video-and-graphics-in-one-browser-program).
+[component program](component-visuals.md#compose-video-and-graphics-in-one-html-visual).
[Visual Track](visual-clips.md) owns its content and source-time inputs. Read its installed
vocabulary for complete appearance and motion fields.
-## Carry measured regions through an explicit peer track
+## Carry measured regions through explicit peer evidence
-Region Track contains already prepared boxes indexed by Timeline Frame. It is not part of static
+Region Evidence contains already prepared boxes indexed by Timeline Frame. It is not part of static
Spatial geometry. Its Recipe uses normalized `[x, y, width, height]` boxes and `null` for absent
measurements, resolved inside an explicit Frame. Source-local measurements need their actual time
placement and the source-to-picture mapping produced by the real presentation before they can
diff --git a/skills/hypit/references/production/studio-companions.md b/skills/hypit/references/production/studio-companions.md
index 46919c13..815d4376 100644
--- a/skills/hypit/references/production/studio-companions.md
+++ b/skills/hypit/references/production/studio-companions.md
@@ -128,7 +128,7 @@ retains an authored unit; it does not convert percentages to pixels.
A Style can own its controls independently of the Track that consumes it. The Track declares
`{ name: "style", companion: true }`; the Style's package contributes
-`createStudioCompanionHostFacet({ parameters: [{ id, match: { module, surface }, bindings, inspector }] })`.
+`createStudioCompanionFacet({ parameters: [{ id, match: { module, surface }, bindings, inspector }] })`.
Its field names are local to that Style. Studio follows the reference and combines those fields
with the Use's time controls. This works for a new project motion Style as well as a familiar
framed presentation. Shared Style edits continue to affect its other Uses.
@@ -166,19 +166,20 @@ all through normal compilation. A separate offset remains a separate local decis
## Load it with the project package
Keep the Companion separate from the component's Producers. External packages import
-`@hypit/hypit/studio-adapter` and relevant public `@hypit/hypit/*` APIs, with the Distribution as a
-development dependency. Add `createStudioTrackCompanionHostFacet(companions)` to the existing
-activation's `hostFacets`, retaining its author and producer contributions. Ship the compiled
+`@hypit/hypit/studio-companion` and relevant public `@hypit/hypit/*` APIs, with the Distribution as a
+development dependency. Add `createStudioTrackCompanionFacet(companions)` to the existing
+activation's `facets`, retaining its author and producer contributions. Ship the compiled
Companion through the package's normal activation entry.
The Source-selected package activates its Companion. Restart Studio after changing package code
or activation. Ordinary Source and Recipe edits recompile within the current session.
-Use the installed `packages/studio-adapter/README.md` for the complete minimal Companion and
-activation example, `packages/studio/INSPECTOR.md` for field declarations, and
-`packages/temporal-markup/EDITING.md` for exact time-form behavior. These are package references
-inside the installed Distribution. Ranking, Caption Fine and Visual Track Companions demonstrate
-persistent events, Cue content with Style Uses, and ordinary visual Clip occurrences respectively.
+Use the installed `@hypit/studio-companion` package README for the complete minimal Companion and
+activation example. The Studio and Temporal package documentation own field declarations and exact
+time-form behavior. Caption Fine and Visual Track are default examples of Cue content with Style
+Uses and ordinary visual Clip occurrences. Ranking demonstrates persistent events only when that
+optional package has been deliberately selected and installed by the project; it is not part of the
+default Distribution.
Try the component in its actual Run: select a meaningful picture part, inspect the corresponding
timeline entity, change an exposed value and inspect the owning Source and resulting picture.
diff --git a/skills/hypit/references/production/studio.md b/skills/hypit/references/production/studio.md
index 643a9f43..884831f1 100644
--- a/skills/hypit/references/production/studio.md
+++ b/skills/hypit/references/production/studio.md
@@ -27,7 +27,7 @@ different one. Reuse an existing session when it serves the intended project and
The startup output identifies the project, absolute Run path, Runtime Profile and selection source.
An explicit `--runtime` applies to this session; the project's default comes from `.hypit/runtime`.
-When launching from another directory, use `--workspace` to select the project and supply the Run
+When launching from another directory, use `--project` to select the project and supply the Run
path from the current directory, as shown in [project boundaries](../creation/project-files.md#establish-the-project-boundary).
Studio watches the Run and its loaded Author/Recipe Sources and recompiles them after changes.
@@ -112,7 +112,7 @@ pass, read the latest file. [Composition review](review.md) explains the judgmen
## Review before export
For visual inspection, use [snapshot](snapshots.md) on this session first. It reads the current
-compiled programme and selected resources, captures exact original frames, and writes PNGs with
+compiled `HtmlProgram` and selected resources, captures exact original frames, and writes PNGs with
optional grids. Studio remains the interactive view for playback, sound and editing.
@@ -159,7 +159,7 @@ include when the user wants to continue editing on another machine.
| View | What it shows and what it can change |
| --- | --- |
| Source | The exact Run, Author and imported Source/Recipe files. Select a file and use Edit source; changes save automatically, and Cmd/Ctrl+S saves immediately. Check save/error state. This is not a project filesystem browser. |
-| Preview | The selected Film composition rendered by HyperFrames in the browser. Play or seek with the transport or timeline. Selecting a component-declared visual part selects its corresponding timeline entity; adjust its exposed position in the Inspector. |
+| Preview | The selected Film composition evaluated from its compiled `HtmlProgram` in the browser. Play or seek with the transport or timeline. Selecting a component-declared visual part selects its corresponding timeline entity; adjust its exposed position in the Inspector. |
| Timeline | Semantic Segments, Selections and Moments, plus the component-projected Track entities and their visible intervals, materials or event lanes. A rectangle may describe occupancy, activation or persistent visibility; read the component's meaning. |
| Inspector | With nothing selected, project, Canvas, time and Run facts. For a selected entity, its declared read-only facts and adjustable fields, organized under Where, When and How where applicable. |
| Tasks | One card per Build, grouped into ongoing and finished. Active status and progress come from the selected Runtime; completed, failed and cancelled Builds come from project Results. Cards retain the source Run, times and any failure or attention reason. |
diff --git a/skills/hypit/references/production/track-authoring.md b/skills/hypit/references/production/track-authoring.md
index 8562c96a..f77fa526 100644
--- a/skills/hypit/references/production/track-authoring.md
+++ b/skills/hypit/references/production/track-authoring.md
@@ -58,7 +58,7 @@ This separation lets one projected Instant drive an answer reveal, a short sound
Consumers can share that one value. Changed speech moves the upstream event without asking each
component to search for a word, carry a projector or inspect the Script parser.
-Use `resolveTemporalContext` from `@hypit/hypit/temporal-markup` to resolve the component's
+Use `resolveTemporalContext` from `@hypit/hypit/temporal/markup` to resolve the component's
`timeline` input. Pass that same Timeline to its Fragment and Producers, alongside projected
Instants/Windows. A component can combine literal times and domain-produced events without switching time
models. The installed `examples/semantic-composition/packages/chat-scene` demonstrates repeated
@@ -106,7 +106,7 @@ and a material change establishes truthful local evidence.
## Make spatial decisions equally explicit
Canvas identifies the final raster viewport. SpatialFrame, anchors, extents and fitting describe
-where content goes and how its intrinsic shape occupies that place. Region Track supplies authored
+where content goes and how its intrinsic shape occupies that place. Region Evidence supplies authored
per-frame regions already resolved in the program picture plane. These are distinct from Timeline,
which owns the complete time range.
@@ -119,17 +119,17 @@ and any detector in their own execution or measurement boundary.
## Write the smallest component that expresses the role
Declare the new package in the project's `packages/` and ordinary package configuration. Read the
-installed `@hypit/hypit/author-kit` README for the public package boundary and inspect a close installed sibling for
+installed `@hypit/hypit/author`, `producer`, `admission` and `markup` READMEs for the public package boundaries and inspect a close installed sibling for
the relevant implementation, rather than depending on a monorepo example directory being present.
-`@hypit/interview-emoji-reveal` demonstrates persistent Moment-driven state; `@hypit/ranking`
-demonstrates reveal Windows and settled rows; `@hypit/visual-track` demonstrates ordinary Clip
-occurrences with independent Window, Frame, fit and source-time relations.
+When already selected by a project, `@hypit/interview-emoji-reveal` demonstrates persistent
+Moment-driven state and `@hypit/ranking` demonstrates reveal Windows and settled rows.
+`@hypit/visual-track` is the default example for ordinary Clip occurrences with independent Window,
+Frame, fit and source-time relations. Optional examples are evidence, not prerequisites.
-Ranking provides a complete example in the installed Distribution. Its `packages/ranking/README.md`
-links the relevant files: `surface.ts` projects authored time, `fragment.ts` connects typed inputs,
-`schedule.ts` computes reveal and settled spans, `render.ts` draws them, and
-`packages/ranking-studio/src/index.ts` turns the same program into editor entities. Follow the part
-that answers the current question. A new component may use fewer operations or different state.
+Ranking's repository README links its implementation: `surface.ts` projects authored time,
+`fragment.ts` connects typed inputs, `schedule.ts` computes reveal and settled spans, `render.ts`
+draws them, and `studio.ts` turns the same program into editor entities. Read it only when that
+example is relevant and available; a new project component may use fewer operations or different state.
The Surface exposes author intent and lowers absolute temporal forms through
`createTemporalWindowConstruction` or `createTemporalInstantConstruction`. The Fragment wires the
@@ -154,7 +154,7 @@ The useful pieces of a project package are:
| Surface | Validate authored attributes and children, resolve typed references, emit inert Records, Components and Fragments |
| Fragment | Wire the finite computation graph and publish outputs |
| Producer | Compute the immutable state or render program from declared inputs |
-| Activation | Register the Manifest, deterministic handlers and Markup facets with their matching Host ABI |
+| Activation | Register the Manifest, deterministic handlers and Markup facets with their matching Facet ABI |
| Vocabulary and preview | Explain the role and show a recognizable, configured example |
| Optional Studio Companion | Project meaningful editor entities, real parameter bindings and temporal lineage without changing video rendering |
@@ -173,7 +173,7 @@ or absolute expressions only. A Narrative package must publish its selected boun
Keep each child's `subjectId` meaningful for inspection while qualifying graph ids by its owning
Track, so multiple instances can coexist. Do not use it to reject a deliberately shared Window. A finite create/append/finalize graph supports any authored
number of messages or cards with ordinary fixed Producer ports. The exact helpers and vocabulary
-live in `@hypit/hypit/temporal-markup`; the `@example/chat-scene` package demonstrates authored and semantic events on one Timeline.
+live in `@hypit/hypit/temporal/markup`; the `@example/chat-scene` package demonstrates authored and semantic events on one Timeline.
A scene may publish computed event times when another component needs them, just as it publishes a
Track. This shares pre-render data. When the author already specifies a common trigger, consumers
@@ -184,7 +184,7 @@ draw nothing; inside it, each slot shows its preset/activated answer or its plac
entrance motion relative to that slot's activation frame. Deriving state directly from declared inputs
and the requested frame keeps Studio scrubbing and partial or concurrent rendering deterministic.
-Emit the public VisualTrack representation through `@hypit/hypit/composition` and `@hypit/hypit/visual-ir`.
+Emit the public VisualTrack representation through `@hypit/hypit/composition` and `@hypit/hypit/composition`.
[Component visuals](component-visuals.md) explains Presents, element trees, local animation,
prepared surfaces and a complete drawing function. [Spatial layout](spatial.md) explains incoming
Frames, and [Fonts and text](fonts-and-text.md) explains font resources.
diff --git a/skills/hypit/references/production/video-downloads.md b/skills/hypit/references/production/video-downloads.md
index 67d14216..cbc003ec 100644
--- a/skills/hypit/references/production/video-downloads.md
+++ b/skills/hypit/references/production/video-downloads.md
@@ -1,13 +1,13 @@
# Downloading a video from a link
-Read this when a reference or source clip lives on a video page. `hypit media fetch` saves the
+Read this when a reference or source clip lives on a video page. `hypit download` saves the
video as a project file through yt-dlp. For a website's interface, scroll or interaction, use
[browser capture](browser-capture.md).
## Save the source video
```bash
-hypit media fetch "https://example.com/watch?v=VIDEO_ID" \
+hypit download "https://example.com/watch?v=VIDEO_ID" \
--to references/ad/source.mp4
```
@@ -23,9 +23,9 @@ it is separate from preparing material for a production's frame clock.
## Prepare the downloader
-Run `hypit media prepare-fetch` explicitly before the first fetch. It uses uv to prepare the
+Run `hypit download prepare` explicitly before the first download. It uses uv to prepare the
Distribution's locked downloader and JavaScript solver, then reports the executable path. Reuse that
-environment for subsequent downloads. `media fetch` never installs dependencies, updates tools or
+environment for subsequent downloads. `download` never installs dependencies, updates tools or
acquires remote components; a missing environment reports the preparation command. `ffmpeg` merges separate picture and sound streams, and `ffprobe` reads the
saved file. [Local tools](../environment/local-tools.md#supply-host-executables-at-machine-scope)
covers these executables on macOS, Windows and Linux. The command runs directly, without a Runtime
@@ -33,7 +33,7 @@ Profile, model credential or Build.
Supported sites and access requirements depend on yt-dlp and the source site. A failed download
includes the downloader's error. When a site needs additional download options, the installed
-`services/yt-dlp/README.md` explains direct use of the packaged tool; the site's own download or
+`@hypit/yt-dlp/runtime/README.md` explains direct use of the packaged tool; the site's own download or
export can also supply the same local file.
## Continue from the saved file
diff --git a/skills/hypit/references/production/vocabulary.md b/skills/hypit/references/production/vocabulary.md
index 70f91da0..0126084e 100644
--- a/skills/hypit/references/production/vocabulary.md
+++ b/skills/hypit/references/production/vocabulary.md
@@ -19,7 +19,7 @@ Query the likely package owners:
```bash
hypit vocabulary
hypit vocabulary @hypit/caption-fine
-hypit vocabulary @hypit/media-pipeline --tag StillVideo
+hypit vocabulary @hypit/media-operations --tag StillVideo
hypit vocabulary --visual text
```
@@ -79,12 +79,13 @@ Keep the boundary useful:
- Runtime Profiles own external execution and credentials;
- Provider packages implement media tools and external services.
-Read the installed `@hypit/hypit/author-kit` README for the public package boundary and a relevant component
+Read the installed `@hypit/hypit/producer`, `admission`, `author` and `markup` READMEs for the public package boundaries and a relevant component
for an implementation example. Give the new package its own Module identity and use the project
-owner's scope; the selected Distribution owns the reserved `@hypit/*` namespace.
+owner's scope; `@hypit/*` is the Hypit project's publishing namespace, not a scope for project packages.
-TypeScript imports use public SDK paths such as `@hypit/hypit/author-kit`, `@hypit/hypit/composition`,
-`@hypit/hypit/text`, `@hypit/hypit/caption` or `@hypit/hypit/studio-adapter`. Source imports instead name logical Modules,
+TypeScript imports use public SDK paths such as `@hypit/hypit/author`, `@hypit/hypit/producer`,
+`@hypit/hypit/admission`, `@hypit/hypit/markup`, `@hypit/hypit/composition`,
+`@hypit/hypit/text`, `@hypit/hypit/caption` or `@hypit/hypit/studio-companion`. Source imports instead name logical Modules,
such as `@hypit/caption@1`. When learning from installed official source, translate its internal
workspace imports to the corresponding public SDK paths in the project package.
@@ -108,8 +109,9 @@ with a drawing example. [System relationships](system.md) places it in the compl
The project's package manager installs and versions components. Hypit loads only packages selected
by Source or Run imports and their declared dependencies. Project packages resolve from the project;
-reserved `@hypit/*` packages come from the selected Distribution. It does not scan the dependency
-tree for possible components.
+exact packages embedded in the selected Distribution come from that Distribution, while independently
+published packages—including `@hypit/*` packages—follow ordinary project-first package resolution.
+Hypit does not scan the dependency tree for possible components.
Keep a new component project-local while it serves this work. If its owner later wants to use it
across projects, send a versioned tarball or publish an npm/private-registry release and pin it in the