Skip to content

GFQL type-system T1: schema contract + canonical naming alignment #1296

Description

@lmeyerov

Summary

Execution slice T1 under #1262.

Define and land core schema model / canonical naming alignment for current GraphSchemaCatalog + GFQLSchema reality, with minimal stable contracts.

Scope

In scope:

  • Canonical naming alignment and contract doc/tests
  • Minimal stable interfaces needed by downstream T2/T3
  • No behavioral regressions for loose/default mode

Out of scope:

  • Binder strict-mode validation implementation (T2)
  • Nullability/type propagation implementation (T3)

Acceptance

  1. Canonical schema contracts are explicit and test-backed.
  2. Naming alignment between GraphSchemaCatalog and GFQLSchema is codified.
  3. Follow-on slices (T2/T3) have concrete interfaces to build against.
  4. Links and receipts posted back to Meta: #1046 native type-system staged decomposition program #1262 and Meta: GFQL compiler/planner post-M4 execution DAG (active wave) #1259.

Related

Activity

  1. lmeyerov commented on May 5, 2026

    @lmeyerov
    ContributorAuthor

    Implementation is up in PR #1298: https://github.com/graphistry/pygraphistry/pull/1298\n\nScope landed:\n- GraphSchemaCatalog canonical contract helpers/accessors\n- Focused tests for normalization/canonical naming behavior\n- CHANGELOG development entry\n\nValidation used in PR:\n- focused IR tests + M0B conformance\n- Ruff on touched files\n\nCI status: green (including tck-gfql and docs checks).

  2. lmeyerov commented on May 5, 2026

    @lmeyerov
    ContributorAuthor

    Merged via PR #1298: https://github.com/graphistry/pygraphistry/pull/1298\n\nMerge commit: 559bdc7\nMerged at: 2026-05-05T02:18:37Z\n\nAcceptance receipts:\n- Canonical schema contracts are explicit and test-backed\n- GraphSchemaCatalog/GFQLSchema naming alignment is codified\n- Follow-on slices have stable interfaces to build against\n\nPosted parent/meta updates in #1262 and #1259.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions