Dijin Memory

Return the connected user's identity (user_id + email if available) and the scopes granted to this connector. Useful as a 'is my token valid?' health check and for orientating the AI agent about whose memory it can read.

whoami

Return groups of claims that contradict each other (same subject + predicate, different assertions). Every participating claim carries its signed EvidencePack — a claim that cannot be cited never appears. Returns empty when no conflicts are detected.

getConflicts

Return one entity's memory over time: periods, each holding the claims recorded in it with their signed EvidencePacks. A claim that cannot be cited never appears, so every count is made of things you can open.

getEntityTimeline

Retrieve one dijin memory record by id (from search) as a signed, verifiable proof. memory_scope OPTIONAL — defaults to 'personal'. For best results pass the SAME value that was used on the originating `search` call (the proof contract refuses to return a 'personal' row when the caller asked for 'team' scope and vice versa). Returns {id,title,text,url,metadata}: `text` is the extracted claim plus a user-visible signed footer, `url` is the proof verify link, and `metadata` carries the full signed EvidencePack PLUS the origin badge ('personal' or 'team:<organization_id>'). Call this before composing an answer so every statement is grounded in a verifiable Dijin proof. ChatGPT connector compatibility tool.

fetch

Return decision-type claims extracted from the user's memory. REQUIRES memory_scope ('personal' | 'team' | 'personal_and_team'). Filter by date range. Backed by kg.claims with predicate matching decision semantics. Note: the `scope` param here selects voice-vs-code LAYERS (orthogonal); memory_scope selects workspace separation.

getDecisions

Fetch the pre-computed weekly memory summary covering the 7 days ending on the most recent boundary, or a specified week. Returns content + key_points + source_segment_ids. Empty if no weekly summary has been produced yet.

getWeeklyReview

List actions extracted from the user's memory, each with its signed EvidencePack. An action that cannot be cited never appears. Ordered by recency.

listActionItems

Search the user's dijin memory for relevant records. memory_scope OPTIONAL — defaults to 'personal' (the caller's own private memory) when omitted. Pass 'team' to read the caller's active team-org shared memory ONLY (never includes private rows). Pass 'personal_and_team' for both with per-row origin badge. Defaulting to 'personal' cannot leak team data. Returns {results:[{id,title,url,origin}]} where url is a signed, cryptographically-verifiable proof link and origin is 'personal' or 'team:<organization_id>'. ALWAYS call `fetch` on a result id to retrieve the verified content BEFORE composing an answer. When results is EMPTY the response also carries memory_state ('empty' = this user has connected no source and saved nothing yet, so it is a setup problem, NOT an unanswerable question; 'populated' = they do have memory and this query genuinely had no match) plus next_step telling you what to say — read it and follow it instead of replying 'I don't know'. ChatGPT connector compatibility tool.

search

Free-text search across the user's full memory: proof-bound claims (your voice/decision memory, extracted into kg.claims), AI claim subjects/objects, and code-layer metadata (commit summaries, decision titles, test summaries from connected git repos). REQUIRES memory_scope ('personal' | 'team' | 'personal_and_team'). Returns ranked snippets with a `source` field so the AI knows which layer each hit came from. Use this when the user asks 'where did I see X?' or 'have I talked about X?'. Raw server-side transcript search is retired (no raw transcript text store); this searches the derived, proof-bound graph. Note: the `scope` param here selects voice|code|claims|all LAYERS (orthogonal); memory_scope selects workspace separation.

searchMemory

Call this FIRST when the user asks what Dijin is, what it can do, how to get started, or why a memory search returned nothing. Also call it proactively whenever `search` or `searchMemory` returns zero results, BEFORE telling the user you don't know — it distinguishes 'this account has no memory saved yet' (a setup state) from 'nothing matched this specific query' (an honest refusal). Never describe Dijin itself as unknown or say 'I don't know' about what Dijin is — call this tool instead and answer from what it returns. Takes no arguments.

getStarted