← All workshopsRead Which Connected Records Can the Assistant Use?

Graph Databases

Collect evidence through permitted routes

BOTIE

Restrict nodes to the supplied tenant and retain only edges with both endpoints inside it. Inspect what happens to the route through X before collecting documents.
Ready to test
0 passed · 0 failed · 3 not run

An empty floor. Start with the information your machine needs.

Received result

Your answer will arrive here.

Examples, experiments and workspace controls
Live values

Connect a tool's inputs to see what it produces. You can try a branch before connecting it to Result.

Try your own inputs

Use a copy of the example to try your own data. Keep the problem's assumptions in mind, and predict the effect of a change before checking the output. You can also add another branch to compare two ways of doing the calculation.

Start at an output arrow, then click or drag to an input. Drag empty space to pan. Delete removes a selection. Ctrl/Cmd+Z undoes a change.
Context for this challenge

Restrict nodes to the supplied tenant and retain only edges with both endpoints inside it. Inspect what happens to the route through X before collecting documents.

Future documents and routes through another tenant must not enter the context.

Inspect the component calculation
Restrict the graph before expansion(
  Graph: Invented graph snapshot
  Tenant ID: Permitted tenant
)
Examples and results
Invented graph snapshot
The nodes and directed relationships in this value.Records: P7; Asset; tenant: red. S1; Asset; tenant: red. X; Asset; tenant: blue. D1; Document; tenant: red; available_at: 2. D2; Document; tenant: red; available_at: 8. D3; Document; tenant: red; available_at: 1. Relationships: P7 to S1: DEPENDS_ON. P7 to X: DEPENDS_ON. P7 to D1: HAS_MANUAL. S1 to D2: HAS_MANUAL. X to D3: HAS_MANUAL. Full records and relationships are also listed below the diagram.P7 to S1: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to X: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to D1: HAS_MANUALHAS_MANUALHAS_MANUALS1 to D2: HAS_MANUALHAS_MANUALHAS_MANUALX to D3: HAS_MANUALHAS_MANUALHAS_MANUALP7P7AssetAssettenant: redtenant: redS1S1AssetAssettenant: redtenant: redXXAssetAssettenant: bluetenant: blueD1D1DocumentDocumenttenant: redtenant: redavailable_at: 2available_at: 2D2D2DocumentDocumenttenant: redtenant: redavailable_at: 8available_at: 8D3D3DocumentDocumenttenant: redtenant: redavailable_at: 1available_at: 1
Nodes and properties (6)
  • P7 · Asset
    • tenant: red
  • S1 · Asset
    • tenant: red
  • X · Asset
    • tenant: blue
  • D1 · Document
    • tenant: red
    • available_at: 2
  • D2 · Document
    • tenant: red
    • available_at: 8
  • D3 · Document
    • tenant: red
    • available_at: 1
  • P7 to S1: DEPENDS_ON
  • P7 to X: DEPENDS_ON
  • P7 to D1: HAS_MANUAL
  • S1 to D2: HAS_MANUAL
  • X to D3: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "P7",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "S1",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "X",
      "kind": "Asset",
      "tenant": "blue"
    },
    {
      "id": "D1",
      "kind": "Document",
      "tenant": "red",
      "available_at": 2
    },
    {
      "id": "D2",
      "kind": "Document",
      "tenant": "red",
      "available_at": 8
    },
    {
      "id": "D3",
      "kind": "Document",
      "tenant": "red",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "d",
      "source": "P7",
      "target": "S1",
      "type": "DEPENDS_ON"
    },
    {
      "id": "cross",
      "source": "P7",
      "target": "X",
      "type": "DEPENDS_ON"
    },
    {
      "id": "m1",
      "source": "P7",
      "target": "D1",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m2",
      "source": "S1",
      "target": "D2",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m3",
      "source": "X",
      "target": "D3",
      "type": "HAS_MANUAL"
    }
  ]
}
Permitted tenant
red
Required result
The nodes and directed relationships in this value.Records: P7; Asset; tenant: red. S1; Asset; tenant: red. D1; Document; tenant: red; available_at: 2. D2; Document; tenant: red; available_at: 8. D3; Document; tenant: red; available_at: 1. Relationships: P7 to S1: DEPENDS_ON. P7 to D1: HAS_MANUAL. S1 to D2: HAS_MANUAL. Full records and relationships are also listed below the diagram.P7 to S1: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to D1: HAS_MANUALHAS_MANUALHAS_MANUALS1 to D2: HAS_MANUALHAS_MANUALHAS_MANUALP7P7AssetAssettenant: redtenant: redS1S1AssetAssettenant: redtenant: redD1D1DocumentDocumenttenant: redtenant: redavailable_at: 2available_at: 2D2D2DocumentDocumenttenant: redtenant: redavailable_at: 8available_at: 8D3D3DocumentDocumenttenant: redtenant: redavailable_at: 1available_at: 1
Nodes and properties (5)
  • P7 · Asset
    • tenant: red
  • S1 · Asset
    • tenant: red
  • D1 · Document
    • tenant: red
    • available_at: 2
  • D2 · Document
    • tenant: red
    • available_at: 8
  • D3 · Document
    • tenant: red
    • available_at: 1
  • P7 to S1: DEPENDS_ON
  • P7 to D1: HAS_MANUAL
  • S1 to D2: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "P7",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "S1",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "D1",
      "kind": "Document",
      "tenant": "red",
      "available_at": 2
    },
    {
      "id": "D2",
      "kind": "Document",
      "tenant": "red",
      "available_at": 8
    },
    {
      "id": "D3",
      "kind": "Document",
      "tenant": "red",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "d",
      "source": "P7",
      "target": "S1",
      "type": "DEPENDS_ON"
    },
    {
      "id": "m1",
      "source": "P7",
      "target": "D1",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m2",
      "source": "S1",
      "target": "D2",
      "type": "HAS_MANUAL"
    }
  ]
}
Invented graph snapshot
The nodes and directed relationships in this value.Records: P7; Asset; tenant: red. S1; Asset; tenant: red. X; Asset; tenant: blue. D1; Document; tenant: red; available_at: 2. D2; Document; tenant: red; available_at: 8. D3; Document; tenant: red; available_at: 1. Relationships: P7 to S1: DEPENDS_ON. P7 to X: DEPENDS_ON. P7 to D1: HAS_MANUAL. S1 to D2: HAS_MANUAL. X to D3: HAS_MANUAL. Full records and relationships are also listed below the diagram.P7 to S1: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to X: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to D1: HAS_MANUALHAS_MANUALHAS_MANUALS1 to D2: HAS_MANUALHAS_MANUALHAS_MANUALX to D3: HAS_MANUALHAS_MANUALHAS_MANUALP7P7AssetAssettenant: redtenant: redS1S1AssetAssettenant: redtenant: redXXAssetAssettenant: bluetenant: blueD1D1DocumentDocumenttenant: redtenant: redavailable_at: 2available_at: 2D2D2DocumentDocumenttenant: redtenant: redavailable_at: 8available_at: 8D3D3DocumentDocumenttenant: redtenant: redavailable_at: 1available_at: 1
Nodes and properties (6)
  • P7 · Asset
    • tenant: red
  • S1 · Asset
    • tenant: red
  • X · Asset
    • tenant: blue
  • D1 · Document
    • tenant: red
    • available_at: 2
  • D2 · Document
    • tenant: red
    • available_at: 8
  • D3 · Document
    • tenant: red
    • available_at: 1
  • P7 to S1: DEPENDS_ON
  • P7 to X: DEPENDS_ON
  • P7 to D1: HAS_MANUAL
  • S1 to D2: HAS_MANUAL
  • X to D3: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "P7",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "S1",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "X",
      "kind": "Asset",
      "tenant": "blue"
    },
    {
      "id": "D1",
      "kind": "Document",
      "tenant": "red",
      "available_at": 2
    },
    {
      "id": "D2",
      "kind": "Document",
      "tenant": "red",
      "available_at": 8
    },
    {
      "id": "D3",
      "kind": "Document",
      "tenant": "red",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "d",
      "source": "P7",
      "target": "S1",
      "type": "DEPENDS_ON"
    },
    {
      "id": "cross",
      "source": "P7",
      "target": "X",
      "type": "DEPENDS_ON"
    },
    {
      "id": "m1",
      "source": "P7",
      "target": "D1",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m2",
      "source": "S1",
      "target": "D2",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m3",
      "source": "X",
      "target": "D3",
      "type": "HAS_MANUAL"
    }
  ]
}
Permitted tenant
red
Required result
The nodes and directed relationships in this value.Records: P7; Asset; tenant: red. S1; Asset; tenant: red. D1; Document; tenant: red; available_at: 2. D2; Document; tenant: red; available_at: 8. D3; Document; tenant: red; available_at: 1. Relationships: P7 to S1: DEPENDS_ON. P7 to D1: HAS_MANUAL. S1 to D2: HAS_MANUAL. Full records and relationships are also listed below the diagram.P7 to S1: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to D1: HAS_MANUALHAS_MANUALHAS_MANUALS1 to D2: HAS_MANUALHAS_MANUALHAS_MANUALP7P7AssetAssettenant: redtenant: redS1S1AssetAssettenant: redtenant: redD1D1DocumentDocumenttenant: redtenant: redavailable_at: 2available_at: 2D2D2DocumentDocumenttenant: redtenant: redavailable_at: 8available_at: 8D3D3DocumentDocumenttenant: redtenant: redavailable_at: 1available_at: 1
Nodes and properties (5)
  • P7 · Asset
    • tenant: red
  • S1 · Asset
    • tenant: red
  • D1 · Document
    • tenant: red
    • available_at: 2
  • D2 · Document
    • tenant: red
    • available_at: 8
  • D3 · Document
    • tenant: red
    • available_at: 1
  • P7 to S1: DEPENDS_ON
  • P7 to D1: HAS_MANUAL
  • S1 to D2: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "P7",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "S1",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "D1",
      "kind": "Document",
      "tenant": "red",
      "available_at": 2
    },
    {
      "id": "D2",
      "kind": "Document",
      "tenant": "red",
      "available_at": 8
    },
    {
      "id": "D3",
      "kind": "Document",
      "tenant": "red",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "d",
      "source": "P7",
      "target": "S1",
      "type": "DEPENDS_ON"
    },
    {
      "id": "m1",
      "source": "P7",
      "target": "D1",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m2",
      "source": "S1",
      "target": "D2",
      "type": "HAS_MANUAL"
    }
  ]
}
Invented graph snapshot
The nodes and directed relationships in this value.Records: P7; Asset; tenant: red. S1; Asset; tenant: red. X; Technician; tenant: red. D1; Document; tenant: red; available_at: 2. D2; Document; tenant: red; available_at: 8. D3; Document; tenant: red; available_at: 1. Relationships: P7 to S1: DEPENDS_ON. P7 to X: DEPENDS_ON. P7 to D1: HAS_MANUAL. S1 to D2: HAS_MANUAL. X to D3: HAS_MANUAL. Full records and relationships are also listed below the diagram.P7 to S1: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to X: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to D1: HAS_MANUALHAS_MANUALHAS_MANUALS1 to D2: HAS_MANUALHAS_MANUALHAS_MANUALX to D3: HAS_MANUALHAS_MANUALHAS_MANUALP7P7AssetAssettenant: redtenant: redS1S1AssetAssettenant: redtenant: redXXTechnicianTechniciantenant: redtenant: redD1D1DocumentDocumenttenant: redtenant: redavailable_at: 2available_at: 2D2D2DocumentDocumenttenant: redtenant: redavailable_at: 8available_at: 8D3D3DocumentDocumenttenant: redtenant: redavailable_at: 1available_at: 1
Nodes and properties (6)
  • P7 · Asset
    • tenant: red
  • S1 · Asset
    • tenant: red
  • X · Technician
    • tenant: red
  • D1 · Document
    • tenant: red
    • available_at: 2
  • D2 · Document
    • tenant: red
    • available_at: 8
  • D3 · Document
    • tenant: red
    • available_at: 1
  • P7 to S1: DEPENDS_ON
  • P7 to X: DEPENDS_ON
  • P7 to D1: HAS_MANUAL
  • S1 to D2: HAS_MANUAL
  • X to D3: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "P7",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "S1",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "X",
      "kind": "Technician",
      "tenant": "red"
    },
    {
      "id": "D1",
      "kind": "Document",
      "tenant": "red",
      "available_at": 2
    },
    {
      "id": "D2",
      "kind": "Document",
      "tenant": "red",
      "available_at": 8
    },
    {
      "id": "D3",
      "kind": "Document",
      "tenant": "red",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "d",
      "source": "P7",
      "target": "S1",
      "type": "DEPENDS_ON"
    },
    {
      "id": "cross",
      "source": "P7",
      "target": "X",
      "type": "DEPENDS_ON"
    },
    {
      "id": "m1",
      "source": "P7",
      "target": "D1",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m2",
      "source": "S1",
      "target": "D2",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m3",
      "source": "X",
      "target": "D3",
      "type": "HAS_MANUAL"
    }
  ]
}
Permitted tenant
red
Required result
The nodes and directed relationships in this value.Records: P7; Asset; tenant: red. S1; Asset; tenant: red. X; Technician; tenant: red. D1; Document; tenant: red; available_at: 2. D2; Document; tenant: red; available_at: 8. D3; Document; tenant: red; available_at: 1. Relationships: P7 to S1: DEPENDS_ON. P7 to X: DEPENDS_ON. P7 to D1: HAS_MANUAL. S1 to D2: HAS_MANUAL. X to D3: HAS_MANUAL. Full records and relationships are also listed below the diagram.P7 to S1: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to X: DEPENDS_ONDEPENDS_ONDEPENDS_ONP7 to D1: HAS_MANUALHAS_MANUALHAS_MANUALS1 to D2: HAS_MANUALHAS_MANUALHAS_MANUALX to D3: HAS_MANUALHAS_MANUALHAS_MANUALP7P7AssetAssettenant: redtenant: redS1S1AssetAssettenant: redtenant: redXXTechnicianTechniciantenant: redtenant: redD1D1DocumentDocumenttenant: redtenant: redavailable_at: 2available_at: 2D2D2DocumentDocumenttenant: redtenant: redavailable_at: 8available_at: 8D3D3DocumentDocumenttenant: redtenant: redavailable_at: 1available_at: 1
Nodes and properties (6)
  • P7 · Asset
    • tenant: red
  • S1 · Asset
    • tenant: red
  • X · Technician
    • tenant: red
  • D1 · Document
    • tenant: red
    • available_at: 2
  • D2 · Document
    • tenant: red
    • available_at: 8
  • D3 · Document
    • tenant: red
    • available_at: 1
  • P7 to S1: DEPENDS_ON
  • P7 to X: DEPENDS_ON
  • P7 to D1: HAS_MANUAL
  • S1 to D2: HAS_MANUAL
  • X to D3: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "P7",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "S1",
      "kind": "Asset",
      "tenant": "red"
    },
    {
      "id": "X",
      "kind": "Technician",
      "tenant": "red"
    },
    {
      "id": "D1",
      "kind": "Document",
      "tenant": "red",
      "available_at": 2
    },
    {
      "id": "D2",
      "kind": "Document",
      "tenant": "red",
      "available_at": 8
    },
    {
      "id": "D3",
      "kind": "Document",
      "tenant": "red",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "d",
      "source": "P7",
      "target": "S1",
      "type": "DEPENDS_ON"
    },
    {
      "id": "cross",
      "source": "P7",
      "target": "X",
      "type": "DEPENDS_ON"
    },
    {
      "id": "m1",
      "source": "P7",
      "target": "D1",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m2",
      "source": "S1",
      "target": "D2",
      "type": "HAS_MANUAL"
    },
    {
      "id": "m3",
      "source": "X",
      "target": "D3",
      "type": "HAS_MANUAL"
    }
  ]
}
Try a fresh construction

This clears this draft, including its undo history. Earlier successful attempts stay recorded. Build again without opening hints to record an independent attempt.

Stuck? Inspect a worked construction

The tools below form one possible solution. You can assemble it, follow its signals, and undo that change to return to your own construction.

Assumptions and test precision

These components operate on the supplied records in your browser. They do not run a graph database or interpret Cypher. Numerical tests allow a difference of 0.001. Lists and structures must also have the right shape.

Your last tested pieces can start the full construction. An existing draft there keeps its own pieces.

A permitted document sits beyond a forbidden detour

This check uses the pieces from “Compose bounded dependency and manual retrieval”.

BOTIE

For amber tenant asset R6 at hour ten, allow one dependency hop. Its own manual and S6's manual are available. Another amber manual is reachable only through a violet asset, S7 is two dependency hops away, and a future manual is dated eleven. Predict eligible Document IDs, inspecting scope before traversal.
Invented graph snapshot
The nodes and directed relationships in this value.Records: R6; Asset; tenant: amber. S6; Asset; tenant: amber. S7; Asset; tenant: amber. X6; Asset; tenant: violet. D-own; Document; tenant: amber; available_at: 10. D-supply; Document; tenant: amber; available_at: 4. D-detour; Document; tenant: amber; available_at: 2. D-deep; Document; tenant: amber; available_at: 3. D-future; Document; tenant: amber; available_at: 11. N-label; Note; tenant: amber; available_at: 1. Relationships: R6 to S6: DEPENDS_ON. S6 to S7: DEPENDS_ON. R6 to X6: DEPENDS_ON. R6 to D-own: HAS_MANUAL. S6 to D-supply: HAS_MANUAL. X6 to D-detour: HAS_MANUAL. S7 to D-deep: HAS_MANUAL. S6 to D-future: HAS_MANUAL. R6 to N-label: HAS_MANUAL. Full records and relationships are also listed below the diagram.R6 to S6: DEPENDS_ONDEPENDS_ONDEPENDS_ONS6 to S7: DEPENDS_ONDEPENDS_ONDEPENDS_ONR6 to X6: DEPENDS_ONDEPENDS_ONDEPENDS_ONR6 to D-own: HAS_MANUALHAS_MANUALHAS_MANUALS6 to D-supply: HAS_MANUALHAS_MANUALHAS_MANUALX6 to D-detour: HAS_MANUALHAS_MANUALHAS_MANUALS7 to D-deep: HAS_MANUALHAS_MANUALHAS_MANUALS6 to D-future: HAS_MANUALHAS_MANUALHAS_MANUALR6 to N-label: HAS_MANUALHAS_MANUALHAS_MANUALR6R6AssetAssettenant: ambertenant: amberS6S6AssetAssettenant: ambertenant: amberS7S7AssetAssettenant: ambertenant: amberX6X6AssetAssettenant: violettenant: violetD-ownD-ownDocumentDocumenttenant: ambertenant: amberavailable_at: 10available_at: 10D-supplyD-supplyDocumentDocumenttenant: ambertenant: amberavailable_at: 4available_at: 4D-detourD-detourDocumentDocumenttenant: ambertenant: amberavailable_at: 2available_at: 2D-deepD-deepDocumentDocumenttenant: ambertenant: amberavailable_at: 3available_at: 3D-futureD-futureDocumentDocumenttenant: ambertenant: amberavailable_at: 11available_at: 11N-labelN-labelNoteNotetenant: ambertenant: amberavailable_at: 1available_at: 1
Nodes and properties (10)
  • R6 · Asset
    • tenant: amber
  • S6 · Asset
    • tenant: amber
  • S7 · Asset
    • tenant: amber
  • X6 · Asset
    • tenant: violet
  • D-own · Document
    • tenant: amber
    • available_at: 10
  • D-supply · Document
    • tenant: amber
    • available_at: 4
  • D-detour · Document
    • tenant: amber
    • available_at: 2
  • D-deep · Document
    • tenant: amber
    • available_at: 3
  • D-future · Document
    • tenant: amber
    • available_at: 11
  • N-label · Note
    • tenant: amber
    • available_at: 1
  • R6 to S6: DEPENDS_ON
  • S6 to S7: DEPENDS_ON
  • R6 to X6: DEPENDS_ON
  • R6 to D-own: HAS_MANUAL
  • S6 to D-supply: HAS_MANUAL
  • X6 to D-detour: HAS_MANUAL
  • S7 to D-deep: HAS_MANUAL
  • S6 to D-future: HAS_MANUAL
  • R6 to N-label: HAS_MANUAL
Inspect the node and relationship records
{
  "nodes": [
    {
      "id": "R6",
      "kind": "Asset",
      "tenant": "amber"
    },
    {
      "id": "S6",
      "kind": "Asset",
      "tenant": "amber"
    },
    {
      "id": "S7",
      "kind": "Asset",
      "tenant": "amber"
    },
    {
      "id": "X6",
      "kind": "Asset",
      "tenant": "violet"
    },
    {
      "id": "D-own",
      "kind": "Document",
      "tenant": "amber",
      "available_at": 10
    },
    {
      "id": "D-supply",
      "kind": "Document",
      "tenant": "amber",
      "available_at": 4
    },
    {
      "id": "D-detour",
      "kind": "Document",
      "tenant": "amber",
      "available_at": 2
    },
    {
      "id": "D-deep",
      "kind": "Document",
      "tenant": "amber",
      "available_at": 3
    },
    {
      "id": "D-future",
      "kind": "Document",
      "tenant": "amber",
      "available_at": 11
    },
    {
      "id": "N-label",
      "kind": "Note",
      "tenant": "amber",
      "available_at": 1
    }
  ],
  "edges": [
    {
      "id": "dep1",
      "source": "R6",
      "target": "S6",
      "type": "DEPENDS_ON"
    },
    {
      "id": "dep2",
      "source": "S6",
      "target": "S7",
      "type": "DEPENDS_ON"
    },
    {
      "id": "cross",
      "source": "R6",
      "target": "X6",
      "type": "DEPENDS_ON"
    },
    {
      "id": "own",
      "source": "R6",
      "target": "D-own",
      "type": "HAS_MANUAL"
    },
    {
      "id": "supply",
      "source": "S6",
      "target": "D-supply",
      "type": "HAS_MANUAL"
    },
    {
      "id": "detour",
      "source": "X6",
      "target": "D-detour",
      "type": "HAS_MANUAL"
    },
    {
      "id": "deep",
      "source": "S7",
      "target": "D-deep",
      "type": "HAS_MANUAL"
    },
    {
      "id": "future",
      "source": "S6",
      "target": "D-future",
      "type": "HAS_MANUAL"
    },
    {
      "id": "wrong-kind",
      "source": "R6",
      "target": "N-label",
      "type": "HAS_MANUAL"
    }
  ]
}
Starting asset ID
R6
Permitted tenant
amber
Decision hour
10
Maximum dependency hops
1

Use a number, text, or an array matching the requested result. For a matrix, put each row in brackets. Saving your prediction runs your current construction on these inputs and checks the earlier examples too.

Build a construction in the workspace above first. This case will test those pieces.

How would you test whether the added graph context improves answers, and what should happen when no adequate evidence survives?

Evaluate evidence retrieval and generated claims separately, including forbidden evidence and unresolved questions.

These components operate on the supplied records in your browser. They do not run a graph database or interpret Cypher.

Work through the Python challenges →
← Where Did This Maintenance Claim Come From?