notations: family selection — FGCA, FGA, Goals, Activities#10
Closed
transitrix wants to merge 1 commit into
Closed
notations: family selection — FGCA, FGA, Goals, Activities#10transitrix wants to merge 1 commit into
transitrix wants to merge 1 commit into
Conversation
Replace the placeholder "Picking between FGCA, FGA, Goals, Activities" paragraph in `notations/README.md` with a fuller "Family selection" section that answers the relationship question once. The section carries: - Layer-composition table — which of F, G, C, A each of the four notations covers (FGCA = F+G+C+A; FGA = F+G+A; Goals tree = G alone; Activities = A alone). - Selection matrix — input situation → recommended notation, covering the typical strategy-to-execution scenarios. - Form rule — nested for tree-shaped notations (FGA, Goals), flat for DAG-shaped notations (FGCA, Activities). Records the rule of thumb "if a child can have multiple parents in the semantic graph, the notation uses the flat form." Decided 2026-05-20 alongside the FGCA schema. Specs 02-fgca, 03-fga, 04-goals, and 07-activities each gain a one-line cross-link to the new section. 02-fgca on main has no References list today, so the link lands in a new "See also" section at the end of the spec; the other three add the line to their existing References list. Refs: vkgeorgia/strategy#17 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
ab53978 to
34595e3
Compare
transitrix
added a commit
that referenced
this pull request
May 21, 2026
Replace the placeholder "Picking between..." paragraph in notations/README.md with a fuller "Family selection" section: layer composition table, situation-to-notation selection matrix, and the nested-for-trees / flat-for-DAGs form rule. Specs 02-fgca, 03-fga, 04-goals, 07-activities each gain a one-line cross-link to the new section. On 02-fgca the link joins the existing References list (introduced by the FGCA schema work) rather than a separate "See also" section. Rebased onto current main: was task/17-family-selection (PR #10), which forked before the CONTRACT / FGCA-schema / IDs-appendix / status-vocabulary PRs merged. Refs: vkgeorgia/strategy#17
Owner
Author
|
Superseded by #11. This branch ( Closing in favour of #11. |
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.
Summary
notations/README.mdwith a fuller Family selection section.Closes vkgeorgia/strategy#17.
Where the matrix lives — coordinated with #10
Per the agreement in #4 (closing strategy#10), the family selection matrix lands in
notations/README.mdrather than its own file. The four specs link to it; the README owns it. No duplication.Form rule
Documented the decision recorded 2026-05-20 alongside the FGCA schema (#7): if a child element can have multiple parents in the semantic graph, the notation uses the flat form. Examples: FGCA (one Change → many Goals; one Activity → many Changes) and the Activities network (predecessor fan-out) → flat. FGA and the Goals tree (single parent per child) → nested.
Scope guard
Per the issue refinement, this PR touches only the README family-selection section and adds the cross-link line in each of the four specs. No spec rewrites beyond that line; no example edits; no audit items.
Cross-link placement
02-fgca.mdon main has no References list today, so the cross-link lands in a new "See also" section at the end. When notations/02-fgca: add flat-form schema and rewrite example #7 merges (which introduces FGCA's References list), the cross-link will sit alongside the other references. The two locations don't conflict but a future cleanup could fold them together.03-fga.md,04-goals.md,07-activities.mdadd the line to their existing References list.Test plan
notations/README.mdcarries the Family selection section with the three subsections (layer composition table, selection matrix, form rule).grep "Family selection" notations/*.mdshows them all).vkgeorgia/strategyrepo in any shipped file.🤖 Generated with Claude Code