FPF Reference

G.Core:3 - Forces

Preface node heading:g-core-3-forces:54313

Content

  • Single source of truth vs. usability: We must centralize universal invariants, but G.x must remain readable and pattern-scoped for authors.
  • Delegation-first vs. completeness: Many norms already have canonical owners (A.6.7 / A.15.3 / A.19 / G.0 / A.19.CHR / E.*). G.Core must route to them rather than duplicating semantics.
  • Backwards compatibility: Public CC IDs and legacy trigger tokens must remain stable; deduplication must not break citations.
  • Typed change control: RSCR/refresh must become id‑based (catalogued trigger kinds) rather than prose-based “meaning”.
  • Strict distinction: Keep contract surfaces (CN‑Spec, CG‑Spec), suites, kits/surfaces, policies, planned baselines, audits, and refresh orchestration distinct.
  • Minimal specificity naming: New IDs must be kind‑suffixed and minimally specific, to reduce semantic lock‑in while remaining precise.
  • Phase‑2 scope discipline: G.Core must not become a container for discipline/method/generator taxonomies; those remain pattern-scoped (Extensions), delegated to existing owner‑patterns, or marked Phase‑3 seeds (appendix) without new Phase‑2 norms.