The pre-apply, parent-independent admission checks every proposal —
standalone or carried by a commit, inbound or locally built — must pass
before it is staged, applied, or published (CR-03/CR-02). Returns the first
violation, in this order:
no component id carries more than one AppDataUpdate operation in the
batch, and app_components (0x0001) is never removed (MDK batch loop 1);
every update targets an id that is legal GroupContext state
(the internal NON_GROUP_CONTEXT_COMPONENT_IDS check) and, for a known component id,
carries a payload that decodes with that component's codec. Without this,
one AppDataUpdate — which the admin gate admits from any member as a
standalone proposal, and which a later commit bundles by reference —
could poison the group dictionary with bytes no member can decode;
every remove targets an id that is neither structurally unremovable
(the internal UNREMOVABLE_COMPONENT_IDS set) nor present in the RESULTING required
list (MDK batch loop 2).
requiredIds is the PARENT epoch's required-component list
(requiredComponentIdsOf). Removal legality is then measured against
the list the batch itself produces — this batch's own 0x0001 update wins
over requiredIds — so the spec's atomic "un-require and remove in the same
commit" stays legal while removing a still-required component does not.
Omitting requiredIds yields MDK's standalone admission semantics
(validate_standalone_app_data_update, which passes an empty set): a lone
proposal cannot be judged against a batch it is not yet part of, and the
commit that bundles it re-runs this validator with the real list.
Shared by the admin callback, by every seam that labels a callback
rejection, and by the outbound commit/proposal seams, so the verdict and its
reason cannot differ per seam.
The pre-apply, parent-independent admission checks every proposal — standalone or carried by a commit, inbound or locally built — must pass before it is staged, applied, or published (CR-03/CR-02). Returns the first violation, in this order:
0x8009proof (validateAddProposalAccountIdentityProofs, D-08/D-09);AppDataUpdateoperation in the batch, andapp_components(0x0001) is never removed (MDK batch loop 1);updatetargets an id that is legal GroupContext state (the internalNON_GROUP_CONTEXT_COMPONENT_IDScheck) and, for a known component id, carries a payload that decodes with that component's codec. Without this, one AppDataUpdate — which the admin gate admits from any member as a standalone proposal, and which a later commit bundles by reference — could poison the group dictionary with bytes no member can decode;removetargets an id that is neither structurally unremovable (the internalUNREMOVABLE_COMPONENT_IDSset) nor present in the RESULTING required list (MDK batch loop 2).requiredIdsis the PARENT epoch's required-component list (requiredComponentIdsOf). Removal legality is then measured against the list the batch itself produces — this batch's own0x0001update wins overrequiredIds— so the spec's atomic "un-require and remove in the same commit" stays legal while removing a still-required component does not. OmittingrequiredIdsyields MDK's standalone admission semantics (validate_standalone_app_data_update, which passes an empty set): a lone proposal cannot be judged against a batch it is not yet part of, and the commit that bundles it re-runs this validator with the real list.Shared by the admin callback, by every seam that labels a callback rejection, and by the outbound commit/proposal seams, so the verdict and its reason cannot differ per seam.