Follow one fact.

It starts in the tools you already use.

Team0 syncs your sources in the background. Nothing to forward, nothing to tag. Gmail is read-only.

Every input becomes a background job.

It lands in a queue, deduplicated, so nothing is processed twice. Six queues by urgency, worked on both servers.

Every claim is checked before it becomes a fact.

Who said it, about whom, and when. One writer turns claims into facts, so two jobs never race to save different versions of the truth.

Inside every fact.

A fact is more than a sentence. It keeps where it came from, how far to trust it, and every value it ever had. Nothing is silently overwritten.

Twelve checks, on every save and every night.

A ring of truth checks keeps the understanding current. Thursday replaces Friday, and the history stays. Pick any check.

• Stale heard items expire: Unconfirmed items fade out instead of hardening into facts.
• Single values replaced: A newer value takes over. Thursday 14:00 replaces Friday 11:00.
• Update check on save: Does this replace an older fact? Asked every time something is saved.
• Plan changes: Judged right after saving, so a moved plan is never left in two places.
• Contradictions caught: When two current values clash, Team0 notices.
• Disagreements kept: Kept side by side, and your agent asks you which one holds.
• Promises kept, settled: A promise is linked to whatever closed it.
• Calendar moves settle asks: The calendar is the record. It settled Jordan’s ask.
• Corrections propagate: Fix one fact and everything built on it updates.
• Settlement fence: What is closed stays closed. Old echoes can’t reopen it.
• Relationships, 2 vendors: A second model from a different vendor confirms each relationship.
• Nightly truth check: Every night, facts are re-judged with full context.

Facts link into a picture, and it keeps itself current.

People, companies and moments link into storylines. Every night the whole picture is brought up to date, in every workspace.

Later, a different agent asks.

Codex never saw Jordan’s email or your calendar. It has never been told about the pilot review.

Codex asks Team0:

“When is the pilot review with Jordan?”

One read, shaped by the question.

Five kinds of request, one ranked read. Team0 works out what the question needs before it fetches anything, and says “no record” instead of guessing.

Every read and write passes one governed door.

Each agent sees only what you allow. Tap a step to see what it does.

1. request: Codex asks a question.
2. sign in: OAuth, or a key issued to that one agent.
3. grant: The scope you gave this agent. It decides what Codex can see.
4. limits: Deduplicated and rate limited.
5. privacy: Agent input is encrypted on intake.
6. receipt: What it asked and what it got, written down.
7. packet: Only then does the answer leave, scoped to Codex.

requestsign ingrantlimitsprivacyreceiptpacket

Grant. The scope you gave this agent. It decides what Codex can see.

Codex

readssaves

Full accessStop savingStop all access

Codex gets “Thursday 14:00, confirmed.” What it learns can be saved back.

Stop saving, or stop all access, per agent, any time.

The answer carries its proof.

Not just a time. The agent can say where it came from, and that it was confirmed, not merely asked for.

Codex asks:

“When is the pilot review with Jordan?”

Team0 answers:

“Thursday at 14:00, confirmed by your calendar. Jordan asked for it by email.”

confirmedsaid Tue 09:40Fri 11:00 in history

Every agent reads the same understanding.

And can write back to it. Each one sees only what you allow. Point at an agent to see how it connects.

What is kept, and for how long.

Raw words don’t stay. Learned facts stay, with their history; the raw words around them are erased by a daily job.