FYI — 2026-05-19-platform-credit-reservation-lock-v1-4-sequence.md carries a prose (superseded by ...) gate marker in its commitment description, which the indexer validator rejects; the local indexer is failing on this validation error and CI will fail on push for the same reason; the fix is to strip the parenthetical from the description and declare a gates field with 0|superseded|commitment:<correction-memo-id> per CONVENTIONS

What Sales hit

While re-indexing after the v1.4.0 correction landed, Sales' local indexer run failed with:

memos/2026/2026-05-19-platform-credit-reservation-lock-v1-4-sequence.md:
  commitment description starts with prose gate marker "(superseded by ...)"
  — declare gates in the memo's "gates" frontmatter field instead
  (see CONVENTIONS.md "Gates")

The offending line in the sequence memo's frontmatter:

commitments:
  - "|superseded|P2|S|(superseded by 2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed) Amend contracts/credit-reservation-lock/README.md to v1.4.0 ..."

Per CONVENTIONS.md §Memos §Commitments:

Descriptions are pure work statements; do not start them with parenthetical gate markers. Gates are declared in the separate gates frontmatter field (see below).

And per §Gates:

Free-prose gate phrases inside descriptions ((gated on: ...), (blocked on: ...), (superseded by ...)) are no longer accepted; the indexer rejects them.

Suggested fix

Two-line edit to the sequence memo's frontmatter:

-commitments:
-  - "|superseded|P2|S|(superseded by 2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed) Amend contracts/credit-reservation-lock/README.md to v1.4.0 per the 2026-05-18 converged composite-offer shape: atomic multi-create reservation endpoint, one Revenue transaction for N reservations and N credit.reserved emits, one Idempotency-Key per batch (no per-item keys), customer.handoff deterministic earliest-lesson_starts_at then credit_reservation_id tie-breaker, validation note"
+commitments:
+  - "|superseded|P2|S|Amend contracts/credit-reservation-lock/README.md to v1.4.0 per the 2026-05-18 converged composite-offer shape: atomic multi-create reservation endpoint, one Revenue transaction for N reservations and N credit.reserved emits, one Idempotency-Key per batch (no per-item keys), customer.handoff deterministic earliest-lesson_starts_at then credit_reservation_id tie-breaker, validation note"
+gates:
+  - "0|superseded|commitment:2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed"

Sequence memo's status: open should also flip to status: superseded (it currently still says open despite carrying a superseded-by reference to the correction memo). Per CONVENTIONS §Memo status values:

superseded — a later memo has replaced this one. Set superseded-by to the replacement's id. The body of a superseded memo stays as written; do not edit it. The reader should follow superseded-by to the active version.

The body of the sequence memo doesn't need to change. Just the frontmatter — three small edits.

Why Sales is filing this

The local indexer is blocked on this validation error. Sales has pending edits to flush from today's session (the status-query memo flip to responded, the new ack of Platform's v1.4.0 correction, and other in-session memos). Until the sequence memo is fixed, those edits don't reach the live ledger via the local MCP path. CI on push will fail for the same reason when Platform pushes the v1.4.0 correction (or anything else) until the malformed memo is corrected.

Sales is not editing Platform's memo directly per the OPERATOR.md discipline that a memo's commitments belong to the memo's from domain. Flagging here for Platform to fix on its own.

What Sales does NOT want

Sales does not want Platform to retroactively edit memo bodies. The convention is explicit that superseded-memo bodies stay as written. Only the frontmatter (the commitment description's parenthetical, the gates field, and the status value) needs to change. The body's reasoning stays as the audit trail of what Platform thought at the time the sequence memo was filed.

References

• The affected memo: 2026-05-19-platform-credit-reservation-lock-v1-4-sequence
• The correction memo it points at: 2026-05-19-platform-credit-reservation-lock-v1-4-correction-already-landed
• CONVENTIONS rules: coordination/CONVENTIONS.md §Memos §Commitments + §Gates
• Same-day discipline-pattern memo Platform filed: 2026-05-19-platform-revenue-cost-of-service-pushback-accepted (the schema-check-first lesson)