Cited to the clause
Every claim points to the part of the instrument it rests on, not to a whole document.
Home / Curator · In design — not available today
Deep research you can defend.
Curator is the research interface we are building over BanyanGraph: an answer cited to the clause and correct for the date, what it implies for your work, and a plain statement of what the evidence could not support.
01 / 08
A question with a date in it
Research in regulated work is rarely “what does the rule say”; it is “what applied, on that date, to us”. Curator starts from the question as it is actually asked — here, which KYC instruction governed periodic updation on 12 December 2015.
02 / 08
The evidence
Candidate clauses come from BanyanGraph, the connected law underneath. Curator follows the links between instruments — what amends, replaces and cites what — rather than trusting text that merely looks similar.
03 / 08
The clauses that matter
The few clauses that matter line up, each with its standing on the date asked: in force then, issued later, or guidance rather than an instruction. A later document does not quietly answer an earlier question.
04 / 08
Your own context
Curator is designed to let your own documents — a policy, a board note — add context to the answer, contributing one way and staying yours. It is not built yet In development
05 / 08
The cited answer
The answer is given as of the date asked, and every claim carries a thread back to the clause it rests on, so a reviewer can check the basis rather than trust the sentence.
06 / 08
What the evidence could not support
Where the sources searched do not settle a point, Curator says so and marks it. Declining to answer is a receipt of what was searched, not an error — the knowledge layer beneath already behaves this way.
07 / 08
What it implies
A finding matters because of what it touches: a policy, a procedure, product documentation, a risk, a control. Curator points to them; ChangeProof traces the change through each one and proves what was done.
08 / 08
Review
For regulated teams, a finding moves through review before it counts: a maker, a checker, a committee. The workflow exists in code; Curator as a whole is not yet available In development
What makes an answer defensible.
Built into the knowledge layer Curator uses, and kept visible in the answer.
Correct for the date
Answers are given as of the date asked, using what was in force then and marking what came later.
Honest about gaps
When the sources do not settle a point, the answer says what was searched and what is missing.
Evidence weighed
Evidence is marked as supporting, contradicting or extrapolating, so “cuts against it” is never read as “weakly supports it”.
Effort disclosed
The answer states the level of compute that was asked for and the level that actually ran.
A path to action
Findings lead to the work they affect, and to review before anything counts as approved.
Two ways to work.
For professionals
A research workspace
Ask, read the cited answer and its sources, follow what changed and when, save your research and take it with you.
In design In development
For regulated teams
Change, review and record
What changed that matters to your organisation, routed to the right reviewer, approved by maker, checker and committee, and kept on the record.
Approval workflow in code; change feed and audit In development
An answer that shows what it cannot support.
Illustrative: the parts of a Curator answer. Each part exists in the research stack behind Curator; the interface is in design.
- Statement 1
- Cited to the clause, in force on the date askedAttributable
- Statement 2
- Cited to a circular replaced before that dateContradictory — evidence against the statement, not weak support for it
- Statement 3
- Goes beyond what its sources sayExtrapolatory — shown as unsupported
- Execution
- The level of compute asked for, the level that ran, and why they differ
- Coverage
- What was searched, the corpus watermark and the known gaps
What you can engage us for today
- Technical briefings, and conversations with prospective design partners.
In development
- The Curator research workspace.
- Your own documents as private context.
- A change feed, review and audit record for regulated teams.
- Stated, verified controls for tenant separation, retention and training.
Talk to us about Curator.
Tell us the questions your team has to answer and the dates they turn on. We will show you how Curator is being built to answer them, and be clear about what exists today.