Skip to content

Find a person in the knowledge graph

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.1 on 2026-11-14.

Who is Priya again?

The knowledge graph keeps the people your work mentions, with what you know about them. Ask by first name and get their role and company.

What you get: the person’s entry in the knowledge graph: their role, their company and anything else recorded about them.

quox · talking to Quox

Do we have Priya on file as a contact in our knowledge graph? What's her role and which company is she with?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 2ms

◐ MEMORY │ search ✔ MEMORY │ search │ 1 count, 1 results, 1 entities · 1.5s

⛓ AEE │ envelope opened · ops.tool · memory_search ok

⛓ AEE │ envelope opened · stream_success

Yes, Priya Shah is in the knowledge graph as a person.

• Role: Fleet manager
• Company: Harbourside Hire
• Contact preference: email rather than phone

She also appears in a saved decision from 12 Nov 2026. It says the Kestrel Cycles
workshop labour rate is £52 an hour from 1 December 2026, agreed with her (memory
01M788…).

The graph lists her with Harbourside Hire, not Kestrel Cycles. I can't tell from this
whether Kestrel Cycles is a separate party to that agreement or is connected to her
company. I haven't checked the address book, so I can't say whether she has a full
contact card there.

11.5s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.6.1, 14 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 14 Nov 2026 · test report mwgmpo

Quox searched memory once, and the search came back with one entity. Priya Shah is a person in the graph. She is fleet manager at Harbourside Hire and prefers email to phone. Quox also found the saved decision that names her, and said what it could not tell: whether Kestrel Cycles and her company are linked, and whether she has a full card in the address book, which it had not checked. Quox only read.

entity search
quox entity search --query PriyaID         Type      Name          Rank01M788…    person    Priya Shah    -3.3967938085302745
From the same scratch workspace (fictional Kestrel Cycles data), run after the turn above. ID shortened.

--query is required, so the search word always follows it. Add --type person to keep only people.

entity get
quox entity get <id>id                01M788…org_id            01M6F8…user_id           01M626…name              Priya Shahentity_type       personattributes  role: Fleet manager  company: Harbourside Hire  phone_pref: emailfirst_seen        2026-11-12 16:13:39last_referenced   2026-11-12 16:13:39reference_count   1deleted_at        -relations         []
Same workspace. IDs shortened.

Use the ID from the search. attributes holds what is known about her, and relations is empty, so nothing in the graph links her to another entry yet.

Quox and the terminal read the same entry. Searching and reading change nothing in the graph. The company is a text attribute, not a link, so to see what is held on Harbourside Hire itself, read its own entry.