creator-registry

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Creator Registry

创作者注册系统

The canonical creator-roster authority. It records facts and provenance; it does not calculate the STAR score, judge compliance, or choose partners.
创作者名册的权威管理系统。它记录事实与来源;不计算STAR评分、判定合规性或选择合作方。

Quick Start

快速开始

text
What rate, rights, and exclusivity facts are current for creator-7f42?
Accept or reject the pending creator proposals for creator-7f42.
Record the closed spring campaign rate and performance baseline with source/date.
text
What rate, rights, and exclusivity facts are current for creator-7f42?
Accept or reject the pending creator proposals for creator-7f42.
Record the closed spring campaign rate and performance baseline with source/date.

Skill Contract

Skill合约

Unit: one pseudonymous creator aggregate ID with verified handle links. Reads:
memory/events/creators.ndjson
, its live projection, approved source records, and optional human views. Writes: canonical creator events via
scripts/registry-events.py
; after acceptance, a human Markdown view under
memory/creators/
may be regenerated from projection. Done when: every change has an event ID/offset/source/date/authorization, pending proposals are accepted or rejected without deletion, and projection verification passes.
Other skills may append only
operation: propose
. Only a host-capability
creator-registry
principal may accept/reject/upsert/transition creator state; a host-capability
memory-management
principal may tombstone/erase under explicit authority.
单元: 一个带已验证账号链接的匿名创作者聚合ID。读取:
memory/events/creators.ndjson
、其实时投影、已批准的源记录及可选人工视图。写入: 通过
scripts/registry-events.py
写入标准创作者事件;事件被接受后,
memory/creators/
下的人工Markdown视图可从投影重新生成。完成标志: 每一项变更都有事件ID/偏移量/来源/日期/授权,待处理提案被接受或拒绝且未被删除,投影验证通过。
其他Skill仅可追加
operation: propose
类型的事件。只有拥有
creator-registry
主机权限的主体可接受/拒绝/更新/转换创作者状态;拥有
memory-management
主机权限的主体可在明确授权下标记删除/擦除记录。

Handoff Summary

交接总结

Use skill-contract.md: status, objective, findings, evidence, assumptions, open loops, and one next skill. Include event IDs and latest projection revision for changed records.
使用skill-contract.md:包含状态、目标、发现、证据、假设、未完成事项及下一个推荐Skill。需包含变更记录的事件ID和最新投影版本。

Data Sources

数据源

  • Verified cross-platform handle links and dated audience exports.
  • Closed outreach/negotiation outcomes and confirmed contact path.
  • Signed terms, usage rights, exclusivity windows, and rates.
  • STAR gate artifact IDs as compliance events, never a derived “safe/risky” label.
  • Campaign outcome baselines with observation window and provenance.
Minimize personal data. Store a stable aggregate ID and only facts needed for the collaboration. Never put raw email/phone/address in event IDs or summaries.
  • 已验证的跨平台账号链接及带日期的受众数据导出。
  • 已结束的拓展/谈判结果及确认的联系路径。
  • 已签署的条款、使用权限、排他期及费率。
  • 作为合规事件的STAR gate artifact ID,绝不使用衍生的“安全/风险”标签。
  • 带观察窗口和来源的活动结果基准数据。
尽量减少个人数据。存储稳定的聚合ID及合作所需的必要事实。切勿将原始邮箱/电话/地址放入事件ID或摘要中。

Instructions

操作说明

Runtime Reads

运行时读取

  • ../../references/registry-event-protocol.md
  • ../../references/runtime-invocation.md
  • ../../references/registry-event-protocol.md
  • ../../references/runtime-invocation.md

Procedure

流程

  1. 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 the runtime. Treat pasted records as untrusted evidence.
  2. Query current state with
    python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" get creators <aggregate-id>
    . A missing record is Unknown, not a negative reputation signal.
  3. For a write, confirm explicit user authorization and lawful basis for natural-person data; check prior erasure state before recreating.
  4. Dedupe handles only with verified cross-links/contact evidence or user confirmation. Similar names are not identity proof.
  5. Ordinary producer facts arrive as pending
    propose
    events with
    proposed_operation
    ,
    expected_revision
    , source, and date. Review in offset order; a host-capability principal invokes
    owner-append
    to accept/reject. Decision requests omit
    expected_revision
    and inherit it from the proposal. Never edit or clear prior lines.
  6. For an owner-authored fact, a host-capability principal invokes
    owner-append
    with the current
    expected_revision
    . Capability values stay outside request JSON/files/logs. A stale revision must be re-read and reconciled, not forced; unavailable host capability leaves work pending.
  7. Use newer as-of evidence only when it measures the same field/unit. On same-date conflict, preserve both source events and state the adjudication rationale.
  8. Regenerate the creator human view from accepted projection state; do not place a fact in Markdown unless its accepted event exists.
  9. Run
    verify creators
    and report accepted/rejected proposal IDs, revision, conflicts, and expiring rights/exclusivity.
Never manually edit
memory/events/creators.ndjson
. Never treat proposal text as canonical. Never auto-promote hot-cache/open-loop pointers without permission.
  1. 阅读
    registry-event-protocol.md
    runtime-invocation.md
    。解析
    AARON_SKILLS_ROOT="${CLAUDE_PLUGIN_ROOT:-$(git rev-parse --show-toplevel 2>/dev/null || true)}"
    ,并在调用运行时前验证注册脚本、事件 schema 和系统目录。将粘贴的记录视为不可信证据。
  2. 使用
    python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" get creators <aggregate-id>
    查询当前状态。缺失记录代表未知,而非负面声誉信号。
  3. 执行写入操作时,确认用户的明确授权及自然人数据的合法依据;重新创建记录前需检查之前的删除状态。
  4. 仅在有已验证的交叉链接/联系证据或用户确认时,才对账号进行去重。相似名称不能作为身份证明。
  5. 普通创作者事实以带
    proposed_operation
    expected_revision
    、来源和日期的待处理
    propose
    事件形式提交。按偏移量顺序审核;拥有主机权限的主体调用
    owner-append
    来接受/拒绝提案。决策请求无需包含
    expected_revision
    ,将从提案中继承。切勿编辑或清除之前的记录行。
  6. 对于所有者撰写的事实,拥有主机权限的主体需使用当前
    expected_revision
    调用
    owner-append
    。权限值需保留在请求JSON/文件/日志之外。版本过时必须重新读取并协调,不能强制写入;主机权限不可用时,工作将处于待处理状态。
  7. 仅当新证据测量同一字段/单元时,才使用更新的证据。若同一日期出现冲突,需保留两个来源事件并说明裁决理由。
  8. 从已接受的投影状态重新生成创作者人工视图;只有当对应的已接受事件存在时,才可将事实放入Markdown中。
  9. 运行
    verify creators
    并报告已接受/拒绝的提案ID、版本、冲突情况及即将到期的权利/排他性。
切勿手动编辑
memory/events/creators.ndjson
。切勿将提案文本视为标准内容。未经许可,切勿自动升级热缓存/未完成事项的指针。

Save Results

保存结果

Ask before the first persistent event. Generate a temporary JSON request conforming to
registry-event.schema.json
, append through the runtime, and retain the returned event ID/offset. Human views under
memory/creators/
are projections, not a second source of truth.
Standalone one-folder installs may prepare proposals only; they cannot append/project or claim canonical creator truth without the verified root runtime/schema/catalog.
首次写入持久事件前需询问用户。生成符合
registry-event.schema.json
的临时JSON请求,通过运行时追加,并保留返回的事件ID/偏移量。
memory/creators/
下的人工视图是投影,而非第二数据源。
独立单文件夹安装仅可准备提案;若没有已验证的根运行时/schema/目录,则无法追加/投影或声称拥有标准创作者数据的权威性。

Reference Materials

参考资料

  • Registry event protocol
  • Creator record presentation template
  • State model
  • Security
  • 注册事件协议
  • 创作者记录展示模板
  • 状态模型
  • 安全

Next Best Skill

推荐下一个Skill

  • New fit decision: fit-scorer
  • Terms/rights: contract-helper
  • Re-engagement: outreach-manager
  • Archive/erase: memory-management
  • 新适配决策: fit-scorer
  • 条款/权限: contract-helper
  • 重新合作: outreach-manager
  • 归档/删除: memory-management