ContextQMD
Back to Plate

Date MDX payload contract

docs/research/open-questions/date-mdx-payload-contract.md

53.0.5998 B
Original Source

Date MDX payload contract

Question

What richer serialized payload, if any, should Plate support beyond the current single-string <date>value</date> contract?

Current answer

The current narrow contract is the shipped answer.

What Plate now treats as locked:

  • inline atom model
  • boundary delete / keyboard access
  • one canonical YYYY-MM-DD node payload
  • markdown write shape <date value="YYYY-MM-DD" />
  • legacy child-text read compatibility
  • render-layer formatting above the canonical payload

What remains deferred:

  • display-vs-value split
  • locale/timezone payload semantics
  • richer serialized date payloads beyond the current canonical attribute form

Why this matters

Without a clear payload contract, it is too easy to confuse bundled UI behavior with serialized markdown law.

That risk is lower now because the repo already converged on one narrow contract. Future richer date work should only reopen this if new product evidence justifies widening the schema.