M2-02: Freeze scope, judge map and Gate contracts

Type: Product/Engineering Contract Docs
Priority: P1
Initial status: Ready after M2-01 proposal is stable
Owner: Product/Ops
Depends on: M2-01 proposed boundary
Blocks: M5-04, final claims
Writable: docs/hackathon-scope.md, docs/judge-map.md,
          docs/implementation-roadmap.md, README links only

唯一目标

在仓库内冻结本次交付范围、五项评审证据、Gate A/B/C 和 Scope Cut，不夸大实现状态。

验收

[ ] Exact-input Swap 是唯一 P0 操作
[ ] happy + amount mismatch 是主场景
[ ] 至少一个真实协议为 P0；第二协议 P1
[ ] Gate A/B/C 和日期完整
[ ] MANUAL_REVIEW 合同准确
[ ] Live/Fixture/Local Fork 清楚
[ ] out-of-scope 含 wallet/signing/broadcast/ZK/multichain
[ ] 五项评审各有可观察证据
[ ] planned 与 implemented 明确分开

验证

pnpm check
git diff --check
rg -n 'SAFE|APPROVED|READY TO SIGN|100% SECURE' docs/hackathon-scope.md docs/judge-map.md docs/implementation-roadmap.md README.md

Codex 指令

只把已批准范围、Gate 和评审映射写入 docs；不要用产品愿景替代验收条件，
不要把预计实现写成当前能力。列出所有禁止词命中及其上下文分类。

Dependency gate cleared - 2026-07-31

M2-01 / #22 is Maintainer Accepted, closed as Completed, and Project Done. The accepted runtime and module boundary is Next.js App Router on the Node runtime in one deployable Node process, with Moss server-only and Clear402 fully optional.

#23 is therefore released from Blocked to Ready.

Execution boundaries:

Record the approved scope, judge evidence map, Gate A/B/C, current delay, and Scope Cut without describing planned work as implemented.
Preserve exact MANUAL_REVIEW and provenance language.
Apply the first Scope Cut tier now: second protocol is P1 after one real protocol works; no animated Capability Tree, Markdown/print export, third attack scenario, local fork requirement, extended protocol explanation, or extra token/form flexibility in the P0 claim.
Do not cut Decision Engine, Moss Capability/simulation evidence, PreflightReport, happy path, amount mismatch STOP, explicit provenance/Fixture recovery, Gate A false mode, minimum Clear402 envelope/digest/verifier, Gate B matrix, or Gate C.
Existing PR docs: define STOP presentation requirements #12/docs: define two-layer STOP presentation requirements #11 owns its README link first. M2-02: Freeze scope, judge map and Gate contracts #23 may develop in parallel, but must rebase and merge after docs: define two-layer STOP presentation requirements #11 to avoid README conflict.

This record changes readiness only; it does not claim any Gate has passed.

POST_MERGE_AUDIT: main 41a32cabd12702fa4786bdf72160db381fa6f542; merged-main quality-gate run 31248130228 SUCCESS; Issue Closed/Completed; Project Done; branch/worktrees cleaned.

Navigation Menu

Repository navigation

M2-02: Freeze scope, judge map and Gate contracts #23

Dependency gate cleared - 2026-07-31

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

M2-02: Freeze scope, judge map and Gate contracts #23

Description

Activity

pillowtalk-Qy commented on Jul 31, 2026

Dependency gate cleared - 2026-07-31

pillowtalk-Qy commented on Aug 8, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions