Your people and your agents, working from the same memory.
Everything your organization learns lands in one bank, including the conversations nobody writes down. People and agents read it live, under the same permissions.
What did we promise Nordkap about the migration deadline?
You committed to a staged cutover finishing 30 September, with a read-only window on the 27th1. Lars flagged the Q3 freeze as a risk and the team agreed to look at it again in September2. Both dates are in the plan you sent them3.
- 1Nordkap sync12 Jun · 14:02
- 2Nordkap sync12 Jun · 31:47
- 3Migration planp. 3
Three sources. Open any one of them and hear the sentence it came from.
Agents are about to do the day-to-day. They'll need to know what's going on.
Most of what a company does every day is about to be done by software you can hand work to. The bottleneck stops being capability and becomes context: an agent that doesn't know what you decided last week will do the wrong thing, confidently and at speed.
Agents take the work
Drafting, chasing, reconciling, answering. The repetitive middle of most jobs, done by something that never forgets to follow up and never has a Friday afternoon.
- Draft
- Follow up
- Reconcile
People keep the direction
Deciding what matters, judging what's good enough, and stepping in where the answer needs a person. That doesn't shrink as agents take on more. It becomes most of the job.
- Oversee
- Instruct
- Taste
The most valuable input is the one nobody captures.
Chat, email and documents are already machine-readable. The conversation where the decision actually got made, in a room or on the way out of one, is not. That's where the reasoning lives, and it's the part that never reaches the systems your agents read.
Skientia is the glue.
Every conversation, document and decisionone shared memorypeople and agents who know what's going on
The knowledge already exists. Finding it is the problem.
Everything your team needs was said, written or decided somewhere. It just isn't anywhere you can look it up.
- It stays in whichever tool it happened in, so you have to remember where before you can search for what.
- Notes keep the conclusion and lose the reasoning, so the same argument gets had twice.
- Anyone who wasn't in the room depends on someone who was, and on them remembering it correctly.
Scrolled past three weeks ago
Forwarded to four people
Two files, both called final
On holiday until the 8th
It doesn't just store what happened. It works out what it means.
Meetings, people, companies, documents and decisions go in and get connected to each other. What comes out is not a bigger archive. It's an organization that remembers why, not just what.
- Meetings
- People
- Documents
- Companies
- Decisions
- Tasks
- Contexts
- Presentations
Four things build up, and the last one is why you keep it running.
An archive is worth the same on day 400 as on day 4. This isn't. Each layer is built from the one below it, so the longer it runs the more it can answer.
Facts
What was actually said and written, kept verbatim with the moment it came from.
For example
“Read-only from the 27th.” Lars, Nordkap sync, 14:02
Relationships
Who said it, who they said it to, which account it belongs to, what it changed.
For example
Lars → Nordkap → migration plan → the cutover date
Conclusions
What follows from the facts, kept separate from them, so you can always see which you're reading.
For example
The 30 September date depends on the read-only window holding
Learnings
Patterns across many meetings and months: what tends to happen, and where things tend to slip. This is the part a competitor can't copy, because it's made of your history.
For example
Cutover dates on this account have moved twice, both times after a freeze
One memory. Both sides of your workforce, in sync.
Your team and the assistants they're starting to rely on read the same knowledge and write back into it, live and under one set of permissions. No export, no second copy, no agent working from last month.
People
Browse, search and ask. What they learn goes back into the bank as they work.
- Web app
- Mobile
One shared memory
Read and written by both sides. One knowledge base, one set of permissions, one answer.
Agents
Connect an assistant over MCP or build on the API. It reads and writes what its person can.
- MCP
- HTTP API
- CLI
Live, not exported
No snapshot ageing in a vector store somewhere. Both sides read the bank as it is right now, and a change is visible to both the moment it lands.
One set of permissions
An agent sees exactly what the person it acts for can see. Access is scoped by token, and revoking one takes effect immediately.
The same citations
Answers come back with their sources attached either way, so anything an agent tells a customer can be traced to where it came from.
An agent is only as good as its briefing.
Before you hand work to software, it needs standing answers to the questions any new colleague would ask. Those answers aren't sitting in a document. They're spread across the last three months of conversations.
How is support actually going?
Three customers raised the same billing edge case this month. Two are on the enterprise plan, and one renews in six weeks.
Assembled from support calls, the account pages, and the renewal dates attached to them.
What is the team actually working on?
The migration is the priority through September. The search rework was deprioritised in the last planning call and hasn't been picked back up.
Assembled from planning meetings, the decisions in them, and the open tasks.
What's our position on this?
The board took a view on exposure in the region in April, and revisited it once in June when the supplier terms changed.
Assembled from board meetings, the decisions recorded there, and the documents attached.
What stays with the people
The more an agent does, the more the remaining human work concentrates into three things. This is built so all three get easier as agents take on more, not harder.
Oversight
Every answer an agent gives can be traced to the moment it came from, so checking its work means reading a citation rather than trusting a tone of voice.
Instruction
What people decide in a meeting becomes part of what agents read next. Correcting the direction is a conversation, not a config file.
Taste
Judging what's good, what's worth doing, and what to say no to. No amount of context produces that, and it's the part that compounds.
To be straight with you: goals, manifests and explicit rules that an agent is formally bound by are not built yet. Today an agent reads the current state of your organization and its history. Binding it to a written charter is where this goes next.
Same question. Different people. Different answers, both correct.
Pooling everything your organization knows is only safe if the pool is scoped. Permissions from the source follow the material through indexing, search, answers and agents.
Mette Bruun
On the Nordkap account
The cutover finishes 30 September, with read-only from the 27th. Margin on the renewal was raised in the internal prep call, and Lars flagged the Q3 freeze as the main risk.
- Nordkap sync
- Internal prep
- Migration plan
Support agent
Scoped to customer-facing material
The cutover finishes 30 September, with read-only from the 27th.
- Migration plan
- 2 sources withheld
The second answer isn't a redaction of the first. The material it can't see never entered the retrieval at all.
Access comes from the source
A document keeps the permissions it already had. Nothing gets more visible by being indexed.
Revoking is immediate
Remove someone's access and the next answer reflects it. No reindex, no waiting for a sync.
Agents inherit, never exceed
An agent cannot see more than the person it acts for. There is no service account with a view of everything.
The people it affects shouldn't have to think to ask.
Search only helps someone who already knows there's something to look for. When something changes, the bank works out who it lands on, and tells them.
When something changes
A decision moves
Something agreed in March is agreed differently in June.
A commitment is made
Someone promises a date, a number or a scope on a call.
Two sources disagree
What was said in the meeting doesn't match what's in the plan.
Routed by relationship, not by channel
Who owns the account, who committed to it, who works on what it touches. Worked out from the bank, and always inside their permissions.
The people it lands on hear about it
The person who owns it
Whoever holds the account or the workstream it changes.
The agents working on it
An assistant acting on stale context gets the correction as it happens.
Everyone else, on a schedule
What changed in your world this week, in one place, rather than as it happens.
Everything routed here obeys the same scoping as everything else. Nobody is told about something they could not have looked up themselves.
Browse it, search it, or just ask.
One knowledge base, three doors. Most people end up using all three in the same week.
Follow the thread
Every person, company and meeting is a page, and every page is connected to the others. You rarely arrive knowing exactly what you're looking for, and browsing is how you find out.
Mette Bruun
Head of Delivery · Nordkap
Appears in
- Nordkap migration sync12 Jun
- Nordkap A/SCompany
- Migration plan v29 Jun
- Quarterly review28 May
Capture is the beginning, not the product.
Recording a meeting is the easy part. What matters is what happens in the hour after it ends.
Capture
Record the meeting, upload the call, or connect the tools the material already lives in.
- Record
- Upload
- Calendar
- Connect
Structure
People, companies, decisions and tasks are pulled out, matched to what you already have, and linked.
- People
- Companies
- Decisions
- Tasks
Retrieve
Anyone with the right permissions gets the current answer, with the sources it rests on.
- Your team
- Your agents
Every answer shows its work.
A knowledge base you can't verify is a rumour mill. So nothing here asks to be taken on trust. Every claim carries the moment it came from, and you can open it.
Named sources, not a summary
Each claim links to the meeting or the document passage behind it, not to a paraphrase of one.
The exact moment
Down to the speaker and the timestamp. Press play and hear the sentence for yourself.
Said versus worked out
What someone actually said is kept separate from what was concluded from it. You always know which you're reading.
Read-only from the 27th1 was agreed in the sync, and the full cutover date follows from it.
Source
We'd keep it read-only from the 27th so nobody writes into the old system mid-cutover.
For the reader who wants the retrieval details.
Most people don't need this section, and the page works without it. If you're the one who has to believe the answers before your team uses them, here's how they're produced.
Connected to what you already use.
Meetings arrive through the recorder or as an upload. Everything else comes from the tools the material is already in: read-only, and only what you connect.
- Google Calendar
- Gmail
- Google Drive
- Meeting recorder
- Google Docs
- Audio & video
- Microsoft 365
Delivery surfaces
- Slack
- Jira Cloud
Share cited answers and recordings to approved Slack channels, or turn tasks into Jira issues with durable receipts and status sync. Neither destination is treated as an ingestion source.
Running something we don't connect to yet? There's an authenticated API for pushing your own systems in, and it lands in the same knowledge base as everything else.
Built for the people who have to approve it.
Everything below is shipped, not on a roadmap. Send this section to whoever signs off on new tools.
SSO
OIDC and SAML, configured per organization, with group claims mapped to roles.
SCIM provisioning
Users and groups provisioned and deprovisioned from your identity provider. Someone who leaves loses access there and here.
Roles and permissions
Who can see, who can edit, who can invite. Set per organization, enforced on every request.
Audit log
A record of who did what, exportable with a signature so it holds up outside the product.
Permission-aware retrieval
Access rules follow the material into search and answers. If you can't open the source, it can't appear in your answer.
Stays in the EU
Your data is stored and processed in the EU. Credentials for connected tools are encrypted under a key ring that can be rotated without downtime.
One system, three very different afternoons.
It gets useful the moment more than one person, or one agent, needs to know the same thing.
The manager
The same complaint came up in three support calls and never reached anyone who could act on it. It gets surfaced, with the calls attached.
"What are we missing?"
The delivery team
What the company is actually prioritising this quarter, as last stated out loud, rather than as written in a doc that stopped being true in May.
"Is this still the priority?"
The new starter
Three months of context that exists, is relevant, and lives in other people's heads. They ask the bank instead of interrupting someone, and get the source along with the answer.
"Why do we do it this way?"
Three steps, and nothing to migrate.
Start with one team and one source. It gets more useful the more it has, but it's useful from the first meeting.
- 1
Create your workspace
Sign in, name your organization, and you have somewhere for the knowledge to go.
- 2
Connect your first source
Record a meeting, upload a call you already have, or connect a calendar. Nothing moves out of the tools you use.
- 3
Invite the team
Set who can see what, and let people browse, search and ask. Connect your agents when you're ready.
No migration. No data leaves the tools it lives in unless you connect them.
The things people ask first
Your agents are only as good as what your company remembers.
Start with one conversation. See what your organization already knows.