Skip to content

Typed node system / node schema (ReactFlow-compatible) #282

Open

Description

@codeforstartups

Context

Every orchestration primitive is a node with typed inputs/outputs/config and typed ports. The schema must serialize to a ReactFlow-compatible shape so the SDK and the canvas share one model.

Scope

  • Node base class/schema: typed inputs, outputs, config, ports
  • Serialize/deserialize nodes + edges to a stable JSON graph format
  • Validation: port type compatibility across edges
  • Round-trip a graph: SDK object → JSON → SDK object

Acceptance criteria

  • A node declares typed ports and config and (de)serializes losslessly
  • Connecting incompatible ports raises a clear validation error
  • JSON format is documented and versioned

References

Roadmap doc, §5 (Node system), §6.


Part of #273 (flow).

Imported from the dynavec — Agent Orchestration Roadmap.

Activity

  1. Ashishds commented on Oct 14, 2026

    @Ashishds
    Contributor

    Hi @abhishek.rdx, I would like to take this up!

    Having recently contributed the core graph engine (#344), I can implement the typed port compatibility validation across edges and the lossless round-trip ReactFlow-compatible graph serialization/deserialization (SimpleGraph.to_dict() / from_dict()).

    Please assign this issue to me.

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions