veilSense / Feature Deep Dive
Brain Wiki

One knowledge base.
Every change tracked.

Brain is where every source your team touches ends up — documents, web research, Confluence, chat answers, and manual notes — and it's the single base every assistant, generator, and workflow reads from. Every entry is labeled by origin, written to be read by people and AI alike, versioned automatically, and never becomes searchable knowledge with unreviewed sensitive data still in it.

📄 Documents
🌐 Web / Research
📋 Confluence & Notion
☁️ Cloud Storage
🤖 AI chat results
✍️ Manual notes
veilsense.company.local / wiki / gdpr-data-processing-policy
Workspace
📁 Legal
📄 GDPR Data Processing Policy
📄 DPA Template
📁 Engineering
📁 Onboarding
GDPR Data Processing Policy
Rev. 7 Confluence · edited 2 days ago
🏷️
AI vs. human, labeled
Every entry shows whether it was extracted or written by a person
🧑‍🤝‍🤖
Readable by both
A real formatted document for people, semantically indexed for AI
🕓
Tracked automatically
Every edit becomes a revision — nothing is silently overwritten
🔒
Safe from unreviewed PII
Sensitive content can require sign-off before it's searchable knowledge
Version history

Every edit is a revision. Nothing is ever lost.

Every wiki entry carries full revision history. Compare any two versions with a word-level diff, and revert non-destructively — a revert creates a new revision instead of erasing the ones after it, so the audit trail always stays intact.

  • ✓
    Full revision list, newest first, for every entry
  • ✓
    Word-level diff between any two revisions
  • ✓
    Non-destructive revert — history is never deleted
  • ✓
    Draft autosave never pollutes the revision history until you publish
Rev. 5
Rev. 7 (current)
Data must be retained for 2 years5 years and reviewed by the appointed DPO quarterly.
Rev. 7 — currentAug 16
Rev. 6Aug 2
Rev. 5Jul 21
Knowledge graph

See how your knowledge actually connects.

Link entries with typed relationships — depends on, defines, part of, references, and more — and browse the result as a visual graph. It's how a policy document, the glossary term it defines, and the team that owns it stay connected without duplicating content.

  • ✓
    14 general-purpose relationship types for linking entries, plus a starter ontology of 31 typed relations and 23 classes — including veilSense's own building blocks — all configurable per workspace
  • ✓
    Visual graph view of any entry's connections
  • ✓
    Explicit links alongside automatic semantic search
GDPR Policy
DPA Template
Legal Team
"DPO" (term)
RELATED_TO
CREATED_BY
DEFINES
Origin, always visible

AI-extracted or human-written — you can always tell.

Every entry in Brain carries a visible origin badge. A glossary term pulled from a document, a summary an assistant wrote, and a policy your compliance lead typed by hand all look different at a glance — nobody mistakes an AI extraction for a human sign-off, or the other way around.

  • ✓
    Origin badge on every entry — Document, Web, Confluence, AI chat result, or Manual note
  • ✓
    AI-extracted glossary terms and summaries stay marked as such, never blended into human text unlabeled
  • ✓
    Revision history shows who — or what — made each change
📋
GDPR Data Processing Policy
Synced from Confluence · Rev. 7
Synced
📄
ROPA — Definition
Extracted from glossary table
AI-extracted
🤖
DPA obligations — Q&A summary
Saved from a Brain Q&A chat
AI result
✍️
Data Retention — Team Decision
Written directly by Legal
Human-authored
One entry, two readers

Written to be read — by people and by your AI.

Every entry is a genuine formatted document, not a raw blob sitting behind a vector index. A person can read it end to end, edit it, or export it to Word or PDF. The exact same content is semantically embedded so every assistant can ground an answer in it. One piece of content, two readers, nothing to keep in sync.

  • ✓
    Entries render as real, formatted documents — not a wall of raw extracted text
  • ✓
    Export to Word (.docx) or PDF whenever a person needs the document itself
  • ✓
    The same content is embedded and searchable by every AI assistant
  • ✓
    No separate "AI copy" and "human copy" to keep in sync
👤
Read by your team
Formatted markdown, editable inline, exportable to Word/PDF
🤖
Read by your AI
Semantically embedded, grounding every assistant's answers
Ontology

Give your Brain a shared vocabulary.

Define the classes your organisation talks about — people, projects, systems, documents, decisions — and the typed relations between them. The AI proposes a class for every entry, a person accepts it, and search and the graph understand how things connect.

  • ✓
    Start from a ready-made template, from scratch, or by importing an ontology package
  • ✓
    AI suggests a class per entry — nothing is classified until a person accepts
  • ✓
    Links that do not fit the schema are flagged, with AI-proposed fixes you review
  • ✓
    Near-duplicate nodes ("SAP S/4", "SAP S4HANA") are found and merged
🏷️
Class: Project
AI suggests · a person accepts or rejects
🧩
Class: System
Typed relations with domain, range and inverse
Temporal facts

Know which facts are still true.

Entries carry an effective date and a lifecycle state. The AI extracts the individual statements of decisions and meeting minutes and spots when a newer fact replaces an older one. It only proposes — a person accepts or rejects each replacement, so Brain Search stops quoting outdated numbers.

  • ✓
    Effective date, archive and "last verified" stamp on every entry
  • ✓
    Fact Review queue: old statement, new statement, and the AI's reasoning
  • ✓
    Archived entries stay out of Brain Search; each result carries its date
  • ✓
    Superseded facts are shown struck through in the context the AI receives
Fact Review
Budget 2026: €75,000 as of June
Budget 2026: €90,000 as of September
Proposed: older fact supersededAccept / Reject
Ingestion that reads the content

Glossary tables and long documents are chunked differently.

A recursive splitter breaks long documents into precisely sized chunks for retrieval. But a chunk that's mostly a pipe-delimited table gets detected automatically and routed through a glossary-extraction prompt instead — so a 40-row terminology table becomes 40 searchable entries, not one blob.

  • ✓
    Recursive chunking sized for precise retrieval on long documents
  • ✓
    Table-heavy chunks auto-detected and switched to extract-every-term mode
  • ✓
    Every entry carries its origin — document, web, Confluence, or AI result
Detected: glossary table
| Term | Definition |
| DPO | Data Protection Officer |
| ROPA | Record of Processing Activities |
| ... | 37 more rows |
→ 40 individual glossary entries extracted
Write, don't just read

An AI writing assistant that knows your Brain.

Continue, rephrase, expand, fix grammar, or summarize a section without leaving the entry. Point any of those actions at a Brain-grounded prompt — set per entry or workspace-wide — instead of a blind completion, so what gets written stays specific to your actual content instead of generic filler. Draft edits autosave every couple of seconds; publish when you're happy, or discard and keep the last published version untouched.

  • ✓
    Continue / Rephrase / Expand / Fix grammar / Summarize, inline
  • ✓
    Back any action with a Brain-grounded prompt, configured per entry or workspace-wide
  • ✓
    Falls back to a plain LLM call only when no prompt is configured
  • ✓
    Draft autosave with an explicit Publish or Discard step
  • ✓
    Export any entry to Word (.docx) or PDF, images included
  • ✓
    Copy or move an entry to another workspace, with an unsaved-changes guard
🧠 Prompt: "Legal Glossary Writer" · Brain-grounded
Continue Rephrase Expand Fix grammar
Privacy controls

Some knowledge is personal. Some must never touch AI at all.

Two independent, per-entry toggles cover very different needs. Mark an entry Confidential and only you can find it — hidden from every other member's list, search, and Brain-Search answers, while it stays fully usable by your own AI assistants. Mark it AI-Excluded and it's the opposite: visible to the team if you choose, but its content is never sent to any AI model at all — no embedding, no extraction, no Brain-Search context — for anyone, including you.

  • ✓
    Confidential — hidden from other members' lists, search, and Brain-Search context; the owner keeps full AI access
  • ✓
    AI-Excluded — content never reaches embedding, extraction, AI Assist, or Brain-Search, for anyone
  • ✓
    The two combine freely — visible-but-AI-excluded, or confidential-but-AI-processable, independently
  • ✓
    Turning AI-Exclusion on retroactively purges any embeddings the entry already had
🔒
Confidential
Hidden from other members — owner keeps full AI access
🛡️
AI-Excluded
Never embedded, extracted, or sent to any AI model — for anyone
🔒 Safe by default

Sensitive data doesn't become searchable knowledge without a sign-off.

Content that touches PII can be gated behind review before it's writable, publishable knowledge — configurable per source and workspace. A Confluence import or document upload that turns up personal data sits in Pending Review until a person clears it, working alongside veilSense's anonymization pipeline that keeps sensitive data out of every LLM call in the first place.

  • ✓
    PII review gate on incoming content — Confluence syncs, document uploads, and source monitoring
  • ✓
    A "Pending review" filter shows exactly what's waiting on a human decision
  • ✓
    Every entry carries an explicit review status, end to end
  • ✓
    Works together with veilSense's anonymization modes — PII is masked before it ever reaches an LLM, reviewed or not
✓
Not required
👤
Pending review
3
Reviewed
DPA Template — synced from Confluence, contains 2 detected personal-data entities.
Status: Pending Review — held for a human decision before the change is treated as cleared knowledge.
How it works

From scattered sources to one Brain.

1

Everything lands in Brain, clearly labeled

Documents, Confluence, web research, chat answers, and manual notes — indexed automatically, each carrying a visible origin badge and, when required, a PII review gate.

2

Search and write — for people and AI

Semantic search finds the right entry by meaning. Every entry is a real document a person can read and edit, and the same content grounds every assistant's answers.

3

Track every change, automatically

Full revision history, diffing, and non-destructive revert — with export whenever you need the document itself.

Your knowledge, actually organized.

One Brain, every source, clearly labeled and fully versioned — safe from unreviewed sensitive data, readable by your team and your AI alike.