About Services Tools Blog Contact us

Company Knowledge Base

A private store of company facts that an assistant can ask questions of, with trust levels, limits on what it may change and a record of every change.

  • Knowledge Base & SOPs
  • Cross-sector
  • Tool
  • Product
  • Local/private
  • 2026

The problem

Facts about the business, its jobs and its decisions sat in folders and chat, so every new session began with the same explanation. A document search finds a similar paragraph but misses how two facts relate, or which one is a credential and which is only a guess. File notes also cannot say what changed or when.

What it does

Each fact is stored as an item, with links to related items, an area, a trust level and a note of where it came from. An assistant asks a question in plain language and gets the related facts back, or Unknown if that area is empty. Changes are planned against what is already stored and then applied, with a record a person can correct.

Outcomes

  • A later session starts from the stored facts instead of a blank explanation.
  • An empty area returns Unknown instead of a guessed paragraph.
  • Every change keeps a before and after record.
  • Operators can see what the assistant holds without opening the database.

Simplified mockup

Interactive preview with sample data. Nothing is sent to a server.

Node tree

3 scopes
Nodes
0
Links
0
Open sessions
0
Vault
credential durable Supplier portal passphrase is held by the accounts lead
vault/supplier-portal
credential durable Card machine admin code stays in the vault, not in chat
vault/card-machine
People
confirmed durable Amira Cole is the accounts lead
people/amira-cole
inferred session Saturday cover is Jonah Reed
people/saturday-cover
Work
confirmed durable Dispatch cutoff is 15:00 on weekdays
work/dispatch-cutoff
confirmed durable Returns window is 30 days from delivery
work/returns-window
Links
FromLinkTo
Amira ColeholdsSupplier portal
Amira ColeownsDispatch cutoff
Dispatch cutoffsame scopeReturns window
Saturday coverinferred fromLast week’s rota

Scoped question

neighbourhood
Nodes in view
confirmed Amira Cole is the accounts lead
people/amira-cole
confirmed Dispatch cutoff is 15:00 on weekdays
work/dispatch-cutoff
confirmed Returns window is 30 days from delivery
work/returns-window
inferred Saturday cover is Jonah Reed
people/saturday-cover
Work scope facts stored
When does dispatch close, and who owns it?
Archive scope empty
Who covered Saturday in the closed archive?

No nodes are stored here. The answer must not be guessed.

Ingest a note

Scoped note work

Saturday cover has moved to Freya Moss. Reinforce the weekday dispatch cutoff of 15:00. The returns window may now be 14 days, and that is not confirmed.

Floor desk · today 11:40

Already stored
PathValueTrust
dispatch-cutoff15:00 weekdaysconfirmed
returns-window30 daysconfirmed
saturday-coverJonah Reedinferred

Maintenance tick

Sessions

Expire agent sessions that have gone quiet, so a later ask starts clean.

Due jobs

Fire anything waiting, including a held ingest that was confirmed.

Embeddings

Re-embed nodes whose text changed since the last tick.

Last scheduled tick 06:00
CheckResult
Sessions expired0
Jobs fired0
Nodes re-embedded1

How it works

  1. Store each fact as an item with a path, area, trust level and lifespan.
  2. Index the links between facts as well as the facts, so search can match the meaning of a link.
  3. Accept a note as a job, propose new, stronger or weaker facts, and check the plan before applying it.
  4. Answer a question within its area from the related facts, and return Unknown when nothing is stored.
  5. Run a regular check that expires old sessions, runs due jobs and refreshes facts whose text has changed.
  6. Show the tree, the trust badges and the change record in a console, with a run-now maintenance summary.

Pipeline

flowchart LR
  Note["Scoped note"] --> Plan["Propose plan"]
  Plan --> Check["Validate"]
  Check --> Graph["Node tree"]
  Graph --> Ask["Scoped question"]
  Ask --> Answer["Answer or Unknown"]
  Graph --> Tick["Maintenance tick"]
  Tick --> Audit["Audit log"]