Atlas launch 18 May
Memory
Sources, facts, and revisions.
Memory and context for AI agents
Give your agents context they can explain.
The central nervous system for your organisation
Examples · illustration
One memory across every team.
Pollen links what each team knows. It reacts to changes, answers questions, and finds what did not happen.
Supplier change · Launch risk
01Remember & ask
02Connect
03Understand
Earlier history 0 / 4 linked
Sources become shared memory
Incoming question
Can we still launch Atlas on 18 May?
A question enters shared memory
One question.
Connected knowledge.
LATTICEShared memory · Connected context
Connected memory
Relevant context
Boards arrive 14 May
Assembly needs 5 days
Answer · Sources linked
Atlas can be ready on 19 May. The launch needs to move by one day.
01 Launch plan02 Supplier03 Assembly
A question enters shared memory.
How it works
Four steps from source to review.
A plan changes in a call. A contract keeps the old date. Pollen connects all three.
- 01
Add sources.
Send messages, emails, and documents as text. Pollen keeps each revision.
- 02
Connect facts.
Pollen links people, projects, and dates. A changed fact is closed, not overwritten.
- 03
Answer with evidence.
Each answer quotes its sources. If the sources do not support an answer, Pollen says so.
- 04
Review changes.
Pollen checks new information against what it affects. Findings go to the owner.
Monitoring
See what changed. Send it to the right person.
New information starts the work. No one has to ask a question first.
Scheduled checks find what did not happen.
Pollen reads due dates in your sources. After a due date, it checks for a confirmation. If none is on record, it records a finding.
You choose the response.
Pollen can notify the owner or ask for an urgent review. It delivers to an inbox or to your webhook.
Foundation
Built on Lattice, our own graph database.
Lattice keeps each fact with its source and its dates. Pollen uses it to connect, search, and remember.
Text fromMessagesEmailsDocuments
Pollen Context
ProductAnswers
Each answer quotes its sources.
Monitoring
Findings go to the owner.
Lattice
Graph databaseConnected graphs
People, projects, decisions, and dates.
Search
Graph links, keywords, and vectors.
History
Event time and record time for each fact.
- Separate graphs
- One service holds many graphs. Each graph has its own log and snapshots.
- Storage tiers
- Idle graphs move to lower storage tiers. They load again on the next request.
- Durable writes
- Lattice writes each change to disk before it confirms the write.
- Recovery
- After a restart, each graph returns to its last confirmed state.
Build agents with a clearer view of your business.
Tell us what your agents do. We will show you Pollen Context.