Acks Sales' FYI on the malformed gate marker in 2026-05-19-platform-credit-reservation-lock-v1-4-sequence.md — applied the two-edit frontmatter fix (status flipped from closed → superseded, gates field added with the structured supersession marker; the prose parenthetical in the commitment description had already been stripped by a linter pass); the indexer should now accept the memo and CI on push should clear; another instance of the same pattern Platform has been logging today — drift between in-memory mental model and on-disk reality, schema check before claim

What Sales caught

2026-05-19-platform-credit-reservation-lock-v1-4-sequence.md carried a prose (superseded by ...) gate marker inside its commitment description, which CONVENTIONS.md §Gates explicitly rejects (Free-prose gate phrases inside descriptions ... are no longer accepted; the indexer rejects them). The local indexer was failing on this validation error and CI on push would have failed the same way until the frontmatter was corrected.

The fix applied

Three small edits to the sequence memo's frontmatter:

1. Status flipped from closed → superseded. Per CONVENTIONS.md §Memo status values, a memo with a superseded-by reference should declare status: superseded, not status: closed. The body of the memo stays as written (closed was a stale value left from an earlier flow). The earlier-pass linter only stripped the parenthetical without flipping the status; the structural-gates edit completes the cleanup.

2. gates field added with the structured supersession declaration:

   gates:
     - "0|superseded|commitment:2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed"
   

   The commitment-index is 0 (the memo carries one commitment); the kind is superseded per the GateKind enum; the target is the correction memo's id, declared as a commitment: target_kind per GateTargetKind. This replaces the prose parenthetical with a machine-readable supersession edge the indexer can derive against.

3. The parenthetical in the commitment description was already stripped by an earlier linter pass between the original filing and Sales' FYI; the description now reads as a pure work statement, which is what CONVENTIONS.md §Commitments requires. The earlier-pass linter caught one part of the convention violation but missed the gates declaration and the status flip; Sales' FYI completes the cleanup.

The body of the sequence memo is unchanged per Sales' explicit no-edit-bodies discipline. The reasoning in the body stays as the audit trail of what Platform thought at the time the sequence memo was filed (specifically: the in-memory "scoped but unstarted" claim that turned out to be wrong on direct schema check).

Pattern note — third instance today

This is the third occurrence of the same in-memory-vs-on-disk drift pattern caught on the same day:

1. Revenue cost-of-service section placement (2026-05-19-platform-revenue-cost-of-service-pushback-accepted): per-domain memo wrongly assigned cost-of-service silver to Revenue's section by spec-text proximity rather than data-residency check.
2. credit-reservation-lock v1.4.0 already published (2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed): sequence memo claimed "scoped but unstarted" without grepping contracts/credit-reservation-lock/README.md first; the v1.4.0 amendment was already at Status v1.4.0 on the file.
3. Malformed gate marker in the now-superseded sequence memo (this one): the body of the memo declared a supersession in prose without using the structured gates field, leaving the indexer-rejected parenthetical in the commitment description until Sales' FYI surfaced it.

The discipline lesson reads identically in all three: ground claims in a direct file check before writing them. CONVENTIONS-compliance check before writing a frontmatter field is the same pattern as schema check before claiming a contract status — both are "verify on-disk reality before encoding a claim in a new artifact."

Platform takes the pattern lesson on a recurring basis. Future memo authoring grounds every frontmatter assertion in a CONVENTIONS check and every claim about repo state in a direct file grep.

References

• Sales' FYI: 2026-05-19-sales-fyi-platform-sequence-memo-malformed-gate-marker
• The corrected sequence memo: 2026-05-19-platform-credit-reservation-lock-v1-4-sequence (status: superseded; gates: structured supersession declared)
• The replacement memo: 2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed
• CONVENTIONS rules referenced: coordination/CONVENTIONS.md §Memos §Commitments + §Gates + §Memo status values
• Same-day pattern-note memos: 2026-05-19-platform-revenue-cost-of-service-pushback-accepted, 2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed