docs: clarify continue adoption boundaries

This commit is contained in:
axiomlogicnexus 2026-06-24 05:23:32 +00:00
parent f664f099f5
commit db5820bb54
2 changed files with 56 additions and 0 deletions

View file

@ -84,6 +84,24 @@ Future instances must not interpret `continue` as:
- permission to widen into a different pillar because it feels interesting
- permission to dissolve a previously declared boundary
At prepared decision boundaries, plain `continue` may or may not confirm or
adopt the displayed suggestion. It may confirm or adopt the suggestion only
when the prior closeout or prepared packet explicitly states that recommendation
adoption is allowed for that exact boundary. It may fail to confirm or adopt
the suggestion when the closeout states that explicit user selection is still
required or when a real stop condition remains active. Future instances must
not silently assume that `continue` is a universal vote for the last displayed
recommendation.
At prepared decision boundaries, plain `continue` may or may not confirm or
adopt the displayed suggestion. It may confirm or adopt the suggestion only
when the prior closeout or prepared packet explicitly states that recommendation
adoption is allowed for that exact boundary. It may fail to confirm or adopt
the suggestion when the closeout states that explicit user selection is still
required or when a real stop condition remains active. Future instances must
not silently assume that `continue` is a universal vote for the last displayed
recommendation.
## Stop rule
Future instances should halt only when a real stop condition exists.

View file

@ -184,6 +184,44 @@ or
- recommendation-adoption status: explicit user choice still required because sovereign ownership or legal routing remains materially unresolved
Expanded closeout-shape repertoire:
- recommendation-adoption status: plain `continue` may adopt the displayed
recommendation because the boundary is same-family, low-ambiguity, and no
real stop condition remains active
- recommendation-adoption status: plain `continue` may not adopt the displayed
recommendation because the boundary still requires explicit user choice
- recommendation-adoption status: plain `continue` does not itself settle the
suggestion because a live blocker, quiz boundary, legal boundary, or
fresh-family boundary still controls
The governing interpretation is now explicit:
- plain `continue` may confirm or adopt a displayed suggestion
- plain `continue` may also fail to confirm or adopt it
- the closeout must state which case is true
- future instances must not infer adoption from `continue` alone when the
closeout does not authorize that adoption
Expanded closeout-shape repertoire:
- recommendation-adoption status: plain `continue` may adopt the displayed
recommendation because the boundary is same-family, low-ambiguity, and no
real stop condition remains active
- recommendation-adoption status: plain `continue` may not adopt the displayed
recommendation because the boundary still requires explicit user choice
- recommendation-adoption status: plain `continue` does not itself settle the
suggestion because a live blocker, quiz boundary, legal boundary, or
fresh-family boundary still controls
The governing interpretation is now explicit:
- plain `continue` may confirm or adopt a displayed suggestion
- plain `continue` may also fail to confirm or adopt it
- the closeout must state which case is true
- future instances must not infer adoption from `continue` alone when the
closeout does not authorize that adoption
This field is mandatory because deterministic continuation now includes a narrow
safe path for recommendation adoption, and future instances must not leave that
truth implicit.