Retrieval finds passages. A second brain knows how things connect — which statute
imposes an obligation, what penalty attaches to it, who enforces it, which instrument amends it.
Those chains run across documents, so they appear in no single passage and no search result can
return them. This page queries that graph live.
Corpus: Malaysian data protection and cyber security legislation — English and Bahasa
Malaysia.
Explore
Ask about anything in the corpus. The graph returns the entities your question
names, everything connected to them within two hops, and the source of every fact.
Graph
Facts — with source
Ask a question, or pick an example above.
“Where does this obligation actually come from?”
A regulator asks your DPO why breach notification runs to 72 hours when the
Cyber Security Act says six. Answering means showing how two Acts, a subsidiary regulation and
an internal policy relate to one another — and no single page in any of those documents
states the relationship. Normally you need the one person who has read all four.
The questionHow is our internal security policy connected to the Personal Data Protection Act?
Why search failsThe answer is a chain across four documents. No passage contains it, so there is
nothing for a search to return.
What you getThe chain itself, each step naming the document it came from — an answer you can
take to the regulator.
Pick a worked example, or name any two things from the
corpus.
Choose a worked example above to see how it reads.
How it stays correct
Every edge carries the document, section and chunk it came from, so any claim here can be walked
back to the passage that supports it. The graph is rebuilt from the corpus whenever a document is
ingested or changed — a fingerprint per document decides what needs re-reading, so an
unchanged corpus costs nothing. Facts from a superseded document are deleted before the
replacement is read: in compliance, confidently citing a repealed provision is worse than saying
nothing at all.