Open loops
Everything raised and never closed
Ranked by consequence, not by age — a live blocker outranks an ancient nit.
TEMPORAL KNOWLEDGE GRAPH · MULTIPLAYER · LOCAL-FIRST
Your notes remember what. Limitless remembers when you believed it — and shows you the moment the story changed.
THE PREMISE
The deadline moved to September. That happened on a date, in the world, whether or not anyone wrote it down.
You learned it eleven days later, in a Thursday standup. That is a different date, and the gap between them is the interesting part.
Real output. The offset between the rows is your reporting lag — the thing no single-clock tool can even represent.
WHAT IT CATCHES
Nobody lied. Each revision was reasonable on the day it was made. But no document anywhere holds all three — so nobody saw the shape until now.
+184 days of slippage, assembled from three different meetings across six months.
THE SURFACE
Built for a non-linear thinker: it opens with what needs you, not with a blank search box. Everything below is real, unedited output.
CONNECTED TODAY
BUILDING NEXT
Sources stay where they are. Limitless reads them, dates every claim twice, and links them — it never becomes another place your work lives.
Open loops
Ranked by consequence, not by age — a live blocker outranks an ancient nit.
Obsidian vault
Every entity a page, every relation a link. The graph view is the graph.
Claude Desktop
Twenty MCP tools. “Catch me up.” “How did this change?” “What did I drop?”
SEPARATE WORLDS, ONE BRAIN
Spaces live on relationships, not on things. So an unrelated venture stays sealed off — while a person or vendor who quietly appears in two of them lights up as a bridge.
robotics
30 relationships
bridge
Sam Rivera
in both, mentioned in neither brief
philanthropy
8 relationships
MULTIPLAYER
Bridge one narrow seam of your graph to a partner's. They see the shape of what is true — never the sentence someone said in the room.
See the exact edges that would leave, and every one withheld, with a reason.
A code buys a request. It grants no access at all — a leaked code is not a breach.
You compare their fingerprint out of band, then wrap the key to them personally.
Rotates the key. They are cut off even if they kept the old one and bypass the relay.
Crosses the boundary
Withheld, with reasons
BUILT ON CONTRL
A partner acting on your fact needs to know it is actually sourced.
Limitless translates each share policy into CRL
— the CONTRL Rule Language — and the released crlc decides.
Limitless supplies the evidence; it does not grade its own homework.
On a real graph, of 14 facts a plain allow/deny would have shipped, CRL authorises 1. Ten were single-source. Three had gone stale. Fail closed: evidence whose freshness cannot be proven never satisfies a rule.
Rules compile to a deterministic sha256: bundle hash, so a
sharing decision can be pinned and re-verified years later. Decision
records land on the hosted CONTRL platform — the shared, verifiable
history across every party — as it ships.
The relay stores ciphertext and public keys. We pulled a live bundle straight out of storage: 256/256 distinct byte values, longest readable run 6 characters. It cannot read what it routes.
ACROSS EVERY GRAPH
Once two graphs are bridged, the interesting question stops being what each of you knows and becomes where you diverge. Limitless answers it continuously, without anyone running a report.
What you, your co-founder and your team each independently assert is locked. What only one of you believes is what the next meeting is for. Alignment stops being a feeling and becomes a query you can run.
You start reasoning toward Y. A partner already committed to X. Nobody asks for a report — the contradiction arrives by embedding distance, while it is still cheap to resolve.
Check a claim against a partner's private knowledge without ever seeing it. You learn whether you contradict them. You learn nothing else — the knowledge stays encrypted and still does its job.
A fact buried a thousand messages deep is recalled the moment it matters, and once you use it the graph marks it learned. What you have absorbed is tracked separately from what you were merely told.
THE POINT
In private build — not open yet
Local-first. Your graph is a SQLite file and a folder of Markdown. No account, no cloud, nothing leaves unless you say so.