Demand-driven knowledgeHow it works →

A company brain that keeps learning after you stop writing.

Agents spot what's missing, get answers from the people who know, and keep your knowledge current.

Join the waitlistSee how it works
Knowledge gapssorted by demand
  • How do I get read access to the billing replica?interviewing
  • What's the retry policy for the payments webhook?In review
  • Why do prod deploys need manual approval?resolved
  • Which feature flags are safe to delete?open
  • Who owns the legacy search indexer?open
Works where your docs already live
  • Slack
  • GitHub
  • Markdown / MDX
  • Confluencesoon
  • Notionsoon
  • Microsoft Teamssoon
  • MCP / llms.txtsoon

Your docs aren't outdated. The knowledge was never written down.

The most valuable knowledge in a company lives in a handful of heads. It surfaces only when someone interrupts them.

×5

The same question, again

A senior engineer answers it in Slack. The answer scrolls away. Next month someone new asks it again.

0

Pages that cover it

Not outdated docs — missing ones. Nobody knew this knowledge was missing until someone got blocked.

1

Person who knows why

When they go on holiday, or leave, the reason leaves with them. Every interruption is interest on knowledge debt.

How it works

From a repeated question to permanent knowledge

  1. 01

    Someone asks

    In Slack or the web chat, instead of interrupting an expert. Answered from your docs when they cover it.

  2. 02

    It doesn't guess

    Low confidence means no hallucinated answer. A knowledge gap is logged: the question, the topic, who asked.

  3. 03

    Demand is counted

    Paraphrases merge into one gap. Asked once, it waits. Asked by many different people, it becomes a priority.

  4. 04

    The right expert, briefly

    A short interview with the person who owns the topic. A few targeted questions, not “please write docs”.

  5. 05

    A draft, not a chore

    The answers become a doc draft, opened as a pull request. Experts review knowledge instead of writing it.

  6. 06

    Never asked twice

    Merging resolves the gap and re-indexes the docs. Next time, the answer is already there.

Interview · Slack DMGap #142 · 4 askers
Four engineers asked why production deploys need a manual approval this month. Why does the approval exist — and who can give it?
KM
It came out of the 2024 payments audit. Anything touching billing needs a second approver from platform. Hotfixes too — use break-glass, it pages on-call.
Thanks. One more: does it apply to non-billing services?
docs/operations/deploy-approval.mdx Merged #318
+## Why production deploys need approval
+Introduced after the 2024 payments audit:
+any deploy touching billing needs a second
+approver from the platform team.
+
+### Hotfixes
+Use the break-glass flow; it pages on-call.
Gap #142 resolved · docs re-indexed · reviewed by @kasia

Why different

Not a retrieval problem. A creation problem.

What it doesWhat it misses
Enterprise searchFinds knowledge that already exists.Blind to what was never written down.
Docs-sync botsKeep documentation in step with code changes.Only update what someone already documented.
LacunaCreates knowledge that should exist but doesn't.Prioritised by real demand, captured from the person who knows.

No migration. Lacuna works where your docs already live and publishes back there — a pull request today, a Confluence or Notion draft next.

Stop paying interest on knowledge debt

Lacuna is in early development with a small group of engineering teams. Design partners get hands-on setup with Slack and their docs repo, a direct line to the founder, and free access.

Role (optional)

No newsletter. Your email is never shared.