notations/02-fgca: add flat-form schema and rewrite example#7
Merged
Conversation
02-fgca.md previously carried only business prose and no schema, so an FGCA file had nothing to validate against. Add the schema sections matching the depth of 03-fga and 04-goals: - File location and naming. - Top-level structure — flat form: a single `fgca:` root key holds document metadata, and `factors` / `goals` / `changes` / `activities` are parallel arrays under it. Links between layers are id-references, not nesting. Rationale: the Changes layer makes FGCA a DAG (one change can deliver many goals; one activity can deliver many changes), which the flat form expresses without node duplication. FGA and Goals stay nested in their own specs — they are tree-shaped. - Fields tables for the root and each layer. - Validation rules FGCA-001 … FGCA-014. - References to FGA, Goals, Activities, methodology. The example `notations/examples/fgca/strategy-2026.fgca.transitrix.yaml` is rewritten to match: metadata wrapped under `fgca:`; string IDs of the form `<TYPE>-<INTEGER>` (FACTOR-1, GOAL-1, CHANGE-1, ACTIVITY-1) per the canonical grammar; id-reference cross-links between layers (goals reference factors; changes reference goals; activities reference changes). The example parses and all cross-references resolve. Front-matter version 1.1 → 1.2 (additive schema section). Refs: vkgeorgia/strategy#15 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 21, 2026
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
1 participant
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
02-fgca.mdpreviously carried only the business description; no schema, no validation rules. Now adds File location, Top-level structure (flat form), Fields, Validation rules, References — matching the depth of03-fga.md/04-goals.md.fgca:root key holds document metadata;factors/goals/changes/activitiesare parallel arrays under it; links between layers are id-references on each item, not nesting. FGA and Goals stay nested in their own specs — they are tree-shaped.notations/examples/fgca/strategy-2026.fgca.transitrix.yamlto match the new schema: metadata underfgca:, string IDs (FACTOR-1,GOAL-1,CHANGE-1,ACTIVITY-1), id-reference cross-links.Closes vkgeorgia/strategy#15.
Scope guard
Per the issue refinement, this PR touches only the FGCA spec and its example. FGA, Goals, and other specs are untouched. No audit items picked up.
ID grammar (forthcoming appendix)
IDs use the canonical grammar
<TYPE>-[<middle segment(s)>-]<INTEGER>withACTIVITY-replacing the olderACT-andCHANGE-as the FGCA change-layer prefix. The full grammar and TYPE registry will land in a forthcomingIDS_AND_REFERENCES.mdappendix; the spec body refers to it by anticipated filename rather than hyperlinking.Test plan
yaml.safe_load).goals[].factors[],changes[].goals[],activities[].changes[]ID resolves to a defined entity in its target layer.vkgeorgia/strategyrepo in shipped files (lesson from64d2e72).🤖 Generated with Claude Code