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: explain project file roles

kashorinf5703fb0f913
diff --git a/README.md b/README.md
index 39d40a6c..82a35304 100644
--- a/README.md
+++ b/README.md
@@ -127,17 +127,16 @@ A real Build additionally needs `ffmpeg` and `ffprobe` on your `PATH`, and depen
### Project files
-Narratage gives files distinct roles without reserving their names:
+Narratage separates authorship from execution:
-| Role | Usual form | How it is selected |
-|---|---|---|
-| **Author Source** | `.svml` | Passed to `check`, or referenced by a Run Source |
-| **Recipe Source** | `.svs` | Imported by another Source |
-| **Run Source** | `.svrun` | Passed to `plan` or `build` |
-| **Runtime Profile** | JSON | Passed explicitly with `--runtime` |
-| **Package inventories** | JSON lock files | Referenced by a Runtime Profile or selected explicitly by the CLI |
+| File | What it decides |
+|---|---|
+| `.svml` | What video to make, including the script, generated media and tracks |
+| `.svs` | Reusable creative choices such as prompts, styles and layout |
+| `.svrun` | What to build this time, including targets and prior results to reuse |
+| Runtime profile | How and where to run, including providers, storage and concurrency |
-Names and suffixes are conventions, not parser dispatch. Every Source selects its own Frontend with a `<?svml using="..."?>` header; Runtime Profiles and package inventories are selected by explicit paths. A project may contain any number of each role, and one Author Source may be referenced by many Run Sources.
+A project can have any number of these files, and the same `.svml` can be built by many `.svrun` files.
## Where the name comes from
@@ -149,7 +148,7 @@ Ninety years later, Narratage gives the same idea a new form: a language and sys
AI generation is slow, costly and non-deterministic. Narratage compiles requested work into a durable plan.
-The Core is small and domain-neutral—it knows nothing about video. Installing a package adds capability without requiring a Core release.
+The Core is small and domain-neutral: it knows nothing about video. Installing a package adds capability without requiring a Core release.
| Layer | What it owns | Examples |
|---|---|---|
diff --git a/README.zh-CN.md b/README.zh-CN.md
index 976d68e2..af95c553 100644
--- a/README.zh-CN.md
+++ b/README.zh-CN.md
@@ -119,17 +119,16 @@ node --run narratage -- plan examples/talking-film-graph-check/build.svrun \
### 项目文件
-Narratage 为文件规定不同的角色,但不保留任何固定文件名:
+Narratage 把创作与执行分开:
-| 角色 | 常用形式 | 如何选中 |
-|---|---|---|
-| **Author Source** | `.svml` | 直接传给 `check`,或由 Run Source 引用 |
-| **Recipe Source** | `.svs` | 被另一份 Source 导入 |
-| **Run Source** | `.svrun` | 传给 `plan` 或 `build` |
-| **Runtime Profile** | JSON | 通过 `--runtime` 显式传入 |
-| **包清单** | JSON lock 文件 | 由 Runtime Profile 引用,或通过 CLI 显式选择 |
+| 文件 | 决定什么 |
+|---|---|
+| `.svml` | 制作什么视频,包括稿件、生成素材和轨道 |
+| `.svs` | 可复用的创作选择,例如 prompt、样式和布局 |
+| `.svrun` | 本次构建什么,包括 Target 和需要复用的历史产物 |
+| Runtime Profile | 在哪里、以何种方式运行,包括 Provider、存储和并发 |
-名称与后缀只是约定,不参与解析器分发。每份 Source 都通过 `<?svml using="..."?>` Header 选择自己的 Frontend;Runtime Profile 与包清单则通过显式路径选择。一个项目可以拥有任意数量的这些文件,同一份 Author Source 也可以被多份 Run Source 引用。
+一个项目可以包含任意数量的这些文件,同一份 `.svml` 也可以由多份 `.svrun` 构建。
## 名字的由来
@@ -141,7 +140,7 @@ Narratage 为文件规定不同的角色,但不保留任何固定文件名:
AI 生成缓慢、昂贵且不确定。Narratage 把所需工作编译为一份持久化计划。
-Core 极小且领域无关——它不认识视频。安装一个包即可增加能力,无需重新发布 Core。
+Core 极小且领域无关:它不认识视频。安装一个包即可增加能力,无需重新发布 Core。
| 层 | 负责什么 | 例子 |
|---|---|---|