M1-00: Evidence Contract Delivery Tracker

角色：父级 Delivery Tracker，仅管理 M1 Evidence Contract 的发布顺序、原生 Sub-issues 与完成条件；不包含业务代码。

协作方式：
Issue 可以立即认领和开发。发布顺序仅约束合并，
不限制调研、分支、Draft PR 或测试工作。

发布顺序：

M1-01: Initialize TypeScript workspace and quality-gate CI #3 M1-01 CI
M1-02: Define PreflightReport v0.1 runtime schema #5 M1-02 Schema
M1-03: Implement fail-closed decision engine #6 M1-03 Decision Engine 与 M1-04: Add MANUAL_REVIEW success fixture #7 M1-04 Success Fixture
M1-05: Add tokenOut mismatch STOP fixture #8 M1-05 STOP Fixture
M1-06: Document M1 evidence boundary and completion criteria #9 M1-06 Documentation
M1-00: Evidence Contract Delivery Tracker #4 M1-00 Tracker closure

M1 完成条件：

M1-01: Initialize TypeScript workspace and quality-gate CI #3 已合并，且 quality-gate 已成为 main 的 required check。
M1-02: Define PreflightReport v0.1 runtime schema #5 至 M1-06: Document M1 evidence boundary and completion criteria #9 全部完成并关闭。
所有质量门槛与各子 Issue 验收标准均满足。
M1 仍不包含真实 Moss、Monad、协议、钱包、签名、交易发送、前端或后端集成。

不设置具体执行时点；Milestone 截止日期为 2026-07-24。

docs: accept PreflightReport v0.1 schema contract (#13)

@pillowtalk-Qy

M1 status update: ADR prerequisite completed; #5 implementation started

ADR 0001 and its Maintainer clarification ADR 0002 are Accepted and merged to main.
ADR 0002: https://github.com/Moss-Mini-Demo/moss-mini-demo/blob/main/docs/adr/0002-preflight-report-v0-1-implementation-values.md
Clarification PR docs: fix PreflightReport v0.1 implementation values #14 merged at 7f9c143.
The merge SHA passed main quality-gate: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30158117333
M1-02: Define PreflightReport v0.1 runtime schema #5 is reopened, assigned to @pillowtalk-Qy under its fallback-owner rule, labeled status:ready, moved to Project Ready, and has an Implementation Authorized Maintainer record.
M1-02: Define PreflightReport v0.1 runtime schema #5 is now the active implementation stage. The remaining release order stays M1-02: Define PreflightReport v0.1 runtime schema #5, then M1-03: Implement fail-closed decision engine #6/M1-04: Add MANUAL_REVIEW success fixture #7, then M1-05: Add tokenOut mismatch STOP fixture #8, then M1-06: Document M1 evidence boundary and completion criteria #9. No final review for M1-03: Implement fail-closed decision engine #6 through M1-06: Document M1 evidence boundary and completion criteria #9 starts from this update.
Tracker M1-00: Evidence Contract Delivery Tracker #4 remains Open and Project In Progress. M1 is not complete, and this update does not authorize Tracker closure.

@pillowtalk-Qy

M1 status update: Decision Engine contract accepted

ADR 0003 is Accepted and merged through PR docs: freeze Decision Engine v0.1 contract #17.
Accepted decision: https://github.com/Moss-Mini-Demo/moss-mini-demo/blob/main/docs/adr/0003-decision-engine-v0-1-contract.md
Merge/main SHA: 29d2cbcbb815eee81f16773b1487991386303c60
PR docs: freeze Decision Engine v0.1 contract #17 Accepted-head quality-gate and the merged-main quality-gate both succeeded.
M1-03: Implement fail-closed decision engine #6 now has a fixed module, input/output, 22-code STOP, SourceReference, determinism, and acceptance-test contract.
M1-03: Implement fail-closed decision engine #6 is assigned to @pillowtalk-Qy under the fallback-owner rule and remains Open / status:ready / Project Ready.
This ADR decision may proceed in parallel with PR feat: add PreflightReport v0.1 runtime schema #15 repair, but M1-03: Implement fail-closed decision engine #6 business implementation must not start before M1-02: Define PreflightReport v0.1 runtime schema #5 and PR feat: add PreflightReport v0.1 runtime schema #15 merge to latest main and the merged head passes quality-gate.
Release order remains M1-02: Define PreflightReport v0.1 runtime schema #5, then M1-03: Implement fail-closed decision engine #6/M1-04: Add MANUAL_REVIEW success fixture #7, then M1-05: Add tokenOut mismatch STOP fixture #8, then M1-06: Document M1 evidence boundary and completion criteria #9.
Tracker M1-00: Evidence Contract Delivery Tracker #4 remains Open and Project In Progress. M1 is not complete, and this update does not authorize Tracker closure.

Maintainer M1 post-PR #15 status

Current M1 baseline: main@a210d9c297ddef4b42648b2c1343da5b9c19a407.

Evidence:

PR feat: add PreflightReport v0.1 runtime schema #15 is merged and Project Done: feat: add PreflightReport v0.1 runtime schema #15
Squash commit: a210d9c
Main push quality-gate is SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30263166240/job/89967568066
Issue M1-03: Implement fail-closed decision engine #6 Schema dependency-gate record: M1-03: Implement fail-closed decision engine #6 (comment)

Control-plane status:

Issue M1-02: Define PreflightReport v0.1 runtime schema #5 is closed and Project Done.
Issue M1-03: Implement fail-closed decision engine #6 remains Ready; its Schema prerequisite is satisfied, but Decision Engine implementation has not started.
Issue M1-04: Add MANUAL_REVIEW success fixture #7's PR feat: add PreflightReport v0.1 runtime schema #15 prerequisite is satisfied. Its execution lane is refresh of existing PR test: add synthetic MANUAL_REVIEW success fixture #16 from current main, not a duplicate PR.
PR test: add synthetic MANUAL_REVIEW success fixture #16 remains Draft / Blocked until a refreshed current head resolves its DIRTY state and passes fresh validation.
Issues M1-05: Add tokenOut mismatch STOP fixture #8 and M1-06: Document M1 evidence boundary and completion criteria #9 remain Ready.
Tracker M1-00: Evidence Contract Delivery Tracker #4 remains Open / Project In Progress. This comment does not close M1 or mark the tracker Done.

Execution order remains: #6/#7 -> #8 -> #9 -> Tracker #4 closure assessment.

Maintainer M1 post-PR #16 status

Current M1 baseline: main@316dd1478b46185df862be80499963e42d73855b.

Evidence:

PR test: add synthetic MANUAL_REVIEW success fixture #16 is merged and Project Done: test: add synthetic MANUAL_REVIEW success fixture #16
Issue M1-04: Add MANUAL_REVIEW success fixture #7 is Closed / Project Done: M1-04: Add MANUAL_REVIEW success fixture #7
Squash/main commit: 316dd14
Main push quality-gate is SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30277600027/job/90015494282

Control-plane status:

Remaining M1 delivery items are M1-03: Implement fail-closed decision engine #6, M1-05: Add tokenOut mismatch STOP fixture #8, and M1-06: Document M1 evidence boundary and completion criteria #9.
M1-03: Implement fail-closed decision engine #6 is the next execution channel. Its Schema dependency gate is satisfied and implementation starts from the current main baseline through a detailed Contributor or Builder Work Plan.
M1-05: Add tokenOut mismatch STOP fixture #8 and M1-06: Document M1 evidence boundary and completion criteria #9 remain Ready. They do not enter Maintainer Review or Merge Gate ahead of M1-03: Implement fail-closed decision engine #6.
Tracker M1-00: Evidence Contract Delivery Tracker #4 remains Open / Project In Progress. M1 has not reached its closure conditions, and this record does not close the tracker or set it to Done.
The corrected release order is M1-03: Implement fail-closed decision engine #6 -> M1-05: Add tokenOut mismatch STOP fixture #8 -> M1-06: Document M1 evidence boundary and completion criteria #9 -> Tracker M1-00: Evidence Contract Delivery Tracker #4 closure assessment.

The M1 Milestone remains Open and overdue with its original 2026-07-24 due date. No new schedule is set until #6 Work Plan and initial implementation produce a credible estimate.

Hackathon recovery planning sync - 2026-07-29

Recovery target: 2026-07-29 23:00 Asia/Hong_Kong. The original M1 due date remains unchanged as historical fact.

New outstanding dependency chain:

M1-07: Clarify DecisionInput and MANUAL_REVIEW contract #18 (M1-07 contract clarification) -> M1-08: Implement ADR 0004 DecisionInput and STOP reason boundary #19 (M1-08 runtime boundary) -> M1-03: Implement fail-closed decision engine #6 (Decision Engine)
M1-03: Implement fail-closed decision engine #6 -> M1-05: Add tokenOut mismatch STOP fixture #8 and M1-09: Add amountIn mismatch STOP fixture #20 (M1-09 amountIn STOP fixture)
M1-03: Implement fail-closed decision engine #6 + M1-05: Add tokenOut mismatch STOP fixture #8 + M1-09: Add amountIn mismatch STOP fixture #20 -> M1-06: Document M1 evidence boundary and completion criteria #9 -> this tracker closure assessment

Accordingly, #6, #8, and #9 are now Project Blocked until their recorded dependencies are satisfied. Existing completed work (#5 and #7), merged ADRs, PR evidence, and the original overdue date are preserved.

This is a planning/dependency update. It does not accept #18, pass a Gate, authorize a merge, or close this tracker.

@pillowtalk-Qy

M1 dependency and release sync - 2026-07-31

Current baseline: main@27a9bc66f483a25d6602fdac2748099bfb32d67e.

Completed dependency evidence:

M1-07: Clarify DecisionInput and MANUAL_REVIEW contract #18 is Maintainer Accepted / Closed / Project Done.
M1-08: Implement ADR 0004 DecisionInput and STOP reason boundary #19 and PR M1-08: implement ADR 0004 DecisionInput and strict STOP boundary #65 are merged; ADR 0004 is Accepted.
Merged-main quality-gate is SUCCESS: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30604382716

Current control state:

M1-03: Implement fail-closed decision engine #6 is Open / status:ready / Project Ready and remains assigned to @pillowtalk-Qy.
M1-05: Add tokenOut mismatch STOP fixture #8 and M1-09: Add amountIn mismatch STOP fixture #20 remain Blocked until M1-03: Implement fail-closed decision engine #6 is merged and merged-main CI succeeds.
M1-06: Document M1 evidence boundary and completion criteria #9 remains Blocked until M1-03: Implement fail-closed decision engine #6, M1-05: Add tokenOut mismatch STOP fixture #8, and M1-09: Add amountIn mismatch STOP fixture #20 are merged.
Tracker M1-00: Evidence Contract Delivery Tracker #4 remains Open / Project In Progress.
The M1 Milestone remains Open and overdue; the original 2026-07-24 due date is preserved.

Corrected release chain:

#6
  -> #8 tokenOut fixture + #20 amountIn fixture (parallel development, serialized rebase/merge)
  -> #9 M1 evidence closeout
  -> #4 closure assessment + exact main quality-gate

No new M1 target date is asserted. A credible recovery target requires the approved #6 Work Plan and initial implementation estimate. This update does not start #8/#20, pass M1, or close this tracker.

Issue #6 implementation-scope authorization index

Issue #6 Work Plan v2 received SCOPE_CONFIRMED / IMPLEMENTATION_AUTHORIZED from exact main@7bbbc8bb9b4acb859bc73ba2b861f657864cce5c and has moved to Project In Progress.

Work Plan v2: M1-03: Implement fail-closed decision engine #6 (comment)
Maintainer authorization: M1-03: Implement fail-closed decision engine #6 (comment)
Baseline quality-gate: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30752494660

This records implementation-scope authorization only. It is not QA PASS, GitHub Approval, READY_TO_MERGE, Merge Gate, or merge authorization. #8, #20, and #9 remain Blocked.

M1_CLOSURE_NOT_READY

Evaluated main@7bbbc8bb9b4acb859bc73ba2b861f657864cce5c.

Current main push quality-gate: SUCCESS
https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30752494660/job/91508902082

Current-baseline quality evidence:

Node v22.23.1 and pnpm 11.16.0;
frozen-lockfile install and pnpm check passed in the GitHub clean checkout;
report-schema public package import passed;
8 test files / 340 tests passed / 0 failed.

This is baseline evidence only. It is not the final M1 closure gate because the required Decision Engine and two STOP Fixtures are not yet merged into main.

Completed:

M1-01: Initialize TypeScript workspace and quality-gate CI #3: Closed / Completed / Project Done via PR chore: initialize TypeScript quality gate #10, merge edd37e0b977fe2821752dda4d4c3b4715238ffe8.
M1-02: Define PreflightReport v0.1 runtime schema #5: Closed / Completed / Project Done via PR feat: add PreflightReport v0.1 runtime schema #15, merge a210d9c297ddef4b42648b2c1343da5b9c19a407.
M1-04: Add MANUAL_REVIEW success fixture #7: Closed / Completed / Project Done via PR test: add synthetic MANUAL_REVIEW success fixture #16, merge 316dd1478b46185df862be80499963e42d73855b.
M1-07: Clarify DecisionInput and MANUAL_REVIEW contract #18: Closed / Completed / Project Done.
M1-08: Implement ADR 0004 DecisionInput and STOP reason boundary #19: Closed / Completed / Project Done via PR M1-08: implement ADR 0004 DecisionInput and strict STOP boundary #65, merge 27a9bc66f483a25d6602fdac2748099bfb32d67e.
docs: define two-layer STOP presentation requirements #11 and PR docs: define STOP presentation requirements #12: Closed/Merged / Project Done; PR docs: define STOP presentation requirements #12 merge is current main@7bbbc8bb9b4acb859bc73ba2b861f657864cce5c.
Current main documentation risk-term hits are limitation statements, not capability claims.
main protection still requires strict quality-gate, resolved conversations and linear history; enforce-admins is enabled, force push/delete are disabled, and push access remains restricted to the Maintainers Team.

Outstanding:

M1-03: Implement fail-closed decision engine #6 is Open / Project In Progress. PR M1-03: implement fail-closed Decision Engine v0.1 #66 is Open / Draft at head 5d4731985beb86281610ca7abf187287e5b1d8a0 on main@7bbbc8bb9b4acb859bc73ba2b861f657864cce5c. Its exact-head CI is SUCCESS, but the QA handoff remains incomplete and no Maintainer squash merge or merged-main CI exists.
M1-05: Add tokenOut mismatch STOP fixture #8 is Open / unassigned / status:blocked / Project Blocked, with no closing implementation PR or merge commit.
M1-09: Add amountIn mismatch STOP fixture #20 is Open / unassigned / status:blocked / Project Blocked, with no closing implementation PR or merge commit.
M1-06: Document M1 evidence boundary and completion criteria #9 is Open / unassigned / status:blocked / Project Blocked, with no closeout PR or merge commit.
The Decision Engine public package import and complete 22-code matrix are not present on current main.
The tokenOut and amountIn STOP Fixtures are not present. The required three-Fixture final validation therefore cannot pass.
The M1 closeout document is not delivered. Current README and real-vs-mock correctly state that there is no Decision Engine or STOP Fixture, confirming that this baseline is not closure-ready.
PR M1-03: implement fail-closed Decision Engine v0.1 #66 is an open M1 implementation PR. It has zero unresolved conversations, but remains Draft and unmerged.
M1 remains Open with 5 open issues: M1-00: Evidence Contract Delivery Tracker #4, M1-03: Implement fail-closed decision engine #6, M1-05: Add tokenOut mismatch STOP fixture #8, M1-06: Document M1 evidence boundary and completion criteria #9 and M1-09: Add amountIn mismatch STOP fixture #20. The historical due date remains 2026-07-24.
A final independent clean-main closure verification is withheld until the missing deliverables are merged; current CI results cannot be presented as evidence for absent components.

Tracker #4 remains Open / Project In Progress.
M1 Milestone remains Open.
No M2 handoff baseline is issued by this assessment.
No M2 implementation is authorized by this assessment.

POST_ISSUE_6_EXECUTION_INDEX

Merged baseline: main@aa7ea761b2ac5e78535387e0a7d04d45485cdfb1
Merged-main push quality-gate: SUCCESS, https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30833497929/job/91752910028

Current M1 execution state:

M1-03: Implement fail-closed decision engine #6: Closed / Project Done
M1-05: Add tokenOut mismatch STOP fixture #8: Open / Qy assigned / Project In Progress, closed Work Plan is the next permitted evidence
M1-09: Add amountIn mismatch STOP fixture #20: Open / unassigned / status:ready / Project Ready
M1-06: Document M1 evidence boundary and completion criteria #9: Open / unassigned / status:blocked / Project Blocked
Tracker M1-00: Evidence Contract Delivery Tracker #4: Open / Project In Progress
M1: Open

Current serial order: #8 -> #20 -> #9 -> Tracker #4 closure assessment.

Qy may work on only one Fixture issue at a time. #20 remains unclaimed while #8 is In Progress. No implementation, branch, PR, Review, Merge Gate, or merge is authorized by this status record.

M1_CLOSURE_PASS

Assessment baseline: main@aae0397da1ba4924422d5a456123e9a4243b1797

Merged-main evidence:

PR docs: document M1 evidence boundary and completion criteria #69 squash commit: aae0397da1ba4924422d5a456123e9a4243b1797
Push quality-gate: SUCCESS
Run: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30941143295
Job: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30941143295/job/92099515288

Independent Maintainer closure assessment:

M1 Issues M1-01: Initialize TypeScript workspace and quality-gate CI #3, M1-02: Define PreflightReport v0.1 runtime schema #5, M1-03: Implement fail-closed decision engine #6, M1-04: Add MANUAL_REVIEW success fixture #7, M1-05: Add tokenOut mismatch STOP fixture #8, M1-06: Document M1 evidence boundary and completion criteria #9, M1-07: Clarify DecisionInput and MANUAL_REVIEW contract #18, M1-08: Implement ADR 0004 DecisionInput and STOP reason boundary #19, and M1-09: Add amountIn mismatch STOP fixture #20 are all Closed / Completed / Project Done.
The repository has zero open pull requests, so there is no open M1 PR.
A fresh clean checkout of the exact main SHA passed with Node 22.23.1 and pnpm 11.16.0.
pnpm install --frozen-lockfile passed.
pnpm check passed: format, lint, typecheck, ordered builds, both public package-name import smoke tests, and 13 test files / 655 tests.
manual-review-success.v0.1.json validates as provenance: FIXTURE and the public Decision Engine recomputes {"status":"MANUAL_REVIEW"}.
token-out-mismatch.v0.1.json validates as provenance: FIXTURE and recomputes the exact CRITICAL_ALIGNMENT_FAIL STOP with its two raw-owned references.
amount-in-mismatch.v0.1.json validates as provenance: FIXTURE and recomputes the exact CRITICAL_ALIGNMENT_FAIL STOP with its three raw-owned references.
README, Real-versus-Mock, the M1 completion inventory, security-boundary, and Fixture documentation continue to separate synthetic evidence from live evidence and explicitly reject safety, approval, authorization, execution-guarantee, signing-permission, product, and real-chain claims.
Main protection remains strict: required quality-gate, strict up-to-date checks, resolved conversations, linear history, enforce admins, no force push or deletion, and push restriction to the Maintainers Team.

Conclusion: M1 satisfies the recorded closure criteria on the exact main baseline above.

Tracker #4 may be closed as Completed / Project Done and the M1 Milestone may be closed. This assessment does not itself implement M2 or authorize any M2 Issue beyond the separate post-closure execution-slot update.

Navigation Menu

Repository navigation

M1-00: Evidence Contract Delivery Tracker #4

15 remaining items

M1 status update: ADR prerequisite completed; #5 implementation started

M1 status update: Decision Engine contract accepted

Maintainer M1 post-PR #15 status

Maintainer M1 post-PR #16 status

Hackathon recovery planning sync - 2026-07-29

M1 dependency and release sync - 2026-07-31

Issue #6 implementation-scope authorization index

M1_CLOSURE_NOT_READY

POST_ISSUE_6_EXECUTION_INDEX

M1_CLOSURE_PASS

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

M1-00: Evidence Contract Delivery Tracker #4

Description

Activity

15 remaining items

pillowtalk-Qy commented on Jul 25, 2026

M1 status update: ADR prerequisite completed; #5 implementation started

pillowtalk-Qy commented on Jul 26, 2026

M1 status update: Decision Engine contract accepted

pillowtalk-Qy commented on Jul 27, 2026

Maintainer M1 post-PR #15 status

pillowtalk-Qy commented on Jul 27, 2026

Maintainer M1 post-PR #16 status

pillowtalk-Qy commented on Jul 29, 2026

Hackathon recovery planning sync - 2026-07-29

pillowtalk-Qy commented on Jul 31, 2026

M1 dependency and release sync - 2026-07-31

pillowtalk-Qy commented on Aug 2, 2026

Issue #6 implementation-scope authorization index

pillowtalk-Qy commented on Aug 3, 2026

M1_CLOSURE_NOT_READY

pillowtalk-Qy commented on Aug 3, 2026

POST_ISSUE_6_EXECUTION_INDEX

pillowtalk-Qy commented on Aug 5, 2026

M1_CLOSURE_PASS

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions