LDC-Q1001 — The snapshot holds a node kind the schema never declared

What it means

A snapshot lists typed nodes, and every node carries a kind such as a type or symbol declaration. The engine checks each kind against the schema before loading anything: an unknown kind means the snapshot was not produced from a package the schema describes, so the load stops at the first offending node instead of reasoning over foreign data.

Fix the snapshot at its source so every node kind comes from the schema, then run the query again. The query text itself is not at fault.

Example

run

{"argv": ["query", "from r in rules select r", "--path", "$ROOT/world.json"], "expect": "LDC-Q1001", "files": {"world.json": "{\"nodes\": [{\"id\": \"n1\", \"kind\": \"NoSuchKind\"}], \"package\": {\"name\": \"demo.diagnostics\", \"namespace\": \"urn:law:demo:diagnostics\"}}"}}

Fix

run

{"argv": ["query", "from r in rules select r", "--path", "$ROOT/world.json"], "expect": "LDC-Q1001", "files": {"world.json": "{\"nodes\": [{\"id\": \"n1\", \"kind\": \"type_decl\"}], \"package\": {\"name\": \"demo.diagnostics\", \"namespace\": \"urn:law:demo:diagnostics\"}}"}}

Engine message

The engine reports this in its own wording:

Output

LDC-Q1001: $ROOT/world.json: node kinds unknown to the schema: ['NoSuchKind'].

Related

• Questions to the engine — what a snapshot carries.
• LDC-Q1004 — when a node carries no identifier.