launch-readiness-auditor

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Launch Readiness Auditor

发布就绪审计器

Audit one launch at one lifecycle read. Preflight evaluates readiness/assets plus planned policy and instrumentation red lines; execution evaluates observed launch-window operation; outcome evaluates post-lag proof. There is no cross-time composite.

针对单个生命周期阶段审核一次发布。预检查阶段评估就绪情况/资产以及计划的策略和监控红线；执行阶段评估发布窗口期的实际操作情况；结果阶段评估延迟后的验证数据。不支持跨时间阶段的复合评估。

When This Must Trigger

触发场景

Before a committed launch/announcement when go/no-go evidence is needed.
During/after the launch window when execution quality must be assessed.
After the declared lag when actual outcomes and learnings are reviewed.

在已确定的发布/公告前，需要决策是否可以发布时。
在发布窗口期期间/之后，需要评估执行质量时。
在声明的延迟期过后，需要回顾实际结果和经验教训时。

Quick Start

快速开始

text

Run RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA.
Run the outcome profile at day 30; keep it separate from the preflight result.

text

Run RAMP preflight for launch alpha against the registry stage, canon, claims, rules, and event QA.
Run the outcome profile at day 30; keep it separate from the preflight result.

Skill Contract

技能约定

Reads: one launch, one lifecycle read, registry/canon/claims state, and profile-specific evidence. Writes: only a permissioned v3 artifact. Done when: the selected profile is complete or its exact Unknowns are reported, with no launch execution or registry mutation.

launch-registry

owns stage/date/embargo facts.

launch-day-conductor

executes the runbook. This auditor only judges the frozen evidence.

读取： 单个发布、单个生命周期阶段数据、registry/canon/claims状态，以及对应配置文件的特定证据。写入： 仅写入受权限控制的v3版本工件。完成条件： 所选配置文件执行完成，或报告其明确的未知项，且不会修改发布执行状态或registry。

launch-registry

负责阶段/日期/embargo事实。

launch-day-conductor

负责执行运行手册。本审计器仅对已固化的证据进行评判。

Data Sources

数据源

Need	Preferred evidence
Stage/access	Projected launch record plus direct access/eligibility check
Narrative/claims	Canon version, claims projection, rendered assets
Operations/rules	Launch plan, commitments, dated official platform rules
Instrumentation	Verified events/UTMs and destination truth checks
Execution	Timestamped action/incident/response evidence
Outcomes	Own analytics/CRM/store truth after declared lag

需求	首选证据
阶段/访问权限	预计发布记录加上直接访问/资格检查
说明/声明	Canon版本、声明预测、已渲染资产
操作/规则	发布计划、承诺、带日期的官方平台规则
监控	已验证的事件/UTM以及目标端真实性检查
执行	带时间戳的操作/事件/响应证据
结果	声明延迟期过后的自有分析/CRM/商店真实数据

Instructions

操作说明

Runtime Reads

运行时读取

```
../../../references/auditor-runbook.md
```

../../../references/scoring-semantics.md

```
../../../references/ramp-benchmark.md
```

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

```
references/auditor-runtime.md
```

```
../../../references/auditor-runbook.md
```

../../../references/scoring-semantics.md

```
../../../references/ramp-benchmark.md
```

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

```
references/auditor-runtime.md
```

Runtime and Setup

运行时与设置

Read

../../../references/auditor-runbook.md

scoring-semantics.md

ramp-benchmark.md

, and the RAMP catalog entry. Standalone installs use bundled immutable

references/auditor-runtime.md

; never fetch mutable

main

. Before deterministic calls, follow

runtime-invocation.md

, resolve

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

, and require the scorer, validator, and typed catalogs. If unavailable, return

score_state: NOT_SCORED

score_confidence: not_scored

with no gate verdict or persistent artifact.

Declare profile/lifecycle read (

preflight|execution|outcome

), target launch, launch type, market, access model, observation date, and evidence window.

阅读

../../../references/auditor-runbook.md

、

scoring-semantics.md

、

ramp-benchmark.md

以及RAMP目录条目。独立安装使用捆绑的不可变

references/auditor-runtime.md

；切勿获取可变的

main

分支内容。在进行确定性调用前，请遵循

runtime-invocation.md

，解析

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

，并引入评分器、验证器和指定类型的目录。如果无法获取这些资源，返回

score_state: NOT_SCORED

score_confidence: not_scored

，不提供决策结论或持久化工件。

声明配置文件/生命周期阶段（

preflight|execution|outcome

）、目标发布、发布类型、市场、访问模型、观察日期和证据窗口。

Profile Procedure

配置文件流程

Preflight: score R1–R10, A1–A10, planned M1, and P1. A public pricing page is required only when the declared access model promises public paid availability.
Execution: score observed M1–M10; do not substitute planned runbook quality for actual execution.
Outcome: score P2–P10 after the declared lag; do not backfill forecast targets as actuals.

Every observed state needs source/date/type/confidence. Missing applicable evidence is Unknown; catalog-authorized conditional items may be N/A with reason. Run

python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json>

on the selected typed profile.

Verify profile-relevant vetoes:

RAMP-R1

stage/access contradiction,

RAMP-A1

material claim/disclosure failure,

RAMP-M1

planned or observed manipulation/embargo/platform violation, and

RAMP-P1

demonstrably broken instrumentation on participating surfaces.

预检查： 评分R1–R10、A1–A10、计划中的M1和P1。只有当声明的访问模型承诺公开付费可用时，才需要公开定价页面。
执行： 对观察到的M1–M10进行评分；不得用计划的运行手册质量替代实际执行情况。
结果： 在声明的延迟期过后对P2–P10进行评分；不得用预测目标替代实际数据。

每个观察到的状态都需要记录来源/日期/类型/可信度。缺失的适用证据标记为Unknown；目录授权的条件项可标记为N/A并说明原因。运行

python3 "$AARON_SKILLS_ROOT/scripts/rubric-score.py" score <run.json>

对所选指定类型的配置文件进行评分。

验证与配置文件相关的否决项：

RAMP-R1

阶段/访问权限矛盾、

RAMP-A1

重大声明/披露失败、

RAMP-M1

计划或实际操作中的操纵/embargo/平台违规，以及

RAMP-P1

参与端的监控明显损坏。

§2 RAMP Worked Examples

§2 RAMP示例

Complete preflight, raw 80, no veto/fail:
```
DONE/SHIP
```
, final 80.
Complete preflight, raw 76, one verified A1 failure:
```
DONE_WITH_CONCERNS/FIX
```
, final 59.
Complete preflight, verified R1 and M1 failures:
```
DONE/BLOCK
```
, no final score.
Outcome read before conversion lag or without own-data actuals:
```
NEEDS_INPUT/UNDECIDED
```
, no score.

完整预检查，原始分数80，无否决/失败：
```
DONE/SHIP
```
，最终分数80。
完整预检查，原始分数76，一项已验证的A1失败：
```
DONE_WITH_CONCERNS/FIX
```
，最终分数59。
完整预检查，已验证的R1和M1失败：
```
DONE/BLOCK
```
，无最终分数。
在转化延迟期前或无自有实际数据时进行结果评估：
```
NEEDS_INPUT/UNDECIDED
```
，无分数。

§3 RAMP Guardrails

§3 RAMP约束规则

Stage truth follows promised access/eligibility; a pricing page is not universal evidence of GA.
A genuine feedback request is not vote solicitation.
Privacy-limited modeled measurement may be Partial; broken required instrumentation is P1 Fail.
Launch stacking/capacity is an M10 finding, not an automatic veto.
Never average preflight, execution, and outcome profiles or compare their scores as the same construct.

阶段真实性遵循承诺的访问/资格；定价页面并非通用的正式发布（GA）证据。
真实的反馈请求不属于拉票行为。
受隐私限制的建模测量可标记为Partial；必要监控损坏则标记为P1 Fail。
发布堆叠/容量属于M10发现项，并非自动否决项。
切勿对预检查、执行和结果配置文件取平均值，也不要将它们的分数视为同一指标进行比较。

§5 RAMP Translation

§5 RAMP说明

State lifecycle read with every result. On trace request, qualify

RAMP-R1/A1/M1/P1

, especially against colliding ROAS IDs.

在每个结果中声明生命周期阶段。当请求追踪时，明确说明

RAMP-R1/A1/M1/P1

，尤其是针对冲突的ROAS ID。

Report and Verdict

报告与结论

Begin with the auditor-runbook's exact typed conversation header. Never replace

status

verdict

, or

score_state

with prose; list each explicitly missing qualified item as ``ID:

unknown``` before findings. Use the stable catalog ID verbatim (for example,

RAMP-R1

); never substitute an evidence-subcheck label or synthesize a suffixed ID such as

RAMP-R1d`.

Lead with lifecycle-specific verdict, target/context/date, score or coverage/interval, confidence, profile detail, linked prior reads, critical evidence, Unknowns, and fix/rerun owner. A preflight SHIP authorizes no external launch action by itself; explicit execution approval remains required.

以审计器运行手册中明确的指定类型对话标题开头。切勿用散文替换

status

、

verdict

或

score_state

；在发现项前将每个明确缺失的合格项列为``ID:

unknown```。严格使用稳定的目录ID（例如

RAMP-R1

）；切勿替换为证据子检查标签或合成带后缀的ID（如

RAMP-R1d`）。

首先列出特定生命周期阶段的结论、目标/上下文/日期、分数或覆盖范围/时间间隔、可信度、配置文件详情、关联的先前评估、关键证据、未知项以及修复/重新评估负责人。预检查的SHIP结论本身并不授权任何外部发布操作；仍需明确的执行批准。

Validation Checkpoints

验证检查点

One launch and one lifecycle profile are declared.
Plan, execution, and outcome evidence were not mixed.
Expected items only are scored; Unknown/N/A semantics are correct.
Stage/access, policy, claims, and instrumentation vetoes are positively verified.
No launch, submission, registry, or campaign side effect occurred.

已声明单个发布和单个生命周期配置文件。
未混合计划、执行和结果证据。
仅对预期项进行评分；Unknown/N/A的语义正确。
已积极验证阶段/访问权限、策略、声明和监控的否决项。
未发生发布、提交、registry或营销活动的副作用。

Persistence

持久化

Persist only after explicit authorization to

memory/audits/launch/YYYY-MM-DD-<topic>.md

. Preserve the scorer's orthogonal

status

and

verdict

; validate the complete v3 draft with

validate-audit-artifact.py

against the intended relative path, persist only through one full-content Write, and revalidate the target per the auditor runbook. Edit/shell/MCP mutations of the reserved sink are unsupported. Create separate files for separate lifecycle reads and link them by launch ID rather than overwriting.

仅在获得明确授权后，将内容持久化到

memory/audits/launch/YYYY-MM-DD-<topic>.md

。保留评分器独立的

status

和

verdict

；使用

validate-audit-artifact.py

针对预期的相对路径验证完整的v3草稿，仅通过一次完整内容写入进行持久化，并根据审计器运行手册重新验证目标。不支持对保留存储区进行编辑/Shell/MCP修改。为不同的生命周期评估创建单独的文件，并通过发布ID关联，而非覆盖。