Commitf83d8d86Recorded12 Aug 2026Repositorysigil-doc
docs: record the two SD-P7 rulings in the v0.1.3 release notes
Message
The known-limitation section called the "required stance" question open. It was ruled at SD-P7's review on 2026-08-12: no model-side requirement, because the model cannot require a stance on a concept it does not own, so the obligation moves to the consuming language's own gate.
Also records the one-directional inheritance ruling and the superset argument that makes it safe, since a reader of the release notes meets that asymmetry the moment they build a delegating language.
Changed
docs/v0.1.3-tag-message.md | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)Diff
docs/v0.1.3-tag-message.mdmodified
@@ -46,5 +46,14 @@ so its profile is installed for the manuscript's extent.
46
A profile's declared refusals are enforced, and a profile that declares nothing 47
about a kind is not constrained about that kind. The mechanism protects against 48
a profile that declares something wrong, not against one that declares nothing.−49
Whether a profile should be required to state its stance on nested structural−50
containers is an open design question.+49
+50
A profile is deliberately NOT required to state its stance on nested structural+51
containers. The model cannot require a stance on a concept it does not own, so+52
the obligation belongs to the consuming language: a delegating language's own+53
gate is where silence about its structural containers should be made impossible.+54
+55
Profile inheritance is one-directional by the same reasoning. Leaving an extent+56
restores the previous profile; entering one does not install a profile. The core+57
block vocabulary is a floor, so any inherited ambient profile is a superset of+58
`sigil/doc`'s and an inner manuscript cannot construct a node its own language+59
forbids.