Capture what your senior experts
know before they retire.
Works with the systems your team already runs
How it works
Capture → Validate → Deliver.
Capture and Validate
Capture the decisions your manuals never recorded.
The expert speaks. Dedendum probes, structures, and verifies.
In a 20-minute voice session, your senior expert shares what they actually do -- not what the manual says. Dedendum asks targeted follow-up questions, structures the knowledge, and gets the expert to verify every item before it reaches the frontline.
No keyboard. No forms. No unverified AI output.
Waiting to begin...
Listening for knowledge items...
03 · Deliver
Knowledge at the point of work.
A new engineer on Line 3 asks a question. In under 30 seconds they get a grounded, step-by-step answer that names the expert whose judgment is behind it.
Trust architecture, not a search bar.
30 sec
to answer
1 hand
operation
100%
attributed
Aarav J.
Line 3 · 6 months | Shift A · 14:08
Compressor · HP-112
Centrifugal · 450 HP · Zone 3
The low thermal reading is likely caused by a faulty RTD sensor connection at junction box J-14, not an actual temperature drop. Terry M. confirmed this pattern during humid-day startups.
Step-by-step
Verify the thermal gauge sensor wiring at junction box J-14.
If wiring is intact, check coolant flow rate at the inboard housing.
Compare against baseline in the HP-112 commissioning video (timestamp 4:22).
If reading persists below threshold, replace the RTD sensor per datasheet spec.
High · Grounded in 2 experts, 1 SOP, 1 datasheet, 1 video…
Terry M.
Senior Mechanic
Session log #142
Apr 18 capture
SOP-112-C Rev 3
PDF document
DS-RTD-440
Datasheet
Document says
“Replace RTD sensor when reading deviates >5% from baseline for 24 hrs.”
Expert says
“On humid days, the RTD gives false lows for the first 20 min. Don't replace - wait and re-check.”
Knowledge graph
Reads from your existing systems. No migration.
Voice and video flow in. SOPs, emails, photos, and the document stack you already run are read in place. Every answer cites its source.
Admin Dashboard
Where the ops director sees the system working.
Three read-only views for plant managers, ops directors, and GM/COO.
Query log
Timestamp, question, expert attributed, confidence, flag status.
Knowledge base
Every validated item, expert name, validation date.
Flag queue
"This didn't help" items with context, ready for expert review.
Everything is read-only. The dashboard reports the system. It doesn't let an ops director edit the expert's judgment.
12 of Terry's knowledge items are live. Your team asked Floor Assistant 34 questions this week that used to go to Terry.
Trust architecture
Why this isn't just another AI chatbot.
Every Dedendum answer carries four things generic AI does not:
Named attribution
The expert whose judgment the answer reflects is named on every answer card.
Human validation
No AI output reaches the floor unless the named expert has reviewed and approved it.
Source citation
Every answer traces back to a validated source with a date.
Confidence tier
High, Medium, or Review. The system never pretends to know more than it knows.
“No output reaches the floor unverified by design.”
What it's built on
The stack, named and specific.
- •OpenAI Whisper — Voice transcription
- •OpenAI GPT-4o — Structured extraction from expert conversations
- •OpenAI GPT-4o-mini — Grounded answer synthesis for Floor Assistant
- •PostgreSQL + pgvector — Knowledge store and semantic retrieval
- •React + Node.js — Browser-based, no app install required
- •Data residency: Canada — PIPEDA-compliant from day one
- •SOC 2 — Certification path begins H2 2026
Réponses directes, sans fard.
Si quelque chose n'est pas livré, on le dit.
Dedendum connecte vos sources documentaires existantes avec des entrevues guidées par IA et livre des réponses sourcées aux travailleurs de première ligne. Il capte le jugement que les manuels manquent : le raisonnement, les cas particuliers, l'expérience de terrain, et le rend disponible à travers une couche de connaissances validée.
SharePoint stocke des documents. Les wikis dépendent de quelqu'un qui les écrit. Dedendum se connecte à ces sources et capte aussi le savoir tacite expert par des entrevues guidées. Les réponses retournées incluent des citations, l'attribution experte et le statut de validation, pas juste une liste de fichiers.
Vingt minutes. Sans clavier, sans préparation de documents. Un opérateur guide la session ; l'expert parle. Dedendum structure chaque réponse en item de savoir validé. Rien ne devient actif sans l'approbation de l'expert.
Non. Dedendum s'y connecte. Vos SOP, manuels et fichiers de formation restent où ils sont. Dedendum les indexe aux côtés du savoir expert capté et retourne des réponses sourcées des deux.
Toutes les données locataires sont stockées à Canada Centre (Azure). Conformité LPRPDE au jour 1. La piste de certification SOC 2 débute au S2 2026. Architecture base-par-locataire : chaque organisation a sa propre base de données.
Dedendum n'invente pas de réponses. Si rien de validé ne correspond à une question, il le dit. Chaque réponse inclut ses sources et l'expert qui l'a validée. Les gestionnaires peuvent réviser et approuver le savoir avant qu'il n'atteigne le plancher.
Architecture prête à l'intégration pour SharePoint, Google Drive, OneDrive et l'ingestion de fichiers locaux. La couche IA utilise les API OpenAI et Claude. Conçu pour le déploiement Azure en entreprise.
Demandez une démo ou planifiez un audit de risque du savoir. On commence avec une équipe, un processus ou une machine critique et on vous montre quel savoir est à risque dans votre opération.
Start with the audit, not the contract.
The first conversation is always the Knowledge Risk Audit. No slides. No pitch until you ask for one. Your named experts, your incident history, your numbers — and you get a one-page risk picture before any contract is on the table.
Built in Vancouver, BC · Canadian data residency · PIPEDA-compliant








