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: finish the 0.3 public documentation audit

kashorinf946760a3f94
diff --git a/CONTRIBUTING.zh-CN.md b/CONTRIBUTING.zh-CN.md
index 2a9edf6e..ae16bb2c 100644
--- a/CONTRIBUTING.zh-CN.md
+++ b/CONTRIBUTING.zh-CN.md
@@ -66,18 +66,24 @@ Hypit 状态目录,关闭 Puppeteer 隐式下载,先验证缺少浏览器的
`npm package execution` 工作流在 PR 上执行这项检查,发布流程复用它;发布的就是已经
安装并执行过的同一份 tarball。
-正式发布请走现有的 GitHub Release 工作流。把下一个稳定 npm 版本写入 `package.json` 并提交到
-`main`。打开 **Releases → Draft a new release**,选择该提交,打上标签 `v<version>`(例如
-`v0.1.8`),写好发布说明后发布 Release。带标签的提交必须包含此工作流。
-`Publish npm` 会核对标签与版本一致、且该提交属于 main 的历史,运行 Linux/Windows 检查,
-构建并检查打包后的 CLI,再以 `latest` 发布到 npm,并把 tarball 附加到这次 Release。
-检查与打包使用触发时的提交,即使随后 main 继续前进。此路径只支持稳定版,不支持预发布。
+正式发布请走现有的 GitHub 工作流。把下一个稳定 npm 版本写入 `package.json` 并提交到
+`main`,然后先在 `main` 上运行 **Actions → Publish npm → Run workflow**,填写该版本且不要勾选
+**Publish to npm**。这会在不改动 npm 的情况下,对完整且不可变的候选版本运行 Linux/Windows
+检查,并将其保留为可下载构件。这个准确提交通过后,再打开 **Releases → Draft a new release**,
+选择该提交,打上标签 `v<version>`(例如 `v0.1.8`),写好发布说明后发布 Release。带标签的提交
+必须包含此工作流。`Publish npm` 会核对标签与版本一致、且该提交属于 main 的历史,运行
+Linux/Windows 检查,构建并检查打包后的 CLI,预检发布计划中的每个包在 npm 上的状态,
+按依赖优先、根 Distribution 最后的顺序以 `latest` 发布,并把 tarball 附加到这次 Release。
+只有全部检查、包安装与 Registry 预检成功后,才会发生任何 npm 写入。检查与打包使用触发时的
+提交,即使随后 main 继续前进。此路径只支持稳定版,不支持预发布。
**Actions → Publish npm → Run workflow** 在 `main` 上仍然可用:填写已提交的版本,不勾选
-**Publish to npm** 时只运行 Linux/Windows 检查并提供可下载的 README 与 tarball;勾选后,
-在检查通过后把本次打出的 tarball 发布为 `latest`。补完一次失败的 Release 发布时,先修好
-外部问题再重跑该 Release 的工作流。若必须改代码,准备新版本和新的 Release。已经发布的
-npm 版本会被跳过且不改动 `latest`;已经附在 Release 上的文件会保留。
+**Publish to npm** 时只运行检查并提供可下载构件;勾选后则手动发布 npm。补完一次失败的 Release
+发布时,先修好外部问题再重跑该 Release 的工作流。检查或包预检失败不会消耗 npm 版本。如果候选
+版本没有任何包进入 npm,可以撤回 Release 与标签,修复代码但保留原定版本,再重新验证完整候选。
+如果独立包已经发布了一部分,重跑同一个不可变候选即可:匹配的版本会被跳过,发布按依赖顺序继续。
+只有根 Distribution 版本已经存在于 npm 后,根包代码变更才必须使用新的 patch 版本;资源上传失败等
+外部步骤仍可在原版本上重跑。已经附在 Release 上的文件会保留。
push main、只 push 标签、或保存草稿 Release 都不会发布 npm。工作流不修改版本,也不创建标签。
可见的 Release 可以早于 npm 发布成功;对外宣布该 npm 版本可用前,先看这次 Actions 的结果。
diff --git a/README.md b/README.md
index 668e62b1..eab8e51f 100644
--- a/README.md
+++ b/README.md
@@ -163,7 +163,7 @@ Your agent can check the environment, request the credentials the video needs, g
- **Clone any video:** drop in a video, get the whole workflow — footage, captions, B-roll, effects. Not a script breakdown.
- **One workflow, 100 variants:** reuse the composition and existing material; generate the parts that change.
-- **Pluggable components:** swap the host without touching the captions. Use the library, fork it, or write your own.
+- **Pluggable components:** swap the host without touching the captions. Use an installed package, adapt an example, or write your own.
- **Open source:** no Hypit seat pricing, per-render fees or added watermark. Model-service usage is billed by the service you choose.
## What Hypit Can Build
diff --git a/README.zh-CN.md b/README.zh-CN.md
index 3afc0781..a65c096d 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -162,7 +162,7 @@ Agent 会检查环境,索要这条视频需要的凭据,生成素材并构
- **真的能 Clone:** 丢一条视频进来,拿到整份 workflow —— 画面、字幕、B-roll、特效。不是拆解脚本。
- **一份 workflow,100 个变体:** 复用编排和已有素材,需要变化的部分再生成。
-- **可插拔组件:** 换主播不动字幕。用组件库、fork 一个,或自己写。
+- **可插拔组件:** 换主播不动字幕。使用已安装的包、改造一个示例,或自己编写。
- **开源:** Hypit 不按人头或渲染次数收费,也不添加水印。模型服务费用由你选择的服务方收取。
## Hypit 能构建什么
diff --git a/docs/guide/packages.md b/docs/guide/packages.md
index d93247bc..e1b39e83 100644
--- a/docs/guide/packages.md
+++ b/docs/guide/packages.md
@@ -15,7 +15,7 @@ interface and implementation; the execution system runs the resulting dependency
| Model | Defines an exact generation request and its outputs | Source imports |
| Provider Endpoint | Executes supported requests through an API or local tool | Runtime Profile |
| Credential store | Resolves the named credentials for an Endpoint | Runtime Profile |
-| Result repository | Keeps a project's Build records and produced files | Project Result configuration |
+| Result repository | Keeps a project's Build records and produced files | Runtime implementation; Local Runtime uses project `.hypit/results` |
| Distribution | Supplies the executable applications and official packages | Installed `@hypit/hypit` release |
For example, a Model describes a requested video, while a Provider maps that request to a service.
@@ -42,8 +42,9 @@ The consumer installs a chosen version and keeps its lockfile with the project.
## Installation and Source imports
The Skill, executable Distribution and video project are installed and updated separately. The
-`@hypit/hypit` Distribution includes the official author packages and public extension APIs. Its selected
-Runtime adapters can prepare their declared services and other runtime materials through
+`@hypit/hypit` Distribution embeds Core, installs product-selected default author packages as ordinary
+npm dependencies, and exposes public extension APIs. Its selected Runtime adapters can prepare their
+declared services and other runtime materials through
`hypit runtime up`. npm dependencies are installed with the package that owns them: Distribution
dependencies with the Distribution, and project component dependencies with the project.
@@ -67,5 +68,5 @@ supplies the public Hypit APIs when it loads the selected extension.
- [Models and Providers](./providers.md) explains new models, services and credentials.
- [Runtime](./runtime.md) covers Endpoint and credential configuration.
-Exact SDK types and implementation examples live with the corresponding package's README and
-source, which also ship in the Distribution.
+Exact SDK types and implementation examples live with the corresponding package README and
+repository source. An installed package supplies its public types and executable code.
diff --git a/docs/guide/providers.md b/docs/guide/providers.md
index 90a26726..d293cf04 100644
--- a/docs/guide/providers.md
+++ b/docs/guide/providers.md
@@ -8,10 +8,11 @@ A **Provider** knows how to fulfill that request through a particular service. A
configured instance of that Provider, with its service address, credential reference and capacity.
The Runtime Profile binds the requested capability to an Endpoint.
-Hypit's official Distribution includes local Providers, the HypiHub Provider, and API-key Providers
-for TokenDance, HiAPI, Pollo and Monid that serve the installed models each service offers. Other services
-connect through packages owned by the production or their authors. The Agent can implement a new
-service through the public SDK, just as it can create a visual component for a video.
+Hypit's official Distribution selects local Providers and the HypiHub Provider as defaults.
+TokenDance, HiAPI, Pollo, BeatAPI and Monid Providers are independently versioned packages installed
+by projects that choose those services. Other services connect through packages owned by the
+production or their authors. The Agent can implement a new service through the public SDK, just as
+it can create a visual component for a video.
[Model and deployment services](./service-partners.md) introduces independent partners through that
same path. Choosing a service is separate from [choosing an Agent environment](./agents.md).
diff --git a/docs/guide/studio-companion-architecture.md b/docs/guide/studio-companion-architecture.md
index 6dff920d..980276f9 100644
--- a/docs/guide/studio-companion-architecture.md
+++ b/docs/guide/studio-companion-architecture.md
@@ -15,9 +15,9 @@ independent packages. In both cases, Studio loads the Companions for the package
current Source and Distribution.
The [Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md)
-provides the activation and interface examples. External packages import `@hypit/hypit/studio-companion`,
-compile the Companion to JavaScript, and ship it with the component. Restart Studio after changing
-the installed code so the new contribution is loaded.
+provides the activation and interface examples. External packages declare and import
+`@hypit/studio-companion`, compile the Companion to JavaScript, and ship it with the component.
+Restart Studio after changing the installed code so the new contribution is loaded.
## Describe the author-facing objects
diff --git a/docs/quickstart/run.md b/docs/quickstart/run.md
index 00db2792..2babda5f 100644
--- a/docs/quickstart/run.md
+++ b/docs/quickstart/run.md
@@ -387,7 +387,7 @@ repository. The installed package manager owns their versions.
hypit doctor
```
-Doctor always validates the project's selected Result Repository. When a Runtime Profile is selected or
+Doctor always validates the project's Result repository. When a Runtime Profile is selected or
passed explicitly, it also validates every selected Runtime role, Endpoint configuration, credential
presence and bounded environment probe. It never starts the Worker or performs a paid request.
diff --git a/docs/zh/guide/packages.md b/docs/zh/guide/packages.md
index e34ec5ea..b0603a99 100644
--- a/docs/zh/guide/packages.md
+++ b/docs/zh/guide/packages.md
@@ -13,7 +13,7 @@ Hypit 把视频需要什么,与哪些代码和服务完成它,分别表达
| Model | 定义明确的生成请求与输出 | Source 导入 |
| Provider Endpoint | 通过 API 或本地工具执行支持的请求 | Runtime Profile |
| 凭据存储 | 为 Endpoint 解析具名凭据 | Runtime Profile |
-| Result 仓库 | 保留项目的 Build 记录与产物文件 | 项目 Result 配置 |
+| Result 仓库 | 保留项目的 Build 记录与产物文件 | Runtime 实现;Local Runtime 使用项目的 `.hypit/results` |
| Distribution | 提供可执行应用与官方包 | 安装的 `hypit` 版本 |
例如,Model 描述要生成的视频,Provider 将请求映射到服务;Ranking 组件描述榜单的行为,渲染器将其贡献绘制到最终编排。两者都通过明确输入与输出参与同一个图。
@@ -30,17 +30,17 @@ Window 与 Instant;作者主导节奏的动画,则可以在声明的时钟
## 安装与 Source 导入
-Skill、可执行 Distribution 和视频项目分别安装与更新。`@hypit/hypit` Distribution 包含官方作者包和公开扩展 API。所选 Runtime Adapter 可以通过 `hypit runtime up` 准备其声明的服务与运行材料。npm 依赖随其所有者安装:Distribution 的依赖随 Distribution 安装,项目组件的依赖由项目管理。
+Skill、可执行 Distribution 和视频项目分别安装与更新。`@hypit/hypit` Distribution 内嵌 Core,将产品选定的默认作者包作为普通 npm 依赖安装,并公开扩展 API。所选 Runtime Adapter 可以通过 `hypit runtime up` 准备其声明的服务与运行材料。npm 依赖随其所有者安装:Distribution 的依赖随 Distribution 安装,项目组件的依赖由项目管理。
Source 使用 `@your-studio/scoreboard@1` 这样的逻辑 Module 地址。npm 安装的包版本决定实际实现,逻辑 `@1` 标识作者接口。视频 Build 使用这些已安装的版本;缺包时会报告安装所需的信息。
## 编写与分享扩展
-外部包只使用自己实际需要的窄公共所有者,例如 `@hypit/hypit/author`、`producer`、`admission`、`markup`、`composition`、`model-kit` 或 `endpoint`。将选定的 `@hypit/hypit` 版本作为开发依赖,把扩展编译为 JavaScript,分发它自己的代码与素材。`package.json` 中的 activation 入口描述它提供的能力;加载选中的扩展时,当前 Distribution 提供公开 Hypit API。
+外部包只使用自己实际需要的窄公共所有者,例如 `@hypit/hypit/author`、`@hypit/hypit/producer`、`@hypit/hypit/admission`、`@hypit/hypit/markup`、`@hypit/hypit/composition`、`@hypit/hypit/generation/model` 或 `@hypit/hypit/endpoint`。将选定的 `@hypit/hypit` 版本作为开发依赖,把扩展编译为 JavaScript,分发它自己的代码与素材。`package.json` 中的 activation 入口描述它提供的能力;加载选中的扩展时,当前 Distribution 提供公开 Hypit API。
- [添加作者包](./author-packages.md):从随发行包提供的可构建组件开始。
- [组件结构](./component-anatomy.md):组件内部各部分的职责。
- [模型与 Provider](./providers.md):新模型、服务与凭据的选择。
- [Runtime](./runtime.md):Endpoint 和凭据配置。
-精确 SDK 类型与实现示例留在对应包的 README 和源码中,它们也随 Distribution 分发。
+精确 SDK 类型与实现示例留在对应包的 README 和仓库源码中;安装后的包提供公开类型与可执行代码。
diff --git a/docs/zh/guide/providers.md b/docs/zh/guide/providers.md
index c51d3f62..12b5de18 100644
--- a/docs/zh/guide/providers.md
+++ b/docs/zh/guide/providers.md
@@ -5,7 +5,7 @@ description: 选择账户、连接服务或添加模型,沿用同一套视频
**Model** 定义要生成什么:输入、支持的参数和输出类型。**Provider** 知道如何通过某个服务完成这个请求。**Endpoint** 是配置好的 Provider 实例,包含服务地址、凭据引用和容量。Runtime Profile 将所需能力绑定到 Endpoint。
-官方发行包含本地 Provider、HypiHub Provider,以及 TokenDance、HiAPI、Pollo、Monid 四个使用 API Key 的 Provider,各自覆盖该服务提供的已安装模型。其他服务通过项目或作者自己的包接入;Agent 可以使用公开 SDK 编写所需接入,就像为视频创建视觉组件。[模型与部署服务](./service-partners.md) 集中介绍独立合作服务,它们沿用同一套扩展方式。选择执行服务,与[选择 Agent 工作环境](./agents.md)是两件事。
+官方 Distribution 默认选择本地 Provider 与 HypiHub Provider。TokenDance、HiAPI、Pollo、BeatAPI 和 Monid Provider 是独立版本包,由选择相应服务的项目安装。其他服务通过项目或作者自己的包接入;Agent 可以使用公开 SDK 编写所需接入,就像为视频创建视觉组件。[模型与部署服务](./service-partners.md) 集中介绍独立合作服务,它们沿用同一套扩展方式。选择执行服务,与[选择 Agent 工作环境](./agents.md)是两件事。
HypiHub 是我们推荐的集成托管服务。**BYOK** 指使用自己账户的 API Key:Key 通过兼容的 Provider 连接到签发它的服务。告诉 Agent 你已有哪个服务及其 API 文档,具体接线和项目包可以由 Agent 完成。Key 负责授权请求,本身不会实现 API 接口。一个项目可以为不同能力使用不同服务,分别使用各自的账户并按各自规则计费。
diff --git a/docs/zh/guide/studio-companion-architecture.md b/docs/zh/guide/studio-companion-architecture.md
index 61a2b2a3..07965788 100644
--- a/docs/zh/guide/studio-companion-architecture.md
+++ b/docs/zh/guide/studio-companion-architecture.md
@@ -9,7 +9,7 @@ description: 为组件提供有意义的时间线 Item 和 Studio 编辑控件
Companion 是应用贡献。项目组件可以在同一个物理包中,以独立文件和 facet 携带它;官方 Distribution 通过独立包提供官方 Companion。两种情况下,Studio 都加载当前 Source 和 Distribution 所选包的 Companion。
-[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md) 提供 activation 与接口示例。外部包使用 `@hypit/hypit/studio-companion`,将 Companion 编译为 JavaScript 并与组件一起分发。修改安装代码后,重启 Studio 加载新贡献。
+[Companion SDK](https://github.com/hypit-ai/hypit/blob/main/packages/studio-companion/README.md) 提供 activation 与接口示例。外部包声明并使用 `@hypit/studio-companion`,将 Companion 编译为 JavaScript 并与组件一起分发。修改安装代码后,重启 Studio 加载新贡献。
## 描述作者面对的对象
diff --git a/docs/zh/quickstart/run.md b/docs/zh/quickstart/run.md
index 55cf05e1..53ed6f25 100644
--- a/docs/zh/quickstart/run.md
+++ b/docs/zh/quickstart/run.md
@@ -325,7 +325,7 @@ Author/Run Source 通过 import 选择作者包;官方视频 Distribution 已
hypit doctor
```
-Doctor 总会校验项目选择的 Result Repository;存在已选或显式传入的 Runtime Profile 时,还会校验全部
+Doctor 总会校验项目的 Result 仓库;存在已选或显式传入的 Runtime Profile 时,还会校验全部
Runtime 角色、Endpoint 配置、凭据是否存在和有界环境探测。它不启动 Worker,也不发付费请求。
存在 Profile 时,`doctor` 默认检查整个 Profile,也可以重复 `--endpoint <instance>` 限定服务。
diff --git a/docs/zh/quickstart/script.md b/docs/zh/quickstart/script.md
index 39596799..4ae4fb4f 100644
--- a/docs/zh/quickstart/script.md
+++ b/docs/zh/quickstart/script.md
@@ -253,7 +253,7 @@ Narrative Projection 声明通过 `{story.moment.ranking}` 引用 Moment,并
| `\\` | 字面量 `\` |
| `\|` | 字面量 `|`(两个竖线写成 `\|\|`) |
-普通文本中的单个 `|` 本身就是字面量;未转义的 `||` 才是 Caption Cue Break。
+普通文本中的单个 `|` 本身就是字面量;未转义的 `||` 才是 Caption Cue 分隔符。
在 Dual Text 内部,第一个未转义的 `|` 分隔 display 和 spoken 两侧;display 侧的竖线必须
写成 `\|`,需要字面量右尖括号时写成 `\>`。
diff --git a/examples/complex-explainer/README.md b/examples/complex-explainer/README.md
index 56da0514..ee756392 100644
--- a/examples/complex-explainer/README.md
+++ b/examples/complex-explainer/README.md
@@ -77,7 +77,7 @@ explains joining exported parts. The archive also includes `productions/explaine
| Which existing material should a new Build use? | [Render Run](productions/explainer/runs/render.svrun) |
Generated and normalized Outputs remain in the entry Source where the Run can satisfy them explicitly.
-Changing a cue break or graphic event does not require replacing the performance. A rewrite of the
+Changing a Cue boundary or graphic event does not require replacing the performance. A rewrite of the
spoken words is different: supply new performance media with timing for that Script and select it in the Run.
The retained generation declarations show the original direction but are not invoked by the default
Run. Configure an explicitly chosen Model/Provider path before requesting new material.
diff --git a/examples/complex-explainer/packages/single-line-captions/README.md b/examples/complex-explainer/packages/single-line-captions/README.md
index 41bf10c0..30424c78 100644
--- a/examples/complex-explainer/packages/single-line-captions/README.md
+++ b/examples/complex-explainer/packages/single-line-captions/README.md
@@ -4,4 +4,4 @@ Uses the public fine-caption renderer and author surface. Incoming cues take the
## Studio
-The project Track reuses the standard Fine Caption Companion with its Module identity. Cues display their actual content and numbering, and Uses keep the normal style band and recipe parameters. Only visibility scheduling differs from Fine Caption; cue identities, style projection and author editing follow the existing public implementation.
+The project Track reuses the standard Fine Caption Companion with its Module identity. Cue Items display their actual content and numbering. Uses remain Inspector presentation-rule objects with their Style and Recipe controls. Only visibility scheduling differs from Fine Caption; Cue identities, Style projection and author editing follow the existing public implementation.
diff --git a/examples/complex-explainer/productions/explainer/README.md b/examples/complex-explainer/productions/explainer/README.md
index bedcd617..b8ba62fc 100644
--- a/examples/complex-explainer/productions/explainer/README.md
+++ b/examples/complex-explainer/productions/explainer/README.md
@@ -18,7 +18,7 @@ The current production Run explicitly selects accepted Outputs. Read the plan be
| Edit | Owner |
| --- | --- |
-| Spoken words, cue breaks, Moments and Selections | `authors/script.svml` |
+| Spoken words, Cue boundaries, Moments and Selections | `authors/script.svml` |
| Input images, recordings, fonts and clock/canvas | `authors/assets.svml` |
| Performance prompt and selected speaker Kit | `authors/direction.svml`, `recipes/performance.svs` |
| Material outputs, media placement, Uses, scene events and Film | `authors/main.svml` |
diff --git a/examples/ranking-football/reference-banana-from-swap/reference-banana-from-swap.svml b/examples/ranking-football/reference-banana-from-swap/reference-banana-from-swap.svml
index ecb55526..5da2530d 100644
--- a/examples/ranking-football/reference-banana-from-swap/reference-banana-from-swap.svml
+++ b/examples/ranking-football/reference-banana-from-swap/reference-banana-from-swap.svml
@@ -26,7 +26,7 @@
<!-- The Program projection owns the complete board lifetime. Each discussed
footballer's complete Segment projects its disjoint reveal window, so
- TierBoard consumes windows without finding frames. Cue breaks are author intent. -->
+ TierBoard consumes windows without finding frames. Cue boundaries are author intent. -->
<script id="story">
<ronaldo>
<HOST>Ronaldo is <D | Dee> tier. || Bro has @{hair-gel} more || hair gel than @{trophy} trophies || at this point.@{/trophy}@{/hair-gel} || Built like || @{greek-god} a Greek god, || plays like || @{greek-tragedy} a Greek tragedy.@{/greek-tragedy}@{/greek-god} || But hey, || at least @{penaldo-social} he's got || the most followers || on Instagram.@{/penaldo-social}
diff --git a/examples/ranking-football/reference-banana/reference-banana.svml b/examples/ranking-football/reference-banana/reference-banana.svml
index ecb55526..5da2530d 100644
--- a/examples/ranking-football/reference-banana/reference-banana.svml
+++ b/examples/ranking-football/reference-banana/reference-banana.svml
@@ -26,7 +26,7 @@
<!-- The Program projection owns the complete board lifetime. Each discussed
footballer's complete Segment projects its disjoint reveal window, so
- TierBoard consumes windows without finding frames. Cue breaks are author intent. -->
+ TierBoard consumes windows without finding frames. Cue boundaries are author intent. -->
<script id="story">
<ronaldo>
<HOST>Ronaldo is <D | Dee> tier. || Bro has @{hair-gel} more || hair gel than @{trophy} trophies || at this point.@{/trophy}@{/hair-gel} || Built like || @{greek-god} a Greek god, || plays like || @{greek-tragedy} a Greek tragedy.@{/greek-tragedy}@{/greek-god} || But hey, || at least @{penaldo-social} he's got || the most followers || on Instagram.@{/penaldo-social}
diff --git a/examples/ranking-football/reference-gpt.svml b/examples/ranking-football/reference-gpt.svml
index fff66a93..5c4d6646 100644
--- a/examples/ranking-football/reference-gpt.svml
+++ b/examples/ranking-football/reference-gpt.svml
@@ -26,7 +26,7 @@
<!-- The Program projection owns the complete board lifetime. Each discussed
footballer's complete Segment projects its disjoint reveal window, so
- TierBoard consumes windows without finding frames. Cue breaks are author intent. -->
+ TierBoard consumes windows without finding frames. Cue boundaries are author intent. -->
<script id="story">
<ronaldo>
<HOST>Ronaldo is <D | Dee> tier. || Bro has @{hair-gel} more || hair gel than @{trophy} trophies || at this point.@{/trophy}@{/hair-gel} || Built like || @{greek-god} a Greek god, || plays like || @{greek-tragedy} a Greek tragedy.@{/greek-tragedy}@{/greek-god} || But hey, || at least @{penaldo-social} he's got || the most followers || on Instagram.@{/penaldo-social}
diff --git a/examples/ranking-football/reference.svml b/examples/ranking-football/reference.svml
index dc8e7933..747e3c58 100644
--- a/examples/ranking-football/reference.svml
+++ b/examples/ranking-football/reference.svml
@@ -27,7 +27,7 @@
<!-- The Program projection owns the complete board lifetime. Each discussed
footballer's complete Segment projects its disjoint reveal window, so
- TierBoard consumes windows without finding frames. Cue breaks are author intent. -->
+ TierBoard consumes windows without finding frames. Cue boundaries are author intent. -->
<script id="story">
<ronaldo>
<HOST>Ronaldo is <D | Dee> tier. || Bro has @{hair-gel} more || hair gel than @{trophy} trophies || at this point.@{/trophy}@{/hair-gel} || Built like || @{greek-god} a Greek god, || plays like || @{greek-tragedy} a Greek tragedy.@{/greek-tragedy}@{/greek-god} || But hey, || at least @{penaldo-social} he's got || the most followers || on Instagram.@{/penaldo-social}
diff --git a/examples/ranking-football/swap-effect-banana-reference-sync/swap-effect-banana-reference-sync.svml b/examples/ranking-football/swap-effect-banana-reference-sync/swap-effect-banana-reference-sync.svml
index fde663c0..0c955e2c 100644
--- a/examples/ranking-football/swap-effect-banana-reference-sync/swap-effect-banana-reference-sync.svml
+++ b/examples/ranking-football/swap-effect-banana-reference-sync/swap-effect-banana-reference-sync.svml
@@ -26,7 +26,7 @@
<!-- The Program projection owns the complete board lifetime. Each discussed
footballer's complete Segment projects its disjoint reveal window, so
- TierBoard consumes windows without finding frames. Cue breaks are author intent. -->
+ TierBoard consumes windows without finding frames. Cue boundaries are author intent. -->
<script id="story">
<ronaldo>
<HOST>Ronaldo is <D | Dee> tier. || Bro has @{hair-gel} more || hair gel than @{trophy} trophies || at this point.@{/trophy}@{/hair-gel} || Built like || @{greek-god} a Greek god, || plays like || @{greek-tragedy} a Greek tragedy.@{/greek-tragedy}@{/greek-god} || But hey, || at least @{penaldo-social} he's got || the most followers || on Instagram.@{/penaldo-social}
diff --git a/examples/ranking-football/swap-host.svml b/examples/ranking-football/swap-host.svml
index 2510c18c..94c4697d 100644
--- a/examples/ranking-football/swap-host.svml
+++ b/examples/ranking-football/swap-host.svml
@@ -26,7 +26,7 @@
<!-- The Program projection owns the complete board lifetime. Each discussed
footballer's complete Segment projects its disjoint reveal window, so
- TierBoard consumes windows without finding frames. Cue breaks are author intent. -->
+ TierBoard consumes windows without finding frames. Cue boundaries are author intent. -->
<script id="story">
<ronaldo>
<HOST>Ronaldo is <D | Dee> tier. || Bro has @{hair-gel} more || hair gel than @{trophy} trophies || at this point.@{/trophy}@{/hair-gel} || Built like || @{greek-god} a Greek god, || plays like || @{greek-tragedy} a Greek tragedy.@{/greek-tragedy}@{/greek-god} || But hey, || at least @{penaldo-social} he's got || the most followers || on Instagram.@{/penaldo-social}
diff --git a/packages/cli/README.md b/packages/cli/README.md
index 1548a39b..8ffe9ae7 100644
--- a/packages/cli/README.md
+++ b/packages/cli/README.md
@@ -124,7 +124,8 @@ instead. Credential entry operates on an already declared Endpoint and changes n
selection or neither. Its JSON fields `profileSource` and `selectionFile` expose that distinction; the
selection-file location is shown even when no selection exists. `doctor` states whether it checked
only project Results or also a selected Runtime. An unselected Runtime is not a completed environment
-diagnosis. Result repository selection and project-package resolution remain independent of Runtime.
+diagnosis. Project-owned Result history and project-package resolution remain available without
+opening a Runtime.
For a command invoked outside the project, name both the project and its input explicitly:
@@ -167,14 +168,15 @@ browsing/export lives under `commands/results.ts`; generic diagnosis and credent
`commands/environment.ts`; active Build observation is read-only code in `observation.ts`; and human
rendering is separate from the explicit machine-view union. `runtime-local/cli` owns local Profile
selection, paths, Programs and Worker lifecycle. `main.ts` consumes only `CliRuntimeHost`; it never
-imports the Local Runtime implementation. Result commands do not consult or construct a Runtime,
-and the generic CLI cannot silently choose a Result Repository or a Provider-specific login flow.
+imports the Local Runtime implementation. Result commands do not consult or construct a Runtime;
+the generic CLI opens the resolved project's Result history and cannot silently choose a
+Provider-specific login flow.
## Execution logs
`hypit logs <build-id> [--project <project>] [--runtime <profile>] [--lines <count>]` reads Build
execution phases and Provider diagnostics. It reads a finished Result directly, without opening the
-Runtime; an active Build is read through Runtime control. The selected Repository handles file access.
+Runtime; an active Build is read through Runtime control. The project Result repository handles file access.
`--lines` limits the tail and the report states the omitted count; JSON carries records plus that count.
An unavailable log reports `source: "unavailable"` and exits unsuccessfully; a readable log with zero
records is a successful empty result. The human report distinguishes a finished Result with no log
diff --git a/packages/gpt-image/README.md b/packages/gpt-image/README.md
index 313fe86a..02f05476 100644
--- a/packages/gpt-image/README.md
+++ b/packages/gpt-image/README.md
@@ -51,5 +51,6 @@ assembly, generation and primary-image selection. The clean module then adds its
generic image-operations package owns the Program shape and operation semantics; this package owns
the selected cleanup recipe.
-The Surface implementation belongs to this package. `model-kit` remains responsible only for the
-exact request and Fragment shell; it owns no author-Surface registry or model syntax.
+The Surface implementation belongs to this package. The public
+`@hypit/hypit/generation/model` helpers remain responsible only for the exact request and Fragment
+shell; they own no author-Surface registry or model syntax.
diff --git a/packages/media-operations/README.md b/packages/media-operations/README.md
index d2e65d0b..acc7e7d8 100644
--- a/packages/media-operations/README.md
+++ b/packages/media-operations/README.md
@@ -118,5 +118,5 @@ of hidden normalization/limiting. The local FFmpeg Provider consumes the shared
public request and result semantics.
AudioProgramPlan preserves AudioClip `gainEnvelope` and `audibility` on the full program sample
-clock. The [Composition definition](../composition/README.md#audio-presentation-on-the-program-clock)
+clock. The [Composition definition](../composition/README.md#audio-level-automation-on-the-program-clock)
owns their semantics; the plan does not reinterpret source choice or presentation precedence.
diff --git a/packages/producer/README.md b/packages/producer/README.md
index fc8c679c..d776cd95 100644
--- a/packages/producer/README.md
+++ b/packages/producer/README.md
@@ -33,12 +33,14 @@ Author Kit; import only the owner of each responsibility:
| `@hypit/hypit/author` | sealed Author Graph Fragments |
| `@hypit/hypit/markup` | Markup Surface declarations and handlers |
| `@hypit/hypit/temporal/markup` | author-time semantic Window/Instant projection helpers |
-| `@hypit/hypit/composition`, `@hypit/hypit/composition` | peer Track values and renderer-independent visual representation |
-| `@hypit/studio-companion` (optional, in Companion code) | editor entity projection, Inspector bindings and executed temporal lineage |
-
-The Author Package keeps one development dependency on `@hypit/hypit`, compiles its activation to
-JavaScript, and publishes only its own files. The active Distribution supplies these subpaths at
-execution, so a component does not carry a second Core or choose its own framework version. This
+| `@hypit/hypit/composition` | peer Track values and renderer-independent visual representation |
+| `@hypit/studio-companion` (optional, in Companion code) | editor Item projection, Inspector bindings and executed temporal lineage |
+
+The Author Package keeps `@hypit/hypit` as its framework development dependency. A package that
+contributes a Companion also declares `@hypit/studio-companion` as a development dependency. It
+compiles its activation to JavaScript and publishes only its own files. The active Distribution
+supplies these APIs at execution, so a component does not carry a second Core or choose its own
+framework version. This
package remains the deterministic-handler owner; the public subpaths do not create a second package
format or a facade that claims to own every kind of author extension.
@@ -96,7 +98,7 @@ Runtime.
## Optional Studio presentation
A component can render through the ordinary Track protocol without custom editor behavior. When it
-needs meaningful timeline entities or Inspector fields, put a Companion in a separate file and
+needs meaningful timeline Items or Inspector fields, put a Companion in a separate file and
merge `createStudioTrackCompanionFacet(companions)` into the same activation's `facets`.
Retain the existing Module, Producer and Surface contributions. The selected project's package
supplies the extension; do not edit Studio's registry or add editor metadata to the domain Manifest.
diff --git a/packages/runtime-local/README.md b/packages/runtime-local/README.md
index a179ad07..10ee735d 100644
--- a/packages/runtime-local/README.md
+++ b/packages/runtime-local/README.md
@@ -117,7 +117,7 @@ The official video Distribution writes Results to the project's `.hypit/results`
cloud account or service. The filesystem implementation belongs to this single-host Runtime rather
than a public adapter registry.
Runtime working Resources remain internal and Build-local; there is no ResourceStore selector. After
-a Result has an outcome, history is read from the selected repository, not Runtime SQLite.
+a Result has an outcome, history is read from the project Result repository, not Runtime SQLite.
The submission passes known Resource references to the Result writer, separately from the execution
graph. Staging bytes for a running Build does not make them new Result files: external and reused
resources keep their addresses even when a Producer embeds them inside a new Composite value.
@@ -168,7 +168,7 @@ Profile's `dataRoot`. Each record carries time, Command and Endpoint identity. P
and repeated progress counters do not become log entries. The latest counters remain active Runtime
state; Provider-authored diagnostics and phase changes are durable evidence.
-Result finishing streams this log through the selected Repository before publishing the terminal
+Result finishing streams this log through the project Result repository before publishing the terminal
manifest or clearing the Build working directory. Complete, failed and cancelled Builds use the same
finishing path. A failed archive leaves Result attention and preserves the working directory; finishing
that Result performs no external execution. Log write failures also surface at the Result boundary,
diff --git a/packages/script/README.md b/packages/script/README.md
index fe6dcafb..0b023c13 100644
--- a/packages/script/README.md
+++ b/packages/script/README.md
@@ -146,7 +146,7 @@ Script preserves the normalized display spelling independently of speech tokeniz
whitespace runs become one space; leading/trailing whitespace in a Turn and padding at the edges
of a Dual Text side are omitted. No language-specific rule removes a Chinese space or inserts a
space between numeric and Korean/Latin tokens. `是的 就是这样`, `3개월`, `3 개월`, `3D` and `3 D`
-therefore remain distinct as authored. Source newlines are prose formatting, not Caption Cue breaks.
+therefore remain distinct as authored. Source newlines are prose formatting, not Caption Cue separators.
Use `||` for Cues and a family's layout controls for visual rows.
Each `CaptionDisplayWord.separatorBefore` is `""` or `" "`, relative to the preceding displayed word
diff --git a/packages/whisperx/README.md b/packages/whisperx/README.md
index 6ad51cf5..eea49f00 100644
--- a/packages/whisperx/README.md
+++ b/packages/whisperx/README.md
@@ -52,7 +52,7 @@ first and final frame, no evidence audio or WhisperX capability is requested, an
`NarrativeAlignment` type is published.
For Chinese speech use `zh`. WhisperX may emit character-sized evidence units; local alignment maps
-them to Script's authored units while Caption continues to use Script's display wording and Cue breaks.
+them to Script's authored units while Caption continues to use Script's display wording and authored Cue boundaries.
The package validates only the language-code form; the selected Endpoint owns actual language support.
## Local deployment
diff --git a/skills/hypit/references/creation/project-files.md b/skills/hypit/references/creation/project-files.md
index 2f59ad56..79b1a239 100644
--- a/skills/hypit/references/creation/project-files.md
+++ b/skills/hypit/references/creation/project-files.md
@@ -20,7 +20,7 @@ Keep discovery tied to the question being answered:
| --- | --- |
| An executable or prepared local service | `hypit paths`, package-manager records, the selected Profile and Provider-documented tool locations |
| Surface syntax or reusable behavior | Installed vocabulary, the owning package's documentation and a relevant component example |
-| This production's inputs and completed work | Supplied files, its notes, Sources, Runs and selected Result repository, including explicitly linked shared assets |
+| This production's inputs and completed work | Supplied files, its notes, Sources, Runs and project Result history, including explicitly linked shared assets |
Follow a path beyond the project when a supplied location, recorded dependency or documented tool
location explains its purpose. A nearby project with a similar name or subject does not establish
@@ -72,9 +72,10 @@ 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. 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,
+project uses its own package installation. Embedded Core comes from the selected Distribution;
+product-selected default packages are ordinary dependencies installed with it. Independently
+distributed project 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.
@@ -214,7 +215,7 @@ selected as file Candidates. A Composite export contains `value.json` and its re
inspection and transport; that document uses the Result value format, whereas a Run `<value>` accepts
a StoredValue wrapper. To retain structured normalized media, local-domain or alignment reuse, keep
its Result available and select each required Output with `build-record`. [Builds and Results](../production/builds.md)
-explains repository selection and export.
+explains Result reuse and export.
## Resume from present facts
diff --git a/skills/hypit/references/environment/distribution.md b/skills/hypit/references/environment/distribution.md
index f1d4d981..94567a7d 100644
--- a/skills/hypit/references/environment/distribution.md
+++ b/skills/hypit/references/environment/distribution.md
@@ -14,7 +14,7 @@ or [updates](#let-the-installation-channel-own-updates) for the current question
| Part | What it supplies | Where changes belong |
| --- | --- | --- |
| Hypit Skill | Production judgment and navigation | The Skill's own installation channel |
-| Executable Distribution, `@hypit/hypit` | CLI, Studio, Runtime and bundled packages | Its npm/release installation |
+| Executable Distribution, `@hypit/hypit` | CLI, embedded Core and product-selected default packages | Its npm/release installation |
| Video project | Sources, Runs, assets, project packages, selected Profile and Results | The project's files and package lock |
An installed Skill does not install the executable. Installing the executable does not connect an
diff --git a/skills/hypit/references/environment/model-and-provider.md b/skills/hypit/references/environment/model-and-provider.md
index ec5a3bba..d24cd1e0 100644
--- a/skills/hypit/references/environment/model-and-provider.md
+++ b/skills/hypit/references/environment/model-and-provider.md
@@ -6,7 +6,7 @@ path. [Profile](profile.md) owns configuration, credentials and routing; [local
owns local preparation. Material Craft owns what the generated or transformed media should do.
Go to [service choice](#choose-the-practical-capability-path-with-the-user),
-[HypiHub connection](#connect-hypihub-through-its-bundled-integration),
+[HypiHub connection](#connect-hypihub-through-its-default-integration),
[BYOK connection](#connect-a-service-the-user-brings),
[project implementation](#implement-the-missing-capability-in-the-project), or
[diagnosis](#diagnose-the-actual-connection) as needed.
@@ -35,7 +35,7 @@ Having a key grants only whatever the issuing service permits; it does not imple
## Choose the practical capability path with the user
**Recommend HypiHub as the integrated hosted route. Support BYOK as an ordinary route.**
-HypiHub's bundled Provider connects its supported image, video, speech, alignment and processing
+HypiHub's default Provider connects its supported image, video, speech, alignment and processing
capabilities through one account connection. This avoids assembling separate service adapters for
those capabilities. Its current catalogue, account access and rates still determine what is usable.
@@ -53,7 +53,7 @@ model capabilities. A Profile can mix services by capability.
| Route | What the user needs | What the Agent does |
| --- | --- | --- |
-| HypiHub | A chosen HypiHub account and spending scope | Use the bundled Provider and declared login flow; check support for the requested model and inputs |
+| HypiHub | A chosen HypiHub account and spending scope | Use the default Provider and declared login flow; check support for the requested model and inputs |
| An existing API service | Service identity, relevant API documentation/address and secure credential access | Reuse a compatible Provider or implement the needed API in the project |
| A chosen deployment | Its serving API, access and compute/account choice | Connect that API; deploy only if deployment is actually part of the requested work |
| Local inference | A suitable machine and an agreed preparation choice | Assess tools, resources and inference cost, then prepare the selected local Provider |
@@ -74,11 +74,11 @@ An installed Skill or executable supplies no model credits. A subscription alone
access to the required model API. Explain cost for the actual remaining work and reuse;
[Builds](../production/builds.md#work-within-the-agreed-paid-scope) owns spending estimates and submission.
-## Connect HypiHub through its bundled integration
+## Connect HypiHub through its default integration
From the production directory, locate the selected Profile with `hypit paths`. For a new project
needing one, `hypit runtime init` writes and selects a starter; it performs no login or download.
-The starter's `hypihub.default` entry already selects the bundled Provider. In an existing Profile,
+The starter's `hypihub.default` entry already selects the default Provider. In an existing Profile,
retain the chosen settings or merge this fragment if HypiHub is the newly selected service:
```json
diff --git a/skills/hypit/references/playbooks/craft/video-direction.md b/skills/hypit/references/playbooks/craft/video-direction.md
index 730eab05..d5843915 100644
--- a/skills/hypit/references/playbooks/craft/video-direction.md
+++ b/skills/hypit/references/playbooks/craft/video-direction.md
@@ -57,7 +57,7 @@ people, objects and world through useful references. A literal boundary frame he
continuity is intended; it is not needed for every new passage. The accepted outputs establish the
target's actual time. When uninterrupted continuity is essential, use a capability that can carry
it or explain what an edited interpretation changes. When an accepted wordless action carries the
-passage, [empty Segments](../../production/media.md#empty-segments-use-their-media-boundaries)
+passage, [empty Segments](../../production/media.md#project-a-wordless-segment-when-its-identity-is-consumed)
let that material establish its time without word tokens.
[Reference relationships](generated-dependencies.md) owns how images carry identity and world
diff --git a/skills/hypit/references/production/caption-presentation.md b/skills/hypit/references/production/caption-presentation.md
index d0a00e9e..0dd08b0a 100644
--- a/skills/hypit/references/production/caption-presentation.md
+++ b/skills/hypit/references/production/caption-presentation.md
@@ -65,6 +65,8 @@ not restart the Cue's animation clock. Changing only one word's visual role is a
choice: Fine provides current/trail unit emphasis, while a custom family can interpret authored word
attributes for structural layouts. Display/pronunciation units remain complete.
-In Studio, the content row shows Cues and the Uses row shows authored windows. Select a Use to edit
-its time or referenced Style. Moving the Use does not move `||`. Inspect the resulting placement,
-handoffs and emphasis alongside the other visuals while reusing the existing media.
+In Studio, Caption's timeline row shows Cue Items. Presentation Uses remain Inspector objects rather
+than draggable timeline ranges: their referenced Style or Recipe can be edited there, while their
+Scope and Role explain which Cues they affect. Changing `||` changes Cue structure; changing a Use
+does not. Inspect the resulting placement, handoffs and emphasis alongside the other visuals while
+reusing the existing media.
diff --git a/skills/hypit/references/production/script-syntax.md b/skills/hypit/references/production/script-syntax.md
index 1f0e97ca..006bd798 100644
--- a/skills/hypit/references/production/script-syntax.md
+++ b/skills/hypit/references/production/script-syntax.md
@@ -171,7 +171,7 @@ GUEST: That looks much easier.
Pass that Text to the speaking prompt. In action direction, relate HOST and GUEST to the supplied
character views and voices. The selected [Prompt Kit](prompt-kits.md) owns its reference
-order; [podcast direction](../playbooks/formats/two-person-podcast.md#direct-conversation-inside-a-take)
+order; [podcast direction](../playbooks/formats/two-person-podcast.md#direct-conversation-inside-a-generated-clip)
shows how those roles and references form one performed exchange.
These are projections of one authored Script, not copies to maintain. The performance request,
diff --git a/skills/hypit/references/production/studio-companions.md b/skills/hypit/references/production/studio-companions.md
index 8ef5d786..d12a7c06 100644
--- a/skills/hypit/references/production/studio-companions.md
+++ b/skills/hypit/references/production/studio-companions.md
@@ -169,10 +169,10 @@ 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-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
+Keep the Companion separate from the component's Producers. External packages declare and import
+`@hypit/studio-companion` alongside relevant public `@hypit/hypit/*` APIs, with the Distribution as
+their framework 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
diff --git a/skills/hypit/references/production/vocabulary.md b/skills/hypit/references/production/vocabulary.md
index fb1d270f..af96f437 100644
--- a/skills/hypit/references/production/vocabulary.md
+++ b/skills/hypit/references/production/vocabulary.md
@@ -85,7 +85,8 @@ owner's scope; `@hypit/*` is the Hypit project's publishing namespace, not a sco
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,
+`@hypit/hypit/text` or `@hypit/hypit/caption`; Studio Companions use the independent
+`@hypit/studio-companion` package. 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.
@@ -109,8 +110,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;
-exact packages embedded in the selected Distribution come from that Distribution, while independently
-published packages—including `@hypit/*` packages—follow ordinary project-first package resolution.
+embedded Core comes from the selected Distribution, while its product-selected default packages are
+ordinary dependencies installed with it. Independently published project 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