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: sharpen the architecture overview
kashorin7b32fdde0f49
diff --git a/README.md b/README.mdindex 3af9925a..341d4100 100644--- a/README.md+++ b/README.md@@ -147,22 +147,21 @@ Ninety years later, Narratage gives the same idea a new form: a language and sys## Architecture-AI generation changes the shape of compilation. A step may take minutes, cost money, fail, or return an artifact that becomes the next step's input. Build truth therefore cannot live on a process stack: Narratage freezes the demanded work first, then advances it from durable facts.+AI generation is slow, costly and non-deterministic. Narratage freezes requested work into a finite plan, then advances it from durable state. A build can pause, retry or change implementations without losing completed artifacts or repeating paid work.-Core is a domain-neutral semantic kernel with two jobs: compile Targets and explicit Candidate choices into one finite BuildPlan, then accept Events and advance BuildState. At execution time, its irreducible law is `BuildState + Event → BuildState`; ready Commands are regenerated from that state. Core never parses Source, executes component code, accesses files or networks, chooses a Provider, changes a Candidate, or understands video concepts.+At the center is a deliberately small, domain-neutral Core. It compiles requested outputs and explicit implementation choices into a plan, accepts execution events and decides what becomes ready next. It does not parse SVML, understand video, call providers, access credentials or render frames.-| Part | What it owns | Why it stays outside Core |+| Part | What it owns | Examples ||---|---|---|-| **Compiler Host & Frontends** | Source Headers, import closure, syntax decoding and Author/Run Graph compilation | Syntax and Source environments can evolve independently |-| **Author facets** | Surfaces, author vocabulary and Graph Fragments | New authoring capabilities should not require a kernel release |-| **Compute facets** | Deterministic Producers and Validators | Domain computation should remain independently installable |-| **Runtime facets** | Scheduler, Worker, Stores, credentials and transports | Deployment, persistence and authority vary by environment |-| **Endpoint facets** | Model APIs, local programs, Lambda functions, devices and human services | External capabilities have their own concurrency, failure and recovery laws |-| **Applications** | CLI, Playgrounds and product interfaces | User experience must not become a central capability registry |--A physical package may contribute one or more facets. Source imports activate authoring meaning without granting filesystem, network, process or credential authority; privileged Endpoint and Runtime facets are selected explicitly by the Runtime Profile.--Neither Core nor the CLI maintains a central registry of models, Tracks or Providers. Installing and locking a package adds its capability without requiring a Core release.+| **Core** | Plan compilation and the Build state machine | `core`, `protocol` |+| **Compiler** | Source parsing, imports and graph elaboration | `host`, `markup`, `svs`, `elaborator` |+| **Shared capabilities** | Media processing, spatial layout, fonts and text | `media-pipeline`, `spatial`, `fonts-open` |+| **Video packages** | Script, generation, speech, tracks, film and rendering | `script`, `seedance`, `caption`, `film` |+| **Providers** | Adapters for external models, programs and services | `provider-kie`, `provider-whisperx-local` |+| **Runtime** | Scheduling, storage, credentials and execution | `runtime`, `store-sqlite`, `local` |+| **Applications** | User-facing ways to author and operate Narratage | `cli`, `svml-playground` |++SVML imports define what the source means. The Runtime Profile separately selects packages that may access files, networks and credentials. Neither Core nor the CLI maintains a central registry of models, tracks or providers: installing a package adds capability without requiring a Core release.## Where to go nextdiff --git a/README.zh-CN.md b/README.zh-CN.mdindex 158c6906..0151b674 100644--- a/README.zh-CN.md+++ b/README.zh-CN.md@@ -139,22 +139,21 @@ Narratage 为文件规定不同的角色,但不保留任何固定文件名:## 架构-AI 生成改变了编译的形态。一项工作可能运行数分钟、明确产生费用、发生失败,或返回一个成为下一步输入的产物。因此,Build 的真实状态不能存在进程调用栈里:Narratage 先冻结被需要的工作,再依据持久化事实推进它。+AI 生成缓慢、昂贵且不确定。Narratage 把被要求的工作冻结为一份有限计划,再依据持久化状态推进。Build 可以暂停、重试或更换实现,而不会丢失已完成的产物,也不会重复执行已经付费的工作。-Core 是一个领域无关的语义内核,只做两件事:把 Target 和显式 Candidate 选择编译为一份有限的 BuildPlan;接受 Event 并推进 BuildState。执行阶段不可再约简的规则是 `BuildState + Event → BuildState`,下一批可运行的 Command 始终从该状态重新生成。Core 不解析 Source,不执行组件代码,不访问文件或网络,不选择 Provider,不更改 Candidate,也不理解任何视频概念。+系统中心是一个刻意保持极小、领域无关的 Core。它把被要求的输出和显式选择的实现编译为计划,接受执行事件,并决定下一步哪些工作可以运行。它不解析 SVML,不理解视频,不调用 Provider,不访问凭据,也不渲染画面。-| 部分 | 负责什么 | 为什么留在 Core 外 |+| 部分 | 负责什么 | 例子 ||---|---|---|-| **Compiler Host 与 Frontend** | Source Header、导入闭包、语法解码,以及 Author/Run Graph 编译 | 语法和 Source 所处环境可以独立演进 |-| **Author facet** | Surface、作者词汇与 Graph Fragment | 新的作者能力不应要求发布内核 |-| **Compute facet** | 确定性的 Producer 与 Validator | 领域计算应当可以独立安装 |-| **Runtime facet** | Scheduler、Worker、Store、凭据与 transport | 部署、持久化和权限随环境而变化 |-| **Endpoint facet** | 模型 API、本地程序、Lambda、设备与人工服务 | 外部能力各有自己的并发、失败与恢复规则 |-| **Application** | CLI、Playground 与产品界面 | 用户体验不能变成中央能力注册表 |--一个物理包可以贡献一种或多种 facet。Source 导入只激活作者语义,不授予文件系统、网络、进程或凭据权限;拥有特权的 Endpoint 与 Runtime facet 必须由 Runtime Profile 显式选择。--Core 与 CLI 都不维护模型、Track 或 Provider 的中央注册表。安装并锁定一个包即可加入它提供的能力,无需重新发布 Core。+| **Core** | 计划编译与 Build 状态机 | `core`、`protocol` |+| **编译器** | Source 解析、导入与图展开 | `host`、`markup`、`svs`、`elaborator` |+| **共享能力** | 媒体处理、空间布局、字体与文本 | `media-pipeline`、`spatial`、`fonts-open` |+| **视频包** | 稿件、生成、语音、Track、Film 与渲染 | `script`、`seedance`、`caption`、`film` |+| **Provider** | 外部模型、程序与服务的适配器 | `provider-kie`、`provider-whisperx-local` |+| **Runtime** | 调度、存储、凭据与执行 | `runtime`、`store-sqlite`、`local` |+| **应用** | 创作和操作 Narratage 的用户界面 | `cli`、`svml-playground` |++SVML 的导入决定 Source 表达什么;Runtime Profile 另外选择可以访问文件、网络和凭据的包。Core 与 CLI 都不维护模型、Track 或 Provider 的中央注册表:安装一个包即可增加能力,无需重新发布 Core。## 接下来去哪