Repository navigation
GFQL type system follow-on A: public declarative schema model + stable exports #1337
Description
Summary
Follow-on child slice for #1046: provide a stable public declarative schema surface that maps cleanly to current internal GFQL schema catalogs.
Parent
- Umbrella: [FEA] GFQL native type system: schemas, inference, validation, and Arrow representation #1046
- Program predecessor: Meta: #1046 native type-system staged decomposition program #1262 (completed internal staging)
Goal
Expose a user-facing schema declaration API (node/edge/schema contracts) with stable import paths, while preserving compatibility with current binder/preflight internals.
In scope
- Public schema model module(s) and stable exports
- Declarative node/edge contracts, including topology constraints
- Adapter path from public schema objects to internal
GraphSchemaCatalog - Strict/permissive validation policy wiring at schema-binding seam
Out of scope
- Schema inference implementation
- Public Arrow/plottable schema boundary APIs
Acceptance
- Users can declare graph schema objects via stable public imports.
- Declared schema can be bound and consumed by binder/preflight validation.
- Topology/property mismatches produce clear compile-time/preflight diagnostics.
- Tests cover declaration, adapter mapping, and schema-bound validation behavior.
- CHANGELOG/docs updated with public API contract and migration notes.
Activity
lmeyerov commentedon May 7, 2026
Scoping alignment note: lane D #1345 tracks cross-lane API contract alignment in parallel.\n\nThis lane A issue remains independently executable and non-blocked by D; please include compatibility notes needed for D drift checks.
lmeyerov commentedon May 17, 2026
Coordinator research follow-up note for #1337 / #1457 scope:
The type-system research reinforces keeping this lane narrow:
NodeType/EdgeTypeshould be treated as trait-like contracts, not nominal Java-style classes.(:A:B)should eventually merge trait/property fragments, but conflict/presence policy belongs in follow-ons, not this merge gate.Follow-ons now carry the broader work:
Practical coordinator rule: do not block #1457 on the full graph type calculus.
lmeyerov commentedon May 20, 2026
Coordinator audit cross-link: typed-schema cluster dispatch audit posted on #1058:
#1058 (comment)
This issue/PR was included in the 2026-05-20 audit covering #1457/#1337/#1338/#1339/#1485/#1465 and downstream implications for #1567/#1580.
lmeyerov commentedon May 25, 2026
Merged PR #1457 as
3d85344d083295a05c7619baa1a5e415a8d69b8f.Closeout:
NodeType,EdgeType,GraphSchema,EdgeTopologyfromgraphistry.schemaplus top-level re-exports.graphistry.edges(...).nodes(...).bind(schema=schema)graph binding.gfql_remote(...)does not transport the boundGraphSchema.117e52436974e2cf8681f2712c6f68adda0e6c8b.Follow-ons remain #1338 schema inference, #1339 Arrow/plottable boundary enforcement/coercion, #1485 schema effects, and #1465 remote schema transport.