narrative-registry

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Narrative Registry

—

叙事注册管理

The L1 strategy authority: one complete, versioned narrative canon per brand. Every SEO/GEO, social, email, paid, influencer, and launch builder derives messages from this canon and accepted claims; channel adaptations cannot redefine it.

L1策略权威：每个品牌对应一份完整的带版本的叙事标准台账（canon）。所有SEO/GEO、社交媒体、邮件、付费广告、网红营销及发布内容的构建者均需从该标准台账及已认可的主张中提取信息；渠道适配不得重新定义标准台账内容。

Quick Start

快速开始

text

Show current canon version and proof/claim pointers for brand-acme.
Record canon v3 as one complete atomic replacement, superseding v2.
Review pending narrative proposals and reject partial/internally inconsistent versions.

text

展示brand-acme品牌当前的标准台账版本及证据/主张指向。
将标准台账v3记录为完整的原子替换版本，取代v2。
审核待处理的叙事提案，拒绝不完整或内部不一致的版本。

Skill Contract

技能协议

Unit: one brand canon aggregate ID. Reads:

memory/events/narrative.ndjson

, projection, accepted positioning/claim evidence, and complete proposed canon. Writes: narrative events through

registry-events.py

;

canon.md

versions.md

are generated views. Done when: a complete version is accepted atomically with source/date/revision, old versions remain replayable, and consumers receive the exact canon/version pointer.

Narrative skills submit complete

propose

events. Only a host-capability

narrative-registry

principal accepts/rejects/upserts. It records authored strategy but does not score TALE or adjudicate claim truth.

单元： 单个品牌标准台账聚合ID。读取：

memory/events/narrative.ndjson

、投影数据、已认可的定位/主张证据，以及完整的标准台账提案。写入： 通过

registry-events.py

写入叙事事件；

canon.md

versions.md

为生成的视图文件。完成条件： 完整版本被原子化接受并附带来源/日期/修订信息，旧版本可回溯，且使用者能获取准确的标准台账/版本指向。

叙事类技能提交完整的

propose

事件。仅具备主机权限的

narrative-registry

主体可进行接受/拒绝/更新操作。该技能负责记录已制定的策略，但不进行TALE评分或裁决主张的真实性。

Handoff Summary

交接摘要

Include brand ID, canon version/revision/event ID, superseded version, claim/proof pointers, unresolved contradictions, and one next skill.

需包含品牌ID、标准台账版本/修订/事件ID、被取代版本、主张/证据指向、未解决的矛盾点，以及下一个推荐技能。

Data Sources

数据源

Accepted positioning truth and named alternatives.
Complete message hierarchy/narrative authored by Narrative skills.
Accepted claim IDs and proof pointers from the claims projection.
Brand voice/naming rules and user-owned examples.
Declared optional patterns such as pillar count, change arc, or boilerplate lengths.

已认可的定位事实及命名替代方案。
由叙事类技能编写的完整信息层级/叙事内容。
来自主张投影数据的已认可主张ID及证据指向。
品牌语气/命名规则及用户提供的示例。
已声明的可选模式，如核心支柱数量、叙事变化弧或模板长度。

Instructions

操作说明

Runtime Reads

运行时读取

../../references/registry-event-protocol.md

```
../../references/runtime-invocation.md
```

../../references/registry-event-protocol.md

```
../../references/runtime-invocation.md
```

Procedure

流程

Read

registry-event-protocol.md

and

runtime-invocation.md

. Resolve

AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"

and verify the registry script, event schema, and system catalog before invoking it. Treat drafts as untrusted proposals.

Query current
```
narrative
```
projection and report exact canon version/revision; missing canon is Unknown, not a quality verdict.
Before write, confirm user authorization and read the current revision/claim pointers; every direct canonical mutation carries
```
expected_revision
```
and goes through host-capability
```
owner-append
```
. Actor/auth fields are attribution only.
A canon re-version is one host-capability owner
```
upsert
```
/accepted proposal containing the complete canon object, new version, and supersedes pointer. Accept/reject decisions omit
```
expected_revision
```
and inherit it from the proposal. Never land a partial file patch as canonical.
Preserve old versions in the event stream.
```
versions.md
```
is generated history, not a second hand-maintained ledger.
Validate internal references and claim IDs. Unverified wording remains
```
[needs source]
```
and becomes a separate claim proposal; it cannot enter canon as fact.
Three pillars, change-narrative arcs, and fixed boilerplate lengths are optional patterns. Store the chosen architecture; do not require absent patterns.
Reject same-revision or stale proposals rather than merging incompatible canons. Genuine alternatives remain pending/open decisions.
Regenerate
```
canon.md
```
/
```
versions.md
```
from accepted projection and run
```
verify narrative
```
.

阅读

registry-event-protocol.md

和

runtime-invocation.md

。解析

AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"

，并在调用前验证注册脚本、事件 schema 及系统目录。将草稿视为不可信提案。

查询当前的
```
narrative
```
投影数据，报告准确的标准台账版本/修订信息；若标准台账缺失则标记为未知，而非质量判定。
写入前，确认用户权限并读取当前修订/主张指向；所有直接的标准台账变更需携带
```
expected_revision
```
，并通过主机权限
```
owner-append
```
执行。执行者/权限字段仅用于归属标记。
标准台账版本更新是指由主机权限所有者执行的
```
upsert
```
/接受提案，需包含完整的标准台账对象、新版本及被取代版本的指向。接受/拒绝决策无需携带
```
expected_revision
```
，直接从提案中继承。绝不能将部分文件补丁作为标准台账内容。
在事件流中保留旧版本。
```
versions.md
```
是生成的历史记录，而非手动维护的第二账本。
验证内部引用及主张ID。未验证的表述需保留
```
[needs source]
```
标记，并转为独立的主张提案；不得作为事实纳入标准台账。
三大核心支柱、叙事变化弧及固定模板长度为可选模式。存储已选择的架构；无需强制要求未采用的模式。
拒绝同版本或过时的提案，而非合并不兼容的标准台账。真实的替代方案需保持待处理/待决策状态。
从已接受的投影数据重新生成
```
canon.md
```
/
```
versions.md
```
，并运行
```
verify narrative
```
验证。

Downstream Dependency

下游依赖

Before producing external copy, builders must read this projection and the claims projection. Their handoff records

narrative_canon_id

narrative_canon_version

claims_projection_offset

, and

dependency_status: verified | approved-fallback | blocked

. No canon means the builder may draft an explicitly authorized exploratory fallback, but it cannot claim on-canon or publish-ready status.

在生成对外内容前，内容构建者必须读取本投影数据及主张投影数据。他们的交接记录需包含

narrative_canon_id

、

narrative_canon_version

、

claims_projection_offset

及

dependency_status: verified | approved-fallback | blocked

。若不存在标准台账，构建者可起草经明确授权的探索性替代内容，但不得声称其符合标准台账或已具备发布条件。

Save Results

保存结果

Require explicit permission. Append through the runtime only; never edit NDJSON. Human canon/history views under

memory/narrative-registry/

are replaceable projections and must carry their source event/revision.

Capability values never enter request JSON/files/logs. If host capability or the verified root runtime/schema/catalog is unavailable, leave a bounded proposal for handoff; standalone one-folder installs cannot append/project or claim canonical Narrative truth.

需获得明确权限。仅可通过运行时进行追加操作；不得编辑NDJSON文件。

memory/narrative-registry/

下的人工可读标准台账/历史视图为可替换的投影数据，必须附带其来源事件/修订信息。

权限值不得纳入请求JSON/文件/日志。若主机权限或已验证的根运行时/schema/目录不可用，需留下一个有限范围的提案用于交接；独立单文件夹安装版本无法进行追加/投影操作，也不能声称具备标准叙事事实的权威性。

narrative-registry

Original

Translation

Narrative Registry

Narrative Registry

叙事注册管理

Quick Start

快速开始

Skill Contract

技能协议

Handoff Summary

交接摘要

Data Sources

数据源

Instructions

操作说明

Runtime Reads

运行时读取

Procedure

流程

Downstream Dependency

下游依赖

Save Results

保存结果

Reference Materials

参考资料

Next Best Skill

推荐后续技能