M1-02: Define PreflightReport v0.1 runtime schema #5

Activity

1. pillowtalk-Qy

   added this to the M1 - Quality Gate & Evidence Contract milestone on Jul 22, 2026
2. pillowtalk-Qy

   added

   type:featureNew product functionalityNew product functionality

   area:architectureArchitecture and module boundariesArchitecture and module boundaries

   priority:P0Critical priorityCritical priority

   risk:trust-boundaryChanges a trust or evidence boundaryChanges a trust or evidence boundary

   on Jul 22, 2026
3. pillowtalk-Qy

   marked this as blocking 2 issues on Jul 22, 2026

   • M1-05: Add tokenOut mismatch STOP fixture #8
   • M1-04: Add MANUAL_REVIEW success fixture #7
4. pillowtalk-Qy

   marked this as blocked on Jul 22, 2026

   • M1-01: Initialize TypeScript workspace and quality-gate CI #3
5. pillowtalk-Qy

   marked this as blocking on Jul 22, 2026

   • M1-03: Implement fail-closed decision engine #6
6. pillowtalk-Qy

   added a parent issue on Jul 22, 2026

   • M1-00: Evidence Contract Delivery Tracker #4
7. pillowtalk-Qy

   marked this as blocking on Jul 22, 2026

   • M1-00: Evidence Contract Delivery Tracker #4
8. pillowtalk-Qy

   unmarked this as blocking 4 issues on Jul 22, 2026

   • M1-00: Evidence Contract Delivery Tracker #4
   • M1-03: Implement fail-closed decision engine #6
   • M1-05: Add tokenOut mismatch STOP fixture #8
   • M1-04: Add MANUAL_REVIEW success fixture #7
9. 6 remaining items

   Load more
10. pillowtalk-Qy

    reopened this on Jul 25, 2026
11. pillowtalk-Qy

    added

    status:readyReady to startReady to start

    and removed

    status:blockedBlocked by an unresolved dependencyBlocked by an unresolved dependency

    on Jul 25, 2026
12. pillowtalk-Qy

    self-assigned this

    on Jul 25, 2026
13. pillowtalk-Qy commented on Jul 25, 2026

    

    pillowtalk-Qy

    on Jul 25, 2026

    ContributorAuthor

    More actions

    Implementation Authorized

    Maintainer determination: implementation of #5 is now formally authorized.

    Decision and gate evidence:

    • ADR 0001: https://github.com/Moss-Mini-Demo/moss-mini-demo/blob/main/docs/adr/0001-preflight-report-v0-1-schema-contract.md
    • ADR 0002 Maintainer clarification: https://github.com/Moss-Mini-Demo/moss-mini-demo/blob/main/docs/adr/0002-preflight-report-v0-1-implementation-values.md
    • Accepted clarification PR docs: fix PreflightReport v0.1 implementation values #14: docs: fix PreflightReport v0.1 implementation values #14
    • Merge SHA: 7f9c143
    • PR quality-gate: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30157078632
    • main quality-gate for the merge SHA: https://github.com/Moss-Mini-Demo/moss-mini-demo/actions/runs/30158117333

    ADR 0001 and ADR 0002 together are the fixed PreflightReport v0.1 contract. The exact asset, availability, selection, simulation, provenance, ProtocolId, EIP-55, reportId, generatedAt, network, and source-reference decisions must be implemented as recorded; they are not implementation-PR discretion.

    Execution owner: @pillowtalk-Qy, assigned under the Issue fallback-owner rule. Issue status is Open with status:ready, and Project Status is Ready.

    Authorization scope and boundaries:

    • This authorization applies only to M1-02: Define PreflightReport v0.1 runtime schema #5 and its stated Zod, TypeScript, export, invariant, and Vitest acceptance scope.
    • Existing STOP conditions, the meaning of MANUAL_REVIEW, raw-evidence ownership, and Capability integrity are unchanged.
    • No real address, protocol value, or live-chain claim is authorized.
    • Final review for M1-03: Implement fail-closed decision engine #6, M1-04: Add MANUAL_REVIEW success fixture #7, M1-05: Add tokenOut mismatch STOP fixture #8, or M1-06: Document M1 evidence boundary and completion criteria #9 is not started. 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.

    Audit note: GitHub temporarily changed the Issue state after interpreting a negated phrase in PR #14 as a closing keyword. The PR body now has no closing reference, and #5 was reopened before this authorization; that transient state was not an implementation completion event.
14. pillowtalk-Qy

    added

    status:blockedBlocked by an unresolved dependencyBlocked by an unresolved dependency

    and removed

    status:readyReady to startReady to start

    on Jul 26, 2026
15. pillowtalk-Qy commented on Jul 26, 2026

    

    pillowtalk-Qy

    on Jul 26, 2026

    ContributorAuthor

    More actions

    Maintainer implementation block

    Issue #5 is blocked on the trust-boundary fixes required by the Maintainer review of Draft PR #15 at reviewed head 70c6cf4ee63bbd42d0eaf2a19474436edfc22cf5.

    Assignee, M1 Milestone, and the Issue/PR relationship remain unchanged. Implementation may resume only after PR #15 produces a corrected head and passes the required full Maintainer re-review.
16. pillowtalk-Qy

    removed their assignment

    on Jul 27, 2026
17. pillowtalk-Qy commented on Jul 27, 2026

    

    pillowtalk-Qy

    on Jul 27, 2026

    ContributorAuthor

    More actions

    Maintainer repair-owner handoff

    Issue #5 remains Open / Blocked, with Project status Blocked, pending repair of PR #15. The previous fallback implementation assignment does not constitute explicit acceptance of this newly defined trust-boundary repair package, so it has been cleared to avoid showing an unconfirmed repair owner.

    Repair owner: currently unassigned / awaiting explicit acceptance. No completion date is being set while the work is unowned.

    A contributor may claim the repair by commenting on this issue that they accept the complete scope below. The Maintainer will assign the issue only after that explicit acceptance:

    1. Make the public @moss-mini-demo/report-schema runtime entry loadable under supported Node 22 and add the package-import smoke test to the quality gate.
    2. Reject AVAILABLE critical evidence whose raw artifact is null, absent, or otherwise unprovable.
    3. Reject SourceReference self-reference, cycles, metadata self-authentication, unrelated references, and dangling references.
    4. Stop applying presentation/prose/extension path restrictions to identically named fields inside legitimate raw payloads.
    5. Separate public JSON Pointer syntax validation from full-report contextual SourceReference validation.
    6. Add regressions for nullable raw evidence, cycles, and the complete STOP-trigger association matrix, including correct links that pass and unrelated/dangling/cyclic links that fail.

    The repair must be submitted as a genuine new PR #15 head. Green CI on the unchanged head is not evidence that these blockers are resolved. PR #15 stays Draft and Blocked until the new head satisfies the recorded re-entry conditions and completes a fresh Maintainer review.

    Control-plane correction: #15 (comment)
18. pillowtalk-Qy commented on Jul 27, 2026

    

    pillowtalk-Qy

    on Jul 27, 2026

    ContributorAuthor

    More actions

    Trust-boundary repair scope acceptance

    I accept the complete PR #15 trust-boundary repair scope recorded in the Maintainer repair-owner handoff, including package entry, non-null raw artifacts, contextual SourceReference validation, raw-path ownership, public API naming, and the complete regression matrix.

    I will keep the repository read-only and will not switch to or modify the PR #15 branch until the Maintainer explicitly reassigns Issue #5 to Qy.
19. pillowtalk-Qy

    removed

    status:blockedBlocked by an unresolved dependencyBlocked by an unresolved dependency

    on Jul 27, 2026
20. pillowtalk-Qy

    self-assigned this

    on Jul 27, 2026
21. pillowtalk-Qy commented on Jul 27, 2026

    

    pillowtalk-Qy

    on Jul 27, 2026

    ContributorAuthor

    More actions

    Maintainer implementation authorization: PR #15 trust-boundary repair

    Qy's complete-scope acceptance is accepted. Issue #5 is now formally assigned to pillowtalk-Qy, and its Project status is In Progress.

    Authorization is granted to update the existing codex/issue-5-preflight-report-schema branch and deliver the repair through the existing PR #15. At the time of authorization, PR #15 remains at 4d47ead0e66b9748dd69e134c214cb0be8c9e480.

    Execution constraints

    • Continue using PR feat: add PreflightReport v0.1 runtime schema #15; do not open a duplicate repair PR.
    • Do not push or commit directly to main.
    • Do not reduce, defer, or partially declare completion of the accepted repair scope.
    • Do not mark PR feat: add PreflightReport v0.1 runtime schema #15 Ready before a genuine repair head containing substantive fixes and regression tests exists.
    • A new head and green CI do not themselves grant Merge Gate entry. The recorded current-head re-review conditions still apply, followed by a complete Maintainer review.
    • PR feat: add PreflightReport v0.1 runtime schema #15 remains Draft, status:blocked, and Project Blocked during repair.
    • PR test: add synthetic MANUAL_REVIEW success fixture #16 and Issue M1-04: Add MANUAL_REVIEW success fixture #7 remain Draft/Blocked and must not absorb or independently validate unfinished PR feat: add PreflightReport v0.1 runtime schema #15 changes.
    • Issue M1-03: Implement fail-closed decision engine #6 remains Ready, but its dependency gate is not released and Decision Engine implementation must not begin.

    Required repair scope

    1. Node 22 can load @moss-mini-demo/report-schema through its public package entry.
    2. The public package-import smoke test is enforced by quality-gate.
    3. AVAILABLE critical raw artifacts reject null, missing, and otherwise unprovable values.
    4. SourceReference validation rejects self-reference, cycles, metadata self-authentication, dangling references, and unrelated references.
    5. Legitimate raw payload fields are not rejected by presentation-layer field-name restrictions.
    6. The public API clearly distinguishes JSON Pointer syntax validation from full-report contextual SourceReference validation.
    7. Regression coverage includes nullable raw artifacts, cyclic references, and the complete STOP-trigger association matrix, including valid associated references that pass and unrelated, dangling, or cyclic references that fail.

    This authorization makes Issue #5 executable; it is not Review or Merge authorization for the current PR head. No delivery date is inferred from scope acceptance because no credible estimate has been supplied.

    Maintainer scope record: #5 (comment)
22. pillowtalk-Qy

    closed this as completedin #15on Jul 27, 2026