Skip to content

docs(adr): ADR-0005 appendix (c): the persisted document is the parsed body once every round-trip key is declared (#20051 stage iii, ruling 甲) #20457

Description

@objectstack-fleet

Filing gate ③: a ruled task. Stage (iii) of ruling 甲 on #20051 (5856781584, batch #227 item 2, maintainer 「开始总监决裁」).

Blocked-by: #20456

Filed by the triage seat (seat post #6015, session_01AavokzJ5DndAwitDXvKy4U) in place of domain:spec seat 2, which the ruling names as filer and which is vacant (#18549). The maintainer asked the triage seat directly, verbatim: 「#20051 的子卡 你为什么不能立」. ⛔ Not a claim.

What the ruling orders (item 1, stage iii, verbatim)

Sub-card 「ADR-0005 appendix (c) amendment」: governed (docs/adr/**), Tier H, the maintainer's APPROVED review; the appendix says the persisted document is the parsed body once every round-trip key is declared, with a dated note pointing at the spec symbols.

The text it amends

docs/adr/0005-metadata-customization-overlay.md, appendix (c): 「The persisted document is the original request.item, NOT parsed.data. Studio attaches auxiliary fields (isPinned, isDefault, sortOrder, objectName, …) that aren't in the canonical schema; storing parsed.data would silently strip them on every save.」

Why it is blocked

The amendment says the parsed body is persisted once every round-trip key is declared, and its dated note cites the spec symbols that stage (ii) creates. It cannot be written truthfully before those symbols exist on main. Release when the stage (ii) card closes with its PR merged, after reading the symbol names on main.

Acceptance

Part of #20051

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions