Skip to content

Drop the "Child Subject" term; record what a page's Subjects are - #1368

Merged
JeroenDeDauw merged 2 commits into
masterfrom
docs/drop-child-subject-term
Sep 7, 2026
Merged

Drop the "Child Subject" term; record what a page's Subjects are#1368
JeroenDeDauw merged 2 commits into
masterfrom
docs/drop-child-subject-term

Conversation

@JeroenDeDauw

Copy link
Copy Markdown
Member

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.

AI-authored — Claude Code, Fable 5 (max); from @JeroenDeDauw's #959 decision and an in-session brief to keep it minimal, one redirection; not yet human-reviewed; blind-judge pass applied, links checked, lines within 120.

JeroenDeDauw and others added 2 commits September 7, 2026 19:31
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
JeroenDeDauw force-pushed the docs/drop-child-subject-term branch from eb0ad84 to 204d703 Compare September 7, 2026 17:31
@JeroenDeDauw
JeroenDeDauw marked this pull request as ready for review September 7, 2026 17:36
@JeroenDeDauw
JeroenDeDauw merged commit 987cd7f into master Sep 7, 2026
18 checks passed
@JeroenDeDauw
JeroenDeDauw deleted the docs/drop-child-subject-term branch September 7, 2026 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Define semantics of Main Subject and Child Subjects

1 participant