Query cheat sheet

Note variables {{…}}

In a graph-query block in Obsidian, {{name}} is replaced by a value of the note holding the block, written as a Cypher literal, before the query is parsed. Values below are for Projects/Atlas/Plan.md with this frontmatter:

---
type: Project
title: Atlas plan
status: active
budget: 1200
draft: false
tags: [graph, ml]
address: {city: Lviv}
---

• Strings are quoted and escaped, so a value with quotes cannot break or extend the query.
• Spaces inside the braces are allowed: {{ fm.status }}.
• Only names and dots are substituted. Nothing is evaluated: {{fm.budget * 2}} stays in the text and fails to parse. Write {{fm.budget}} * 2 instead.
• Line numbers are kept, so error positions still point into the block.
• Substitution happens before the backend is chosen, so variables work with backend: ladybug too.
• Blocks re-run when the note changes, so a block that uses {{fm.*}} follows edits to its own frontmatter.

tg cypher graph (code projects)

tg cypher and the tg_cypher MCP tool query a graph of lat.md/ sections, spec requirements and, with --code annotated|all, source code. Every node also has path (its id) and title, plus type.

• Edges: contains (parent section to child, requirement to scenario), references (plain wiki links and openspec:/specs: frontmatter), and every typed edge line with its {properties}.
• @tg: edges from code carry what you wrote, such as r.since. When the comment sits above a test call they also carry r.test, the test's name.
• Test-spec sections in a file typed Scenario are labelled Scenario too. Use s.scenario IS NOT NULL to keep only spec scenarios.

Ladybug backend

With backend: ladybug the names are the same and the same text runs. The differences:

• keys, properties, startNode and endNode are not available.
• n.title, n.stub, r.id and r.sign are stored columns. Other properties get a typed column per kind, so one property holding numbers in some notes and text in others is read as one kind, with a notice.
• UNWIND, CASE and other read Cypher outside the built-in subset run there.

Recipes

```graph-query
MATCH (me {path: {{path}}})-[r]-(x)
RETURN me, r, x
```

```graph-query
view: table

MATCH (x)-[r]->(me {path: {{path}}})
RETURN x.title AS from, type(r) AS edge,
       r.sign AS sign
```

```graph-query
MATCH (n)
WHERE n.path STARTS WITH {{folder}} + '/'
  AND n.path <> {{path}}
RETURN n.title ORDER BY n.title
```

```graph-query
MATCH (p:Project)
WHERE p.status = {{fm.status}}
  AND p.path <> {{path}}
RETURN p.title, p.budget
```

MATCH (n) WHERE 'ml' IN n.tags
RETURN n.title

MATCH (a)-[r]->(b) WHERE r.sign = -1
RETURN a.title, type(r), b.title

MATCH (a)-[r]->(s) WHERE s.stub
RETURN a.path, type(r), s.title

MATCH p = (n {path: $activeFile})
          -[:knows*1..2]->(y)
RETURN p

tg cypher "MATCH (s:Section)
  WHERE s.file = 'lat.md/cli.md'
  RETURN s.title, s.startLine"

tg cypher "MATCH (q:Requirement)
  OPTIONAL MATCH (c)-[i:implements]->(q)
  WITH q, count(i) AS n WHERE n = 0
  RETURN q.requirement, q.status"