Entity resolution.
The person who emailed you may also be in today's meeting. Team0 connects their context carefully, while keeping different people with the same name apart.
Recognize the person, preserve the distinction.
- Across sources
- Relevant email, meetings and work records can contribute to the same picture of a person.
- Across names
- Different spellings and names in more than one language can be connected when supported.
- When uncertain
- A similar name is a reason to investigate. An unresolved identity should remain uncertain.
Work has names too.
A feature may be called SSO in a meeting and single sign-on in a document. Team0 connects knowledge about pieces of work and their names, with human confirmation where the meaning is unclear.
A broader project and one of its features can still be different things. Connections should help an agent find context without collapsing distinctions that matter.
Mistakes need a way back.
- 01
Sources stay inspectable
You can see the information behind a record and correct what Team0 understood.
- 02
Merges can be undone
Combining two records should not make a mistaken identity permanent.
- 03
Your correction matters
A correction is retained so the same old input does not silently recreate the mistake.
- OverviewThe World Model
- ArchitectureFollow one fact from email to every agent
- Data modelSources, context and history
- Truth maintenanceChanging plans, promises and disagreements
- Trust and scopeWho said it, who may see it
- Understanding EngineCurrent context for the task at hand
- Memory vs understandingWhat a memory layer does, and what understanding adds
- Markdown vs Team0Where notes files stop, and what keeps them current
- ComparisonsHow Team0 differs from memory layers
- The 31 problemsEverything you have to solve, in one list
