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.
TypeScript agentic-aiaiai-agentsai-videocompilerdslffmpeggenerative-aillmmarkup-languagemonorepoplugin-systemprogramming-languagetext-to-videotypescriptvideovideo-automationvideo-clonevideo-editingvideo-generation
docs: align runtime ownership model
kashorine3e334f66811
diff --git a/docs/guide/conventions.md b/docs/guide/conventions.mdindex abac2e2f..0a19011f 100644--- a/docs/guide/conventions.md+++ b/docs/guide/conventions.md@@ -56,5 +56,5 @@ Adding a package does not require changing the root TypeScript configuration.- Compilation failures throw with descriptive messages including source location.- Runtime failures are recorded as Operation failures in the Build state machine.-- Recoverable failures trigger retry according to Endpoint policy after Scheduler resource admission.+- Recoverable failures trigger retry according to Endpoint policy after Scheduler capacity acquisition.- Fatal failures transition the Build to a terminal state.diff --git a/docs/guide/packages.md b/docs/guide/packages.mdindex 9d7b93a7..46525097 100644--- a/docs/guide/packages.md+++ b/docs/guide/packages.md@@ -39,7 +39,7 @@ selects its own Frontend in its mandatory header; no central parser knows every@hypit/source mandatory Source Header@hypit/elaborator author declarations and Fragment expansion@hypit/run syntax-neutral Run Graph-@hypit/validation semantic admission+@hypit/validation semantic validation@hypit/host opaque Host-facet envelope@hypit/workspace replaceable Source/Asset session@hypit/compiler-node reference Node compiler Host@@ -242,7 +242,9 @@ A physical package may expose independently activated facets:| `author` | Frontend, Surface, Graph Fragment | author vocabulary only | source `<import>` through the compiler Host || `compute` | deterministic Producer, Type Validator | pure computation | compiler Host || `endpoint` | privileged external capability | network, filesystem, process, credentials | Runtime Profile |-| `infrastructure` | Scheduler, Worker and Store implementation | persistence, scheduling | Runtime Profile |+| `credential-store` | resolves explicitly named credentials | secret storage | Runtime Profile |+| `result-repository` | completed Build Results | project history storage | project `hypit.results.json` |+| `infrastructure` | Runtime Host, Scheduler and Worker implementation | persistence, scheduling | application Distribution || `application` | Host-specific interpretation such as a Studio Track Companion | only that application's UI/operations | explicit application profile |A source `<import>` activates only author facets. It never grants network, filesystem, process,@@ -251,16 +253,19 @@ credential or queue authority.## Package selectionHypit does not maintain a package registry or a second package-resolution layer. npm or pnpm-installs packages and owns their versions and integrity. Hypit has two explicit selection paths:+installs packages and owns their versions and integrity. Each owner has one explicit selection path:| Selection | Packages activated ||---|---|+| Application Distribution | Runtime Host and trusted bootstrap packages || Source imports | Frontends, Surfaces, Producers and Validators |-| Runtime Profile `use` | Runtime Hosts, infrastructure and Provider Endpoints |+| Runtime Profile `credentials.*.use` / `endpoints.*.use` | Credential Stores and Provider Endpoints |+| Project Result config `use` | one Build Result Repository || Studio Profile `companionPackages` | project Companion packages selected for that Studio session |A Source import never grants network, filesystem, process, credential or queue authority. Those-remain available only to packages explicitly selected by the Runtime Profile.+remain available only to the Runtime Host and packages explicitly selected at environmental+boundaries.### Logical package addresses and Source discovery@@ -279,15 +284,16 @@ Frontend implementations are not privileged fields in the physical package formathe ordinary `hypit.source-frontend@1` Host facet, exactly as Run Fragments, Markup Surfaces andRuntime Adapters advertise their own Host ABIs. Only the Source Host interprets that facet.-Runtime Profiles follow the same rule. Each `use` selects a Runtime Host, Endpoint Adapter or-Runtime Infrastructure ABI plus a logical name. A physical npm package advertises that logical-offer. The generic CLI therefore-does not contain a Provider registry, and different Adapter kinds may share-a logical spelling without colliding.+Runtime Profiles follow the same rule for the two facets they actually select. Each `use` names one+Credential Store or Endpoint Adapter offer. Project Result configuration independently selects one+Repository offer. The application Distribution supplies the Runtime Host itself; it is not repeated+as a fake selector inside that Host's Profile. The generic CLI therefore contains neither a Provider+registry nor a hard-coded Result Repository, and different Adapter kinds may share a logical spelling+without colliding.The loader never downloads packages and never scans unrelated installed dependencies for plugins.-It loads only packages selected by Source discovery or the Runtime Profile, plus exact Module-dependencies declared by those packages.+It loads only packages selected by Source discovery, environmental configuration or the application+Distribution, plus exact Module dependencies declared by those packages.An authored project is a separate directory and Git/workspace boundary. Its explicit packages areresolved from its own `packages/` or installation; the active tool Distribution supplies thediff --git a/docs/guide/providers.md b/docs/guide/providers.mdindex 9fabefaf..6d96d9e1 100644--- a/docs/guide/providers.md+++ b/docs/guide/providers.md@@ -46,8 +46,8 @@ packages or the CLI:## 3. Implement the Provider-The Provider handles Commands from the Scheduler: request submission, polling, download and-admission into the current Build's working byte area.+The Provider handles Commands from the Scheduler: request submission, polling, download and writing+the accepted Resource into the current Build's working byte area.```typescript// src/provider.tsdiff --git a/docs/guide/runtime.md b/docs/guide/runtime.mdindex 5ef88206..d4ac6b7b 100644--- a/docs/guide/runtime.md+++ b/docs/guide/runtime.md@@ -147,13 +147,13 @@ For an S3-compatible repository:The AWS SDK uses its normal credential chain. `endpoint` and `forcePathStyle` are available forS3-compatible services. The prefix is the project boundary: each project should have its ownprefix. S3 changes only where complete Results live; it does not move Runtime SQLite, Provider capacity or-temporary working Artifacts into the bucket.+an active Build's temporary Resources into the bucket.The S3 adapter maps each ordered Build id to a reversible newest-first physical prefix. It can requestone bounded delimiter page from object storage without a central index or duplicate catalog. Resultfiles are streamable by byte range, soStudio video/audio requests do not load a whole remote file into memory first. `hypit doctor-[profile] --workspace <project>` actively checks the selected Result Store as well as the Runtime;+[profile] --workspace <project>` actively checks the selected Result Repository as well as the Runtime;the storage check performs only a bounded read-only listing and does not scan Result history.The Workspace is resolved independently from the explicit `--workspace`, the project containing thediff --git a/docs/quickstart.md b/docs/quickstart.mdindex d2f175ba..58e6ff31 100644--- a/docs/quickstart.md+++ b/docs/quickstart.md@@ -112,8 +112,8 @@ hypit plan build.svrunA project with `package.json` owns its third-party packages. A plain creative folder needs no Nodeproject and uses official packages from the installed Distribution. Source and exported files remain in theproject. By default, Build Results live under the project's `.hypit/results`; a project-owned-`hypit.results.json` may point the same complete Result model at S3. Active execution state always lives under the selected Profile's-`dataRoot`.+`hypit.results.json` may point the same complete Result model at S3. Active execution state and+temporary Resources always live under the selected Profile's `dataRoot`.`runtime use` stores only a local pointer at `.hypit/runtime`. Source imports select authorpackages; the Profile independently selects Credential Stores and Endpoints through their own `use` entries.@@ -183,7 +183,7 @@ hypit runtime upThe Runtime creates a missing managed environment in the machine Program Home and reuses it acrossprojects and sessions. Do not run a service's `uv sync` from an author project.-Run `hypit doctor hypit.runtime.json` after changing a Runtime Profile or project Result Store. It reports missing tools,+Run `hypit doctor hypit.runtime.json` after changing a Runtime Profile or project Result Repository. It reports missing tools,credentials and endpoint configuration without executing the graph.## Read nextdiff --git a/docs/quickstart/preview.md b/docs/quickstart/preview.mdindex 126354cb..7b24a0f3 100644--- a/docs/quickstart/preview.md+++ b/docs/quickstart/preview.md@@ -17,7 +17,7 @@ hypit-studio --run examples/all-components-preview/studio.svrun --workspace .| Argument | Meaning || --- | --- || `--run <build.svrun>` | Run Source to open. Required. |-| `--runtime <hypit.runtime.json>` | Optional Runtime Profile used only to show active `BuildView` and Operation information. Historical Results and `<build-record>` come from the project Result Store. |+| `--runtime <hypit.runtime.json>` | Optional Runtime Profile used only to show active `BuildView` and Operation information. Historical Results and `<build-record>` come from the project Result Repository. || `--workspace <directory>` | Source access and writeback boundary; defaults to the Run directory. || `--port <number>` | HTTP port; defaults to `5179`. |diff --git a/docs/quickstart/run.md b/docs/quickstart/run.mdindex d192f57c..fa66e091 100644--- a/docs/quickstart/run.md+++ b/docs/quickstart/run.md@@ -6,8 +6,9 @@ description: Declaring build targets, reusing results and configuring the runtim# Run Source & BuildsThe Author Source defines the video. A Run Source chooses which of its public outputs to produce and-which explicit Candidates, if any, should satisfy them. The Runtime Profile chooses the machine,-credentials, Provider endpoints and services that execute the resulting plan.+which explicit Candidates, if any, should satisfy them. The official Distribution supplies the Local+Runtime; its Profile names the credentials, Provider Endpoints and services available to execute the+resulting plan.Select the project Runtime once:@@ -207,10 +208,10 @@ lookup. A black video, preview image or human-supplied result uses the same mech## Runtime Profile-The Runtime Profile chooses where Builds execute. It creates named infrastructure instances from-packages selected by logical `use` names, assigns their exported parts to Runtime roles, and-configures Provider endpoints and capacity. It never defines the Source Workspace or Author package-selection.+The official video Distribution has already chosen the Local Runtime. Its Profile names the+Credential Stores and Endpoints that local execution may use, together with deployment settings such+as Endpoint capacity. It never selects the Runtime Host or defines the Source Workspace, Author+packages or project Result repository.```bashhypit runtime use hypit.runtime.json@@ -281,7 +282,7 @@ only with `--workspace`. `--package-root` locates installed packages and never wThat is the zero-configuration Result repository. The `output/` directory shown earlier is only aconvenient destination for explicit exports and is not part of Result storage. A project-owned `hypit.results.json` may instead select`@hypit/build-result-s3`; commands and historical `build-record` references then use that same-repository. Runtime working Artifacts remain local and private to the Runtime.+repository. Temporary Resources remain local and private to the active Runtime.### 1. Select a Runtime@@ -290,9 +291,9 @@ cd examples/talking-head-arollhypit runtime use hypit.runtime.json```-Author and Run Sources select their packages through imports. The Runtime Profile selects its Host,-credential and Endpoint packages through `use`; the project separately owns its Result repository. The installed package manager-owns their versions.+Author and Run Sources select their packages through imports. The Local Runtime Profile selects+Credential Store and Endpoint packages through `use`; the project separately owns its Result+repository. The installed package manager owns their versions.### 2. Diagnose the environment@@ -300,7 +301,7 @@ owns their versions.hypit doctor```-Doctor always validates the project's selected Result Store. When a Runtime Profile is selected or+Doctor always validates the project's selected Result Repository. When a Runtime Profile is selected orpassed explicitly, it also validates every selected Runtime role, Endpoint configuration, credentialpresence and bounded environment probe. It never starts the Worker or performs a paid request.@@ -408,6 +409,7 @@ hypit runtime logshypit runtime down```-`runtime down` stops the Worker from claiming more Builds but leaves external programs running.+`runtime down` stops the Worker from advancing Builds but leaves external programs running.Use `programs down` only when those programs should also stop. Neither command cancels durable-Builds or remote Provider work. Starting the same Profile again continues unfinished dispatches.+Builds or remote Provider work. Starting the same Profile again continues its active Builds from+their already accepted execution facts.diff --git a/docs/zh/guide/packages.md b/docs/zh/guide/packages.mdindex 9e7068ab..a29e8b12 100644--- a/docs/zh/guide/packages.md+++ b/docs/zh/guide/packages.md@@ -34,7 +34,7 @@ Frontend;不存在一个认识全部语法的中央解析器。@hypit/source mandatory Source Header@hypit/elaborator author declarations and Fragment expansion@hypit/run syntax-neutral Run Graph-@hypit/validation semantic admission+@hypit/validation semantic validation@hypit/host opaque Host-facet envelope@hypit/workspace replaceable Source/Asset session@hypit/compiler-node reference Node compiler Host@@ -169,7 +169,7 @@ Frontend;不存在一个认识全部语法的中央解析器。2. **领域无关 Core 闭包。** Layer 1 只有 `protocol` 与 `core`,且 `core` 只依赖 `protocol`。Compiler 与 Runtime 也可以领域无关,但它们不属于 Core。-3. **CLI 独立性。** `@hypit/cli` 和 `@hypit/video-cli` 都不会传递依赖任何 Provider 包。video CLI 同样不依赖任何作者层的视频包(`@hypit/script`、`@hypit/seedance`、`@hypit/media-track`、`@hypit/typography-track`、`@hypit/film`)。Source import 按需激活作者包,Runtime Profile 的逻辑 `use` 名称按需激活运行包;两者都不是 CLI 的编译期依赖。+3. **CLI 独立性。** `@hypit/cli` 和 `@hypit/video-cli` 都不会传递依赖任何 Provider 包。video CLI 同样不依赖任何作者层的视频包(`@hypit/script`、`@hypit/seedance`、`@hypit/media-track`、`@hypit/typography-track`、`@hypit/film`)。Source import 按需激活作者包,Runtime Profile 的逻辑 `use` 名称按需激活 Credential Store 与 Endpoint 包;两者都不是 CLI 的编译期依赖。## 包的结构@@ -223,7 +223,9 @@ packages/example/| `author` | Frontend、Surface、Graph Fragment | 仅作者词汇 | 源码中的 `<import>`,经由编译器 Host || `compute` | 确定性 Producer、Type Validator | 纯计算 | 编译器 Host || `endpoint` | 具备特权的外部能力 | 网络、文件系统、进程、凭据 | Runtime Profile |-| `infrastructure` | Scheduler、Worker 与 Store 实现 | 持久化、调度 | Runtime Profile |+| `credential-store` | 解析被显式命名的凭据 | 密钥存储 | Runtime Profile |+| `result-repository` | 已结束的 Build Result | 项目历史存储 | 项目 `hypit.results.json` |+| `infrastructure` | Runtime Host、Scheduler 与 Worker 实现 | 持久化、调度 | 应用 Distribution || `application` | Studio Track Companion 等特定应用解释 | 仅该应用的 UI/操作 | 显式应用 profile |源码中的 `<import>` 只会 activate author facet。它绝不授予网络、文件系统、进程、凭据或队列权限。@@ -231,16 +233,18 @@ packages/example/## 包选择Hypit 不维护中央包注册表,也不维护自定义包锁。npm 或 pnpm 负责安装、版本与字节完整性。-系统只有两条显式选择路径:+每个所有者只有一条明确的选择路径:| 选择来源 | 被激活的包 ||---|---|+| 应用 Distribution | Runtime Host 与可信启动包 || Source import | Frontend、Surface、Producer、Validator |-| Runtime Profile 的 `use` | Runtime Host、基础设施与 Provider Endpoint |+| Runtime Profile 的 `credentials.*.use` / `endpoints.*.use` | Credential Store 与 Provider Endpoint |+| 项目 Result 配置的 `use` | 一个 Build Result Repository || Studio Profile 的 `companionPackages` | 当前 Studio 会话显式选择的项目 Companion 包 |Source import 绝不授予网络、文件系统、进程、凭据或队列权限;这些权限只属于 Runtime-Profile 显式选择的包。+Host 以及在环境边界被显式选择的包。### 逻辑包地址与 Source 发现@@ -257,12 +261,12 @@ Frontend 实现不是物理包格式里的特权字段。它们与 Run FragmentAdapter 一样,通过自己的 Host ABI 发布普通 facet;Frontend 使用`hypit.source-frontend@1`,只有 Source Host 会解释它。-Runtime Profile 也遵循同一规则。每个 `use` 选择的是 Runtime Host、Endpoint Adapter 或 Runtime-Infrastructure ABI 加逻辑名;物理 npm 包只负责声明它提供这个逻辑能力。通用 CLI 不维护-Provider 注册表;同名的 Endpoint Adapter 与 Runtime-Infrastructure Adapter 也不会互相冲突。+Runtime Profile 对它真正拥有的两种 facet 遵循同一规则:每个 `use` 只选择一个 Credential Store+或 Endpoint Adapter。项目 Result 配置独立选择一个 Repository;应用 Distribution 自己提供 Runtime+Host,不在该 Host 的 Profile 里重复伪造一次选择。通用 CLI 因而既不维护 Provider 注册表,也不写死+Result Repository;不同 Adapter 种类仍可使用相同逻辑名而不冲突。-加载器不会下载包,也不会扫描无关依赖来寻找插件。它只加载 Source 或 Runtime Profile+加载器不会下载包,也不会扫描无关依赖来寻找插件。它只加载 Source、环境配置或应用 Distribution明确选择的包,以及这些包 Manifest 精确声明的 Module 依赖。作者项目拥有独立目录以及自己的 Git/workspace 边界。它的显式项目包从项目自己的diff --git a/docs/zh/guide/runtime.md b/docs/zh/guide/runtime.mdindex 838fde2d..63fa6465 100644--- a/docs/zh/guide/runtime.md+++ b/docs/zh/guide/runtime.md@@ -5,9 +5,6 @@ description: Hypit Source 与 Core 之外的执行边界。# Runtime-实现审计与仍待处理的问题记录在-[Runtime 与 Build Result 实现审计](./runtime-build-result-audit.md)。-Hypit 把四个决定分开:| 所有者 | 决定什么 |@@ -141,12 +138,12 @@ Build id 精确读取仍能看见 Result draft。AWS SDK 使用它通常的凭证链;兼容服务还可以配置 `endpoint` 与 `forcePathStyle`。`prefix` 是项目边界,每个项目应使用自己的 prefix。S3 只改变完整 Build Result 的存放位置,不会把 Runtime-SQLite、Provider 容量或临时工作 Artifact 搬进 bucket。+SQLite、Provider 容量或活跃 Build 的临时 Resource 搬进 bucket。S3 adapter 会把有序 Build id 可逆地映射成“最新优先”的物理 prefix,因此对象存储可以直接返回有界的一页,不需要中央索引或重复 catalog。Result 文件支持按字节范围流式读取,因此 Studio 预览远端视频或音频时,不会先把完整文件装进内存。`hypit doctor [profile] --workspace <project>` 会同时主动-检查 Runtime 和项目选择的 Result Store;存储检查只做一次有上限的只读列表,不扫描历史 Result。+检查 Runtime 和项目选择的 Result Repository;存储检查只做一次有上限的只读列表,不扫描历史 Result。Workspace 独立由显式 `--workspace`、Runtime 指针所在项目或入口 Source 目录确定。Runtime 配置不能扩大源码读取范围。diff --git a/docs/zh/quickstart.md b/docs/zh/quickstart.mdindex bbe84ab2..4a08f418 100644--- a/docs/zh/quickstart.md+++ b/docs/zh/quickstart.md@@ -108,8 +108,8 @@ hypit plan build.svrun含有 `package.json` 的项目负责自己的第三方包;普通创作文件夹不需要成为 Node 项目,直接使用Distribution 里的官方包。默认情况下,完整 Build Result 位于项目的 `.hypit/results`;Profile-不管理 Result,项目根的 `hypit.results.json` 可以把同一套 Result 模型指向 S3。Runtime 活跃状态与临时 Artifact 始终位于所选 Profile 的-`dataRoot`。`runtime use` 只在 `.hypit/runtime` 保存一个本地指针。Source import 选择作者包,+不管理 Result,项目根的 `hypit.results.json` 可以把同一套 Result 模型指向 S3。Runtime 活跃状态与临时+Resource 始终位于所选 Profile 的 `dataRoot`。`runtime use` 只在 `.hypit/runtime` 保存一个本地指针。Source import 选择作者包,Profile 则通过 Credential Store 与 Endpoint 各自的 `use` 独立选择环境包。需要完整 Runtime Profile 时,从@@ -167,7 +167,7 @@ hypit runtime upRuntime 只会在机器 Program Home 中缺少托管环境时创建它,随后被所有项目和会话复用。不要在创作项目里手动执行服务的 `uv sync`。-修改 Runtime Profile 或项目 Result Store 后运行 `hypit doctor hypit.runtime.json`。它会报告缺少的工具、凭据和+修改 Runtime Profile 或项目 Result Repository 后运行 `hypit doctor hypit.runtime.json`。它会报告缺少的工具、凭据和Endpoint 配置,但不会执行作者图。## 接下来读什么diff --git a/docs/zh/quickstart/preview.md b/docs/zh/quickstart/preview.mdindex 954ee905..5196e40e 100644--- a/docs/zh/quickstart/preview.md+++ b/docs/zh/quickstart/preview.md@@ -17,7 +17,7 @@ hypit-studio --run examples/all-components-preview/studio.svrun --workspace .| 参数 | 含义 || --- | --- || `--run <build.svrun>` | 要打开的 Run Source。必填。 |-| `--runtime <hypit.runtime.json>` | 可选,只用于显示活动 `BuildView` 与 Operation;历史 Result 与 `<build-record>` 来自项目 Result Store。 |+| `--runtime <hypit.runtime.json>` | 可选,只用于显示活动 `BuildView` 与 Operation;历史 Result 与 `<build-record>` 来自项目 Result Repository。 || `--workspace <directory>` | Source 访问与写回边界;默认是 Run 所在目录。 || `--port <number>` | HTTP 端口,默认 `5179`。 |diff --git a/docs/zh/quickstart/run.md b/docs/zh/quickstart/run.mdindex 0268b0a8..91ce2e12 100644--- a/docs/zh/quickstart/run.md+++ b/docs/zh/quickstart/run.md@@ -5,7 +5,8 @@ description: 声明 Build 目标、复用结果以及配置运行时环境。# Run Source 与 Build-Author Source 定义视频本身。Run Source 从中挑选最终目标,以及是否用明确的 Candidate 来满足它们。Runtime Profile 则选择执行这份计划的机器、凭据、Provider Endpoint 与服务。+Author Source 定义视频本身。Run Source 从中挑选最终目标,以及是否用明确的 Candidate 来满足它们。+官方 Distribution 提供 Local Runtime;它的 Profile 声明执行这份计划可用的凭据、Provider Endpoint 与服务。先为项目选择一次 Runtime:@@ -174,9 +175,9 @@ Core 不再给 Candidate 标注 `exact` 或 `substitute`。选择 Candidate 本## Runtime Profile-Runtime Profile 选择 Build 在哪里执行。它通过逻辑 `use` 名称选择包、创建具名-Infrastructure 实例,再把实例暴露的 part 分配给 Runtime role,并配置 Provider endpoint 与-容量。Profile 不定义 Source Workspace 或 Author 包选择。+官方视频 Distribution 已经选择 Local Runtime。它的 Profile 通过逻辑 `use` 名称选择 Credential+Store 与 Endpoint,并配置 Endpoint 容量等部署参数;它不选择 Runtime Host,也不定义 Source+Workspace、Author 包或项目 Result Repository。```bashhypit runtime use hypit.runtime.json@@ -263,7 +264,7 @@ output/和公开 Output,媒体在 `files/`,结构化值在 `values/`。这是无需配置的默认 Result 仓库。项目根的 `hypit.results.json` 也可以选择 `@hypit/build-result-s3`;历史命令-与 `.svrun` 中的 `build-record` 会使用同一个仓库。Runtime 临时 Artifact 仍由 Runtime 在本地+与 `.svrun` 中的 `build-record` 会使用同一个仓库。活跃 Build 的临时 Resource 仍由 Runtime 在本地私有管理。`status`、`builds` 等只读归档命令不会在状态尚不存在时初始化 Runtime 数据库。@@ -277,7 +278,7 @@ hypit plan /work/my-film/build.svrun --asset-root /work/shared-media`--asset-root` 可重复使用,只授权读取素材字节,不允许从那里导入 `.svml/.svs` 源码。该 Host选项不进入作者或 Build 身份;真正进入图的是由该文件形成的显式 Resource 值。-Runtime Profile 只选择 Runtime 包与该 Runtime 的封闭配置。完整结构只在+Runtime Profile 只选择 Credential Store、Endpoint 及其封闭配置。完整结构只在[Runtime](../guide/runtime.md) 维护,不在 Quickstart 复制第二份。### 1. 选择 Runtime@@ -287,8 +288,8 @@ cd examples/talking-head-arollhypit runtime use hypit.runtime.json```-Author/Run Source 通过 import 选择作者包,Runtime Profile 通过 `use` 选择环境包;安装、版本-与完整性由 npm 或 pnpm 负责,不再需要同步另一份包库存。+Author/Run Source 通过 import 选择作者包;官方视频 Distribution 已经选择 Local Runtime,Profile+只通过 `use` 选择 Credential Store 与 Endpoint。安装、版本与完整性由 npm 或 pnpm 负责。### 2. 诊断环境@@ -296,7 +297,7 @@ Author/Run Source 通过 import 选择作者包,Runtime Profile 通过 `use`hypit doctor```-Doctor 总会校验项目选择的 Result Store;存在已选或显式传入的 Runtime Profile 时,还会校验全部+Doctor 总会校验项目选择的 Result Repository;存在已选或显式传入的 Runtime Profile 时,还会校验全部Runtime 角色、Endpoint 配置、凭据是否存在和有界环境探测。它不启动 Worker,也不发付费请求。存在 Profile 时,`doctor` 有意检查完整 Runtime Profile。若只想检查某次 Run 真正需要的环境,请使用带@@ -392,4 +393,4 @@ hypit runtime down`runtime down` 只会让 Worker 停止领取新 Build,并保留外部程序;只有确实要停掉这些程序时才执行 `programs down`。两条命令都不会取消耐久 Build 或远程 Provider 工作。再次启动同一-Profile 后,会继续其中尚未完成的执行。+Profile 后,会从已经接受的执行事实继续推进其中的活跃 Build。diff --git a/packages/build-result-kit/README.md b/packages/build-result-kit/README.mdindex aff2608b..c9eb046b 100644--- a/packages/build-result-kit/README.md+++ b/packages/build-result-kit/README.md@@ -1,8 +1,8 @@# `@hypit/build-result-kit`Host-facing package selection for project Build Result repositories. A Repository owns historical-Build manifests, public Outputs and their files. Runtime working Artifacts and active execution-state are separate concerns.+Build manifests, public Outputs and their Resource files. Temporary Resources and active execution+state belong to the Runtime implementation instead.The selected repository is opened before submission and its serializable location travels with theactive Build. A detached Worker therefore writes to the original destination even if the project'sdiff --git a/packages/build-result-s3/README.md b/packages/build-result-s3/README.mdindex 4d93a94d..7ce2febd 100644--- a/packages/build-result-s3/README.md+++ b/packages/build-result-s3/README.md@@ -1,8 +1,8 @@# `@hypit/build-result-s3`Opt-in S3-compatible repository for complete project Build Results. It stores Build manifests,-Composite Value Documents and public Resource files under one project prefix; Runtime working Artifacts remain local-to the selected Runtime implementation.+Composite Value Documents and public Resource files under one project prefix; an active Build's+temporary Resources remain with the selected Runtime implementation.```json{diff --git a/packages/cli/README.md b/packages/cli/README.mdindex af23a83e..f76d77a9 100644--- a/packages/cli/README.md+++ b/packages/cli/README.md@@ -3,13 +3,13 @@Domain neutral commands for checking, planning, building and inspecting Hypit projects.The command engine receives one explicit `CliDistribution`. A distribution supplies the compiler,-trusted bootstrap packages, source package discovery and the Runtime Host selected by a Runtime-Profile. The official video executable is assembled by `@hypit/video-cli`; another domain can-reuse this package without installing video packages.+trusted bootstrap packages, source package discovery and its Runtime Host. The official video+executable assembles the Local Runtime through `@hypit/video-cli`; another application may provide+another Host without changing this package or pretending that a local Profile selected it.-Source imports decide which language and component packages give the source meaning. The Runtime-Profile separately selects the Host and environment packages allowed to execute work. The CLI does-not invent targets, candidates or provider choices.+Source imports decide which language and component packages give the source meaning. A Local Runtime+Profile separately selects Credential Stores and Endpoints allowed to execute work. The CLI does not+invent targets, candidates or Provider choices.Human output is compact by default. `--json` emits a stable, bounded command view rather than rawcompiler, Runtime or Repository objects. `--verbose` adds bounded operational detail; it never turns@@ -21,6 +21,6 @@ browsing/export lives under `commands/results.ts`; Runtime,credential, package and deployment operations live under `commands/environment.ts`; active Buildobservation is read-only code in `observation.ts`; and human rendering is separate from the explicitmachine-view union. `main.ts` resolves project and selected Runtime context separately from parsed-syntax, then dispatches these command groups. Result commands do not consult or construct a Runtime,-and the generic CLI cannot silently choose a physical Result Store or a Provider-specific login+syntax, then routes these command groups. Result commands do not consult or construct a Runtime,+and the generic CLI cannot silently choose a Result Repository or a Provider-specific loginflow.diff --git a/packages/deck-track/README.md b/packages/deck-track/README.mdindex bde629ad..e0297df1 100644--- a/packages/deck-track/README.md+++ b/packages/deck-track/README.md@@ -36,7 +36,7 @@ Optional labels are separate exact-font values and are referenced by Cards. Filemedia metadata are never treated as label truth.The Surface projects every Card `at` and the deck terminal to `TemporalInstant` values before the-Deck component runs. Card append and finalization consume those Instants directly; they never locate+Deck component runs. Card append and completion consume those Instants directly; they never locatea Moment/Selection or manufacture a one-frame terminal Window internally.`deck:Label` accepts either literal body copy or `content={Text}`. It binds that copy to exact fontdiff --git a/packages/elaborator/README.md b/packages/elaborator/README.mdindex c4ad6981..beedadde 100644--- a/packages/elaborator/README.md+++ b/packages/elaborator/README.md@@ -49,7 +49,7 @@ identity, rejects conflicting media assignments for one written locator and foldinto Source Closure identity. It does not know whether a Host obtained the bytes from a filesystem,browser upload, repository object or remote content store.-Frontend output passes a Host-owned Record admission hook before linking. The hook is permitted to+Frontend output passes a Host-owned Record validation hook before linking. The hook is permitted toreject a Record but is forbidden to rewrite Record identity, Type or value.`@hypit/compiler-node` wires this to `@hypit/validation` by default, so authoredvalues use the same Type-owner gate as Producer, Provider and provided Candidate values.diff --git a/packages/media-pipeline/README.md b/packages/media-pipeline/README.mdindex e8fde4be..a51ce7b3 100644--- a/packages/media-pipeline/README.md+++ b/packages/media-pipeline/README.md@@ -76,7 +76,7 @@ WAV but makes no `SemanticTake`, speaker or alignment claim; it can therefore fereference port directly. Frame extraction supports `first`, `last`, `frame:<index>` and`time:<seconds>`. Transform operations are ordered author meaning and never an arbitrary FFmpeg string.-The same package also owns two provider-neutral finalization plans/capabilities:+The same package also owns two provider-neutral media completion plans/capabilities:```textComposition -> pure AudioProgramPlan -> render-timeline-audio Need -> TimelineAudiodiff --git a/packages/provider-hyperframes-aws-lambda/README.md b/packages/provider-hyperframes-aws-lambda/README.mdindex 8a9593da..543199f9 100644--- a/packages/provider-hyperframes-aws-lambda/README.md+++ b/packages/provider-hyperframes-aws-lambda/README.md@@ -19,7 +19,7 @@ configuration.On success the Endpoint requires HyperFrames' plan and completed-frame counts to equal the sourcedocument, then streams the returned S3 object into the current Build's working byte area.-The Runtime Profile selects the state machine and deployment settings. The Provider does not repeat+The Endpoint's Runtime Profile entry selects the AWS state machine and deployment settings. The Provider does not repeatthe request or selected endpoint as vendor metadata. Container and stream conformance stays in the explicit mediainspection/mux capabilities, so the orchestrating machine does not acquire a hidden FFmpegdependency.diff --git a/packages/provider-hyperframes-local/README.md b/packages/provider-hyperframes-local/README.mdindex 7a8be2ad..222a1e05 100644--- a/packages/provider-hyperframes-local/README.md+++ b/packages/provider-hyperframes-local/README.md@@ -4,8 +4,8 @@ Trusted local Provider for the `@hypit/render-hyperframes#render-visual` capabilResource dependencies declared by a `HyperframesDocument`, renders a silent MP4 with theHyperFrames CLI, probes the bytes, and returns a verified `RenderedVisual`. Before staging a typedSurface it decodes the exact bytes and checks declared dimensions, still/frame timing, SDR/sRGB and-opaque/straight-alpha facts. Artifact size and SHA-256 are checked for every dependency. These are-admission gates, not hidden output metadata.+opaque/straight-alpha facts. These checks validate the typed rendering input; they do not create+content identity or hidden output metadata.There are deliberately two concurrency controls:diff --git a/packages/provider-image-opencv-local/README.md b/packages/provider-image-opencv-local/README.mdindex d7d85330..12e474a1 100644--- a/packages/provider-image-opencv-local/README.md+++ b/packages/provider-image-opencv-local/README.md@@ -5,12 +5,12 @@ Local OpenCV/NumPy realization of the single `@hypit/raster` capability.Image Transform and Image Compose lower their different author meanings to one closed RasterRequest.One Handler stages its declared Resource inputs, and one Python interpreter shares decoding, fit,interpolation, alpha and encoding primitives across both variants. It runs in a bounded child process-and stores one new image Artifact. Temporary paths, OpenCV details and diagnostics stay inside the+and returns one new image Resource. Temporary paths, OpenCV details and diagnostics stay inside theEndpoint and never enter the image Product.The Distribution ships the frozen deployment source from `services/image-opencv`. With the RuntimeAdapter's declared configuration, `programs up` installs it only when the machine Program Home has nohealthy environment; the Endpoint, program probe and doctor all resolve the shared `.venv`interpreter. An explicit `pythonExecutable` selects an operator-managed compatible environment and-suppresses the managed installation. Runtime admission and-inner image work share the configured Endpoint pool/lane resources; no separate queue is hidden in this package.+suppresses the managed installation. The Endpoint call and+inner image work share the configured pool/lane resources; no separate queue is hidden in this package.diff --git a/packages/provider-kie/README.md b/packages/provider-kie/README.mdindex 9a50e0b4..23e949e8 100644--- a/packages/provider-kie/README.md+++ b/packages/provider-kie/README.md@@ -10,7 +10,7 @@ choose another model.It imports no exact-model package. Every supported Capability contributes one `KieRoute`: exactCapability, return Type, request compiler, media/count limits and result packer. All Routes share one-upload, admission, paid submission, durable Operation polling and download state machine. Model mappings+upload, paid submission, durable Operation polling, download and working-Resource write path. Model mappingsgenerate eleven Routes; Background Removal contributes the twelfth.## Supported catalog@@ -94,7 +94,7 @@ Manifests actually imported by the author document; installing KIE does not add3. Once a `taskId` exists, later Worker polling continues only that same task. Poll/download errors cannot create a newpaid generation.4. Successful result URLs are converted to short-lived download URLs, bounded while streaming,- immediately admitted into that Build's working byte area, and removed from durable+ immediately written into that Build's working byte area, and removed from durableresult metadata.5. The selected Runtime Execution Store owns shared Build capacity. This Provider contributes one KIEpool plus exact capability lanes and a conservative create-task interval; it does not introduce Redis or another source ofdiff --git a/packages/runtime-kit/README.md b/packages/runtime-kit/README.mdindex 35706055..5868b6c8 100644--- a/packages/runtime-kit/README.md+++ b/packages/runtime-kit/README.md@@ -1,14 +1,15 @@# `@hypit/runtime-kit`-Host facets for the three environmental choices a Runtime Profile may select:+Host facets for the two environmental choices a Local Runtime Profile may select:* an Endpoint implements external capabilities;-* an Artifact Store keeps generated bytes;* a Credential Store resolves explicit credential references.Each adapter is addressed by its kind and `use` name. A package advertises that name through a Hostfacet; the Runtime Profile selects it explicitly. Installing a package does not activate it.Endpoint activation returns one Endpoint and may also describe a Managed Program such as a warm local-WhisperX process. Store adapters validate configuration before opening a store. Runtime Kit knows no-Provider, filesystem, database or video package by name.+WhisperX process. Credential adapters validate configuration before opening a store. Active Resource+storage belongs to the Runtime implementation, while project Build Result repositories use the+separate `@hypit/build-result-kit` boundary. Runtime Kit knows no Provider, filesystem, database or+video package by name.diff --git a/packages/video-cli/README.md b/packages/video-cli/README.mdindex afd7f0f2..bcd333fd 100644--- a/packages/video-cli/README.md+++ b/packages/video-cli/README.md@@ -41,8 +41,8 @@ Source because an Author Graph without execution intent is not a Build. The livethe Script-owned deterministic CaptionDocument alongside real local/remote Endpoints; the CLI neverfabricates a Target, Candidate or missing fact.-`build` compiles one immutable Build Definition and passes it to the selected Runtime Profile with a fresh,-automatically assigned Build id. The id begins with its UTC creation time, so repository order is both+`build` compiles one immutable Build Definition and submits it to the configured Local Runtime with a+fresh, automatically assigned Build id. The id begins with its UTC creation time, so repository order is bothstable and visible; its random suffix prevents same-millisecond collisions and says nothing about content.Source or Plan identity never reclaims an earlier Build; reuseacross Builds exists only through explicit Run Source Candidates. JSON Profiles resolve only adapters in their separately