Truncation and revision mismatch

A bounded result carries more than nodes

Query results have scope and limits. Budgets can constrain the number of nodes or edges, traversal depth, path count or query duration. These bounds make exploration practical, but they also affect what a result can establish.

States and the next useful action

• Complete within the requested scope: interpret the result against that scope, not the entire runtime system.

• Truncated: some candidates may be omitted. Narrow the subject or use an appropriate supported budget.

• Partial capability: the requested semantics are not fully represented by this analyzer or adapter. Check the support guide.

• Revision mismatch: the expected revision and the available source/index state differ. Refresh before combining observations.

• Unavailable or failed: the query did not establish the requested result. Do not report an empty answer as success.

Example: no path in a shallow query

A shallow path search can fail to reach a target that is connected through more intermediate nodes. The useful report is “no path returned under these bounds.” First check the endpoints and direction, then decide whether a larger or more focused query is appropriate.

{
  "subject": "checkout-service.ts",
  "observation": "Inspect returned consumers",
  "revision": "record the actual indexed revision",
  "limits": ["record any truncation or partial coverage"]
}

Inspect the view notice

The captured notice says that the view shows part of the project and that its counts apply to loaded elements. Treat that as a scope statement. Do not report the number of visible nodes as the total number of matching entities in the repository.