Source changed 2026-10-03 14:36:52 UTC · snapshot created 2026-10-03 14:38:14 UTC · last check 2026-10-03 15:00:09 UTC
G.10:4.7 - Published surfaces must ship kind, source, derivation, lens, and shortlist token
Published surfaces should carry the subject kind, source set kind, and relevant declared surface pins. When a selector outcome is shipped, they should also carry its outcome kind and, when applicable, the set-result kind or handoff kind.
These are publication payload metadata fields inside SoTA-Pack(Core), not publication face kinds, publication form kinds, interop publication form kinds, or carrier kinds.
Good publication fields include selectorOutcomeKind, setResultFamily, handoffKind, subjectKind, sourceSetFamily, sourceSetComposition, dominanceRegime, lensId, shortlistId, and any declared archive or promotion-policy ids that the reader needs to interpret the visible set.
Those payload fields should use controlled tokens, cited ids, or already-declared head labels rather than shipping-local prose values.
When the visible surface or the shortlisted source is one derived tradition view, also publish the derivation explicitly.
Useful additional fields there include derivedViewKind, basePaletteRef, and the declared qId or reachability rule id that disciplined that derivation.
portfolioMode may remain as one support field about selector operation, but it should not stand in for the public set label.
A published surface should mirror semantics that are already declared in the governing palette, front, archive, or shortlist language.
It should not redefine that semantics locally.
When one shipped surface still needs a plain-language label, use the declared set-result kind and source set rather than falling back to portfolioMode.