Drop the "Child Subject" term; record what a page's Subjects are - #1368
Merged
Conversation
Fixes #959 A page holds Subjects, one of them optionally the Main Subject; sharing a page is storage, not a relationship, so the other Subjects need no term of their own. The glossary still called them Child Subjects, which implied a link to the Main Subject that only an explicit Relation carries. Drop the term from the glossary (with an Avoid entry), from the Draft ADRs 28 and 31, and from planning/Relations.md; the decisions themselves are unchanged. The planning doc also records where in-flow-created Subjects land now that a Subject can be moved, carries the page-scoped vs free-standing question from the issue so closing it does not lose the question, and points at the identifier rename that follows (#1367). Considered, omitted: the identifier and API renames themselves and the API docs that describe them, tracked in #1367 for after #1265 lands. ADR 7 keeps its wording as an accepted record. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
JeroenDeDauw
force-pushed
the
docs/drop-child-subject-term
branch
from
September 7, 2026 17:31
eb0ad84 to
204d703
Compare
JeroenDeDauw
marked this pull request as ready for review
September 7, 2026 17:36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #959
A page holds Subjects, one of them optionally the Main Subject; sharing a
page is storage, not a relationship, so the other Subjects need no term of
their own. The glossary still called them Child Subjects, which implied a
link to the Main Subject that only an explicit Relation carries.
Drop the term from the glossary (with an Avoid entry), from the Draft
ADRs 28 and 31, and from planning/Relations.md; the decisions themselves
are unchanged. The planning doc also records where in-flow-created
Subjects land now that a Subject can be moved, carries the page-scoped vs
free-standing question from the issue so closing it does not lose the
question, and points at the identifier rename that follows
(#1367).
Considered, omitted: the identifier and API renames themselves and the
API docs that describe them, tracked in
#1367 for after
#1265 lands. ADR 7 keeps
its wording as an accepted record.