Search vault content with hybrid semantic + keyword search.

Get full content of a session by reading the markdown file directly.

Store a new thought — embed and save to vault as a qnote.

Re-index vault content into the search database.

Search the knowledge graph. Bounded: returns total_matched alongside a capped page, so a truncated result is visible rather than silent.

Create multiple new entities in the knowledge graph.

If an entity with the same name exists, new observations are merged.

Each entity can have:

• name (required): Entity name

• entityType: Type (default "concept")

• observations: List of observation strings

• epistemic: "assertion" | "hypothesis" | "speculation" (optional)

Observations are stored with temporal metadata (created date, status). Entities get activation tracking (activation=1.0, last_accessed=today).

Create multiple new relations between entities. Relations should be in active voice.

Canonical relation types: supports, contradicts, evolved_into, depends_on, exemplifies, part_of, caused_by, enables, supersedes, related_to.

Non-standard types are accepted but return a warning.

Add new observations to existing entities in the knowledge graph.

Write entities, relations and observations in one validated, atomic call.

This is the single write path. Everything is validated before anything is written, so a batch that is half-valid writes nothing.

Entity fields: name, entityType (required for new), domain (required for new), epistemic (assertion|hypothesis|speculation|unknown, default unknown), visibility (private|shareable, default private), observations. An observation may be a string, or {"text": ..., "kind": ...} where kind is note|decided|rejected|because|touches.

Relations use the canonical vocabulary; close synonyms are folded, unknown types are rejected. A relation may only point at an entity that exists or is being created in this same call.

Record a decision: what was chosen, what was rejected, and why.

rejected is the field that makes this worth recording. What was chosen stays readable in the code forever; what was considered and dropped exists nowhere else, and it is the question that gets asked months later.

Mark observations as no longer held, and link what replaced them.

Deliberately not a delete. Keeping the superseded belief, dated and linked, is what lets the archive answer "why did we change our mind" later.

If you pass superseding_entity, record that entity first — a relation cannot point at a name the graph does not know.

Delete multiple entities and their associated relations from the knowledge graph.

Delete specific observations from entities in the knowledge graph.

Mark observations as invalidated (belief revision tracking).

Sets status='invalidated' and records invalidated_at date. Optionally records what superseded the old belief.

Delete multiple relations from the knowledge graph.

Read the entire knowledge graph — all entities and relations.

By default returns full entities with pagination (offset/limit). Use summary=True for a compact overview (names + types + observation counts).

Open specific nodes in the knowledge graph by their names.

Returns the requested entities and all relations connected to them.