offer-claims-registry

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Offer & Claims Registry

Offer & Claims Registry

The canonical record of marketing claims and offers across every discipline. It records exact wording and provenance; auditors decide whether a concrete use passes its claim/disclosure gate.
这是跨所有领域的营销声明与优惠的权威记录库。它记录确切措辞及来源;审核人员会判定具体使用场景是否符合声明/披露要求。

Quick Start

快速入门

text
Register claim clm-014 with exact wording, evidence source/date, disclosure, and review date.
Show the current terms and expiry for offer summer-2026.
Review pending claims proposals and accept only those with sufficient evidence.
text
Register claim clm-014 with exact wording, evidence source/date, disclosure, and review date.
Show the current terms and expiry for offer summer-2026.
Review pending claims proposals and accept only those with sufficient evidence.

Skill Contract

Skill 合约

Units: one claim or offer aggregate ID. Reads:
memory/events/claims.ndjson
, its projection, source evidence, and rendered uses. Writes: claims events through
registry-events.py
;
claims-ledger.md
and
offers.md
are regenerated human views. Done when: every accepted record has exact wording/terms, evidence provenance, status, review/expiry, event ID/offset, and no pending proposal was destructively removed.
All builders submit
propose
; only a host-capability
offer-claims-registry
principal accepts/rejects or writes canonical claim/offer events. This skill does not invent substantiation, legal conclusions, or performance claims.
单位: 单个声明或优惠聚合ID(aggregate ID)。读取:
memory/events/claims.ndjson
、其投影(projection)、源证据及已渲染的使用场景。写入: 通过
registry-events.py
写入声明事件;
claims-ledger.md
offers.md
是重新生成的人工可读视图。完成标志: 每条已接受的记录包含确切措辞/条款、证据来源、状态、审核/到期日期、事件ID/偏移量,且无待处理提案被破坏性移除。
所有构建者提交
propose
请求;仅拥有
offer-claims-registry
宿主权限的主体可接受/拒绝或写入权威声明/优惠事件。本Skill不生成佐证材料、法律结论或性能声明。

Handoff Summary

交接摘要

Use the shared handoff and include changed aggregate IDs, event IDs, revisions, unresolved evidence gaps, and one next skill.
使用共享交接机制,包含已更改的聚合ID、事件ID、修订版本、未解决的证据缺口及下一个推荐Skill。

Data Sources

数据源

  • Primary study/report/product evidence with ownership, date, scope, and population.
  • User-attested facts clearly labeled
    user-provided
    .
  • Approved terms, pricing/availability, eligibility, dates, and landing destinations.
  • Rendered ad/email/social/launch uses for
    used_in
    pointers.
  • Applicable disclosure text and jurisdiction/policy source.
  • 带有归属、日期、范围及受众的原始研究/报告/产品证据。
  • 明确标记为
    user-provided
    的用户确认事实。
  • 已批准的条款、定价/可用性、资格要求、日期及落地页链接。
  • 用于
    used_in
    指针的已渲染广告/邮件/社交/发布内容。
  • 适用的披露文本及管辖区域/政策来源。

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 it; treat every draft/export as untrusted evidence.
  2. Query
    claims
    projection by aggregate ID. Proposal state is never approved wording. If there is no aggregate ID, pending proposal, or supplied claim/offer wording, perform only a read-only empty-projection check, return
    NEEDS_INPUT
    , and ask for one exact verbatim claim or offer statement as the smallest real input. Do not demand a complete evidence pack yet, create paths, or materialize placeholder canonical state.
  3. Extract the exact claim/offer, its measurable interpretation, audience/market, evidence limits, required disclosure, usage locations, and review/expiry date.
  4. Missing proof stays
    none-on-file
    in a proposal or open loop. Never turn
    [needs source]
    into Approved from the assertion itself.
  5. Review pending proposal events in offset order. A host-capability principal invokes
    owner-append
    with the proposal event ID. Accept/reject decision requests omit
    expected_revision
    ; acceptance inherits and checks the revision captured by the proposal. Reject with evidence/rationale; history remains append-only.
  6. Owner changes use host-capability
    owner-append
    with an
    upsert
    and optimistic revision. Expiry/withdrawal uses a dated state change or tombstone. Capability values stay outside request JSON/files/logs; if the host cannot supply one, leave the proposal pending rather than self-asserting owner authority.
  7. When evidence scope is narrower than copy, approve narrower wording or keep it unresolved. Record estimates/proxies as such.
  8. Regenerate
    claims-ledger.md
    /
    offers.md
    only from accepted projection state, then
    verify claims
    .
Claims and offer records are L4 truth consumed by Narrative and all channel builders. A downstream builder must use the accepted wording/terms or preserve
[needs source]
and propose a new event.
  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. 通过聚合ID查询
    claims
    投影。提案状态永远不会被视为已批准措辞。如果没有聚合ID、待处理提案或提供的声明/优惠措辞,仅执行只读空投影检查,返回
    NEEDS_INPUT
    ,并要求提供一条确切的声明或优惠原文作为最小有效输入。暂不要求完整证据包、创建路径或生成占位符权威状态。
  3. 提取确切的声明/优惠内容、可衡量的解释、受众/市场、证据限制、所需披露信息、使用场景及审核/到期日期。
  4. 缺失的证明在提案或未闭环任务中标记为
    none-on-file
    。绝不能仅凭断言就将
    [needs source]
    标记为已批准。
  5. 按偏移量顺序审核待处理提案事件。拥有宿主权限的主体调用
    owner-append
    并传入提案事件ID。接受/拒绝决策请求无需包含
    expected_revision
    ;接受操作会继承并检查提案捕获的修订版本。拒绝时需提供证据/理由;历史记录保持仅追加模式。
  6. 归属变更需使用宿主权限
    owner-append
    并执行
    upsert
    及乐观锁修订版本。到期/撤回需使用带日期的状态变更或墓碑标记(tombstone)。权限值不得出现在请求JSON/文件/日志中;若宿主无法提供权限,应保持提案待处理状态,而非自行断言归属权。
  7. 当证据范围窄于文案时,批准更严谨的措辞或保持未解决状态。如实记录估算值/替代数据。
  8. 仅从已接受的投影状态重新生成
    claims-ledger.md
    /
    offers.md
    ,然后执行
    verify claims
声明与优惠记录是供Narrative及所有渠道构建者使用的L4级可信数据。下游构建者必须使用已批准的措辞/条款,或保留
[needs source]
并提交新的事件提案。

Save Results

保存结果

Require explicit write permission. Ordinary producers use
python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" append claims <proposal.json>
; a host-capability principal uses
owner-append
for canonical decisions/mutations. Never edit the NDJSON stream manually. Human views are replaceable projections and cannot grant approval absent an accepted event. Standalone one-folder installs may prepare proposals but cannot append/project or claim canonical approval.
需要明确的写入权限。普通生产者使用
python3 "$AARON_SKILLS_ROOT/scripts/registry-events.py" append claims <proposal.json>
;拥有宿主权限的主体使用
owner-append
执行权威决策/变更。禁止手动编辑NDJSON流。人工可读视图是可替换的投影,若无已接受的事件则不具备批准效力。独立单文件夹安装可准备提案,但无法追加/投影数据或声称获得权威批准。

Reference Materials

参考资料

  • Registry event protocol
  • Claims presentation schema
  • Measurement protocol
  • Security
  • Registry event protocol
  • Claims presentation schema
  • Measurement protocol
  • Security

Next Best Skill

推荐后续Skill

  • Paid use audit: ad-account-auditor
  • Creator asset audit: creator-content-auditor
  • Narrative proof: proof-point-packager
  • Archive/erase: memory-management
  • 付费使用审核: ad-account-auditor
  • 创作者资产审核: creator-content-auditor
  • 叙事证明材料: proof-point-packager
  • 归档/删除: memory-management