[Phase 1] Implement the canonical graph document and type registry #7

New issue

Closed

opened 2026-07-25 21:52:35 +00:00 by lost-rob0t · 0 comments

lost-rob0t commented

2026-07-25 21:52:35 +00:00

(Migrated from github.com)

Parent: #2
Depends on: #4, #6

Scope

Define graph metadata, nodes, edges, positions, viewport, type-library references, timestamps, and extension fields.
Implement stable identifiers and graph invariants.
Build a small node/edge type registry with property definitions, endpoint constraints, display hints, and generic unknown-type fallback.
Keep the model free of React, Cytoscape, storage, and network dependencies.

Acceptance criteria

Blank and typed graph documents can be created and validated.
Invalid identifiers, dangling edges, duplicate IDs, and endpoint violations are rejected.
Unknown types remain visible and serializable.
Core model passes fixture conformance tests.

Parent: #2 Depends on: #4, #6 ## Scope - Define graph metadata, nodes, edges, positions, viewport, type-library references, timestamps, and extension fields. - Implement stable identifiers and graph invariants. - Build a small node/edge type registry with property definitions, endpoint constraints, display hints, and generic unknown-type fallback. - Keep the model free of React, Cytoscape, storage, and network dependencies. ## Acceptance criteria - Blank and typed graph documents can be created and validated. - Invalid identifiers, dangling edges, duplicate IDs, and endpoint violations are rejected. - Unknown types remain visible and serializable. - Core model passes fixture conformance tests.