SKG - Process for graph change

MEETING SUMMARY - SKG Graph Review Process Context: Multum team (Michael, Sy, George) with SKG support (Judy, Travis). Multum was an early SKG adopter who skipped the formal graph review and is now going back through the process. Core graph is ~1GB. ============================================================================= KEY PROCESS CLARIFICATIONS ============================================================================= MATERIAL CHANGE - no hard rule, judgment-based: - Minor (no review needed): adding a few attributes, a new class or two - Material (review required): multiple class changes, restructuring, anything generating more than ~2-5 new queries on the consumer side - Follow-up reviews will be much lighter than the initial - only new/changed items need to be documented, not the full graph again POC vs GRAPH REVIEW - same process, different threshold: - POC is a play area; much is allowed to slide - Formal review triggers when moving from POC to DevStage Broad - Multum has never formally reviewed despite being in the environment UPLOAD BEHAVIOR: - Replace, not additive. Uploading a partial file wipes everything else in the graph. STABLE vs LATEST: - Concept exists in the platform but not yet fully implemented - Both currently point to the same graph DATA vs STRUCTURE RELEASE CYCLES: - Travis acknowledged Multum's situation is atypical - Data updates and structural updates run on different cadences for Multum - Current model (upload to dev, engineer promotes to stage/prod) does not fit a weekly or daily data refresh cycle - Flagged for deeper discussion NEW AUTOMATED REVIEW PROCESS (rolling out soon): - Check out a repo, run an intake wizard (requires Codex) - Paste your schema/trig file and sample queries - Agent auto-checks against requirements and generates a markdown report - Address issues or annotate disagreements, then submit a pull request - Manual review focuses only on flagged items - Travis invited Multum to dog-food the new process with their existing review ============================================================================= ACTION ITEMS ============================================================================= Michael Attend Wednesday office hours slot already booked Michael Book additional office hours Monday or Tuesday with Travis to discuss data release cycle and multi-environment versioning Michael Pull the SKG DevOps repo, install Codex, run intake wizard with schema-only trig file (no instance data needed) Michael Find/share intake review doc and ontology doc already posted to Confluence Travis Watch for Multum's existing review submission ahead of Wednesday Travis/ Publish Confluence page and support channel announcement for SKG new automated review process SKG No timeline yet on stable vs latest implementation - open item