dpaperwork
All guides

Knowledge

Knowledge (previously "Company Brain") is the persistent memory dpaperwork builds for your Workspace. It's what makes dpaperwork feel like a colleague who actually knows your business — not a generic AI you have to brief from scratch every session.

Before every Chat response, Playbook run, and Document draft, dpaperwork queries the Company Knowledge and surfaces the most relevant context for that moment.

You read and manage all of it in the Knowledge section — one page with four tabs: Overview, Pages, Activity, and Decisions.

Three layers

Layer 1 — Company Context

The baseline briefing: what your company does, how you work, who your team is, your communication style, and your current state. Always injected in full into every system prompt — it's never retrieved, it's always present.

You set this during onboarding and update it anytime from Settings → General, or by telling dpaperwork in Chat. The richer it is, the more accurate and on-brand every output will be. The Knowledge Overview shows it read-only for quick reference.

Layer 2 — Activity Log

An automatically maintained record of high-signal events. Written by the system whenever:

  • A Deal closes (won or lost, including the loss reason)
  • A Project or Cycle is created or closed
  • A Document is sent to a client
  • A Playbook runs (completed or stalled)
  • A Monitor escalation fires

The Activity Log is stored as vector embeddings and retrieved by semantic search — only the entries most relevant to your current query are surfaced. If there are multiple entries for the same record (e.g. multiple deal updates), only the most recent is returned — stale signals don't crowd out new ones.

You can also add manual entries via Chat:

"Log this: we lost Acme Corp because we couldn't hit their timeline, not price"

Or from Knowledge → Activity.

Layer 3 — Decisions

Explicit strategic calls you've made — direction changes, priorities, commitments. These are things that aren't in any Record but shape how dpaperwork should interpret everything else.

Examples:

  • "We're going retainer-only from next month"
  • "Targeting healthcare clients this quarter"
  • "No proposals under £5k"
  • "Always CC the client's CEO on delivery reports"

How decisions get saved:

  1. Chat detection — when you make a directive statement in Chat, dpaperwork recognises it and asks: "Want me to save that as a decision?" Confirm and it's saved.
  2. Direct — log a decision from Knowledge → Decisions without going through Chat.
  3. Chat command — say "save as a decision:" followed by the decision.

You can also log a decision on a record's Timeline — a decision with an optional owner and due date posted right where the context lives. Decisions that come with a follow-up task create one on the spot.

When a new decision covers the same topic as a previous one, the old entry is superseded and excluded from future recall — the brain stays current, not contradictory.

Pages

Beyond the three automatic layers, dpaperwork maintains a growing set of Pages — durable definitions it builds about your business as it learns: what a term means, how you name things, standard operating details. If dpaperwork needs a definition it doesn't have, it proposes the page in Chat for your approval. You can browse, search, create, and edit Pages in Knowledge → Pages.

Pending review

Some knowledge is drafted by the agent (summaries, page proposals) and held for your sign-off before it's used. The Overview shows a Pending Review section where you can approve (optionally with edits) or reject each item — nothing the agent writes into memory is used without your say-so.

What gets recalled and when

The brain is queried with every interaction. What gets surfaced depends on the question:

  • Asking about a specific company → relevant Activity Log entries for that company
  • Asking about your pipeline → recent deal close events
  • Any response → all active Decisions are always checked

You can also query the knowledge directly in Chat:

  • "What did we decide about pricing?"
  • "What's the history with Nova Corp?"
  • "What happened last quarter?"

Managing your knowledge

From the Knowledge section:

  • Overview — read your Company Context and approve or reject pending items
  • Pages — browse and manage the definitions dpaperwork maintains
  • Activity — review what's been auto-logged and add manual entries
  • Decisions — view, add, and delete decisions

Company Context itself is edited in Settings → General — it's a structured profile, not a log.

Try it in a walkthrough

Walkthroughs follow one job end to end, in real Chat exchanges: