Lineage Graphs
About Lineage Graphs
Section titled “About Lineage Graphs”A lineage graph is an interactive visualizer of a lineage manifest — a cryptographically verifiable record of how a dataset, model, or other asset was produced, generated by the EQTY SDK. It lets you trace and evidence every step of your workflow while flagging any assets that require further verification.
Lineage graphs render each asset and computation in a manifest as a node, and the connections between them as edges, so you can follow exactly how an output was derived from its inputs. Every node can be inspected for its registration details, verification status, and any metadata attached during creation.
Key concepts and actions associated with Lineage Graphs include:
- Understanding Lineage Graph scope
- Understanding node types
- Viewing a Lineage Graph
- Navigating a Lineage Graph
- Understanding verification statuses
- Viewing node instances
Understanding Lineage Graph scope
Section titled “Understanding Lineage Graph scope”Lineage graphs live within a single project and cannot be shared or viewed across projects. A project can contain multiple lineage graphs, each corresponding to a manifest registered by the SDK.
Any project member with access to the project can view its lineage graphs.
Understanding node types
Section titled “Understanding node types”A Lineage Graph is made up of nodes connected by edges. Each node represents an asset or computation registered by the SDK. Node types include:
- Agent
- Benchmark
- Benchmark Result
- Binary
- Certificate
- Code
- Computation
- Configuration
- Credential
- Database
- Dataset
- Document
- Guardrail
- Media
- Model
- Prompt
- Reasoning
- Skill
- System Prompt
- Token
- Tool
A node whose type the manifest does not name is shown as Unknown.
An edge between two nodes indicates a direct relationship — for example, a computation node connected to a dataset node means that dataset was either an input to or an output of that computation.
Viewing a Lineage Graph
Section titled “Viewing a Lineage Graph”To view a project’s Lineage Graphs:
- Select a project from Projects
- Select the Lineage Graphs tab
- Search for a graph by name or ID, or select one from the list
- Select View Lineage
This opens the graph in an interactive canvas.
Navigating a Lineage Graph
Section titled “Navigating a Lineage Graph”Once a graph is open, you can:
- Pan and zoom the canvas to explore the graph’s structure
- Select a node to open its detail panel
- Toggle between graph and table view using the Graph view / Table view selector in the top-right corner of the canvas
- Download the lineage manifest as a JSON
Node detail panel
Section titled “Node detail panel”Selecting a node opens a detail panel with the following sections:
Registration
- Node ID: The node’s unique content identifier (CID).
- Timestamp: When the node was registered. Computation nodes use this label; every other node type labels the same field Instance — see Viewing node instances.
- Registered By: The signer who registered the node, including any attached user information (such as name or email).
- Executed On: The identity of the host the workload ran on, shown as a signer badge. Computation nodes only.
- Operated By: The signer who operated the workload. Computation nodes only.
- Anchors: Any external anchor recorded for the node, shown as
type:txHash, each with a View link to the anchor’s explorer. - Statement: The node’s registration record, and its verification status – with an option to View JSON.
- Credential: The node’s Verifiable Credential attesting to the statement, and its verification status – with an option to View JSON.
Metadata
Any additional metadata attached to the node during registration, such as description, contact information, license, or other domain-specific fields defined by the SDK user.
Understanding verification statuses
Section titled “Understanding verification statuses”Each node’s Statement and Credential are independently verified in your browser to confirm they haven’t been tampered with. A node can show one of two statuses for each:
- Verified: The statement or credential’s cryptographic proof is valid.
- Unverified: The statement or credential’s cryptographic proof could not be validated.
An Unverified status should be investigated — it means the integrity of that particular statement or credential cannot be confirmed, even if the rest of the graph verifies successfully.
Viewing node instances
Section titled “Viewing node instances”A node can have multiple instances if the underlying asset was registered more than once — for example, across separate runs. When a node has multiple instances, its detail panel includes an Instance dropdown listing each registration, along with the timestamp for each.
Selecting a different instance updates the detail panel to show that instance’s Registration and Metadata.