personal AI infrastructure

A second brain
built on retrievable
knowledge.

Second Brain is a privately developed AI knowledge management system — designed to make 16+ years of professional knowledge searchable, reusable, and callable from any AI interface.

19,488+
indexed thoughts
51 stds
IFRS standards ingested
1,536d
vector dimensions
12 dom
knowledge domains

How it's built

The system pairs a vector-embedded PostgreSQL database with an MCP server, making the entire knowledge base callable as a live tool across Claude Desktop (via mcp-remote bridge), OpenAI Codex CLI, and Microsoft Copilot Studio.

Retrieval is semantic: queries are embedded at call-time and matched against stored vectors via cosine similarity — surfacing related knowledge regardless of exact phrasing.

Supabase
Postgres + pgvector + Edge Functions
OpenRouter
Embedding model routing
text-embedding-3-small
1,536-dim vector embeddings
MCP Protocol
AI-native tool interface
Claude Desktop
Primary MCP client (mcp-remote)
Microsoft Copilot Studio
MCP client — M365 integration
PowerShell pipelines
Bulk ingestion scripts

What's inside

Knowledge is organized by source layer and tagged at ingestion. Each layer has distinct retrieval characteristics — dense technical standards behave differently than conversational memory or process documentation.

16,067
IFRS Standards
all 51 standards, section-chunked
824
Business Process Library
operational process documentation
ongoing
AI Conversation History
Claude + ChatGPT exports, bulk-ingested
14
Career Lifecycle and Framework
8-level mastery, 12-domain, 120-skill map
1,824
ASPE Standards
section-by-section ASPE-to-CICA mapping
409
Not-For-Profit Org. Standards
ASNPO — section-chunked
active
Data Modelling Principles
includes Playbooks construct
active
Finance Team Capabilities
team skills + process mapping

Model-agnostic by design

The knowledge layer is decoupled from any single AI vendor. Language models are interchangeable consumers; the data, access rules, and classification live in one place and travel with the user, not the tool.

Any LLM client
swappable — config, not code
MCP
open protocol, single server
Device identity
one revocable key per device
Access profile
scopes tools and knowledge bases
Knowledge
stays in one governed store
A

Protocol, not vendor

Knowledge is exposed through the Model Context Protocol rather than a vendor plugin format. Embedding models are routed separately, so neither the client nor the embedder is hard-wired.

→ adding or replacing an LLM is a connection change, with no re-ingestion or rebuild
B

One server, many clients

A single server function serves every client, so retrieval behaviour and classification rules are identical regardless of which model asks.

→ no per-vendor forks to maintain; consistent answers across platforms
C

Least privilege per device

Each device authenticates with its own key and is bound to an access profile that limits which tools it can call and which knowledge bases it can read. Newly created knowledge is private to the owner until explicitly released.

→ a secondary or enterprise client sees only what it is cleared to see
D

Clean disconnect

Devices and knowledge bases are registered, so either can be deactivated or archived independently. Access ends immediately and shared secrets never need rotating.

→ contracts and engagements can end without touching the core knowledge base

How it was designed

Several deliberate constraints shaped this system from the start — they're not features, they're load-bearing decisions.

01

Compliance-first data design

Client data is never ingested. Source tagging is enforced at ingestion time, not as a post-hoc audit. Supabase is pinned to Canada East for data sovereignty. Row Level Security is active.

02

Environment-agnostic executability

Knowledge is structured as "Playbooks" — executable knowledge units that define context, inputs, procedure, and output independently of any specific AI interface or client.

03

Selective enrichment

Third-party content (e.g. external documents) is ingested only on manual trigger, with explicit metadata tagging. No passive crawling; no ambiguous provenance.

04

Uniform source tagging

A unified source taxonomy was applied across all ~19,000 rows via SQL migration. Retrieval can be filtered and audited by source at any granularity.

Where things stand

The system is operational and actively used as a live tool across Claude Desktop, OpenAI Codex CLI, and Microsoft Copilot Studio. Core ingestion pipelines are complete. Per-device access control is deployed, and portability is being extended across additional LLM platforms. Moving to deeper contextual classification, to capture and describe thoughts by the context it was learned in, who it concerns, where it belongs, and how sensitive it is, so ‘who may see this, and why?’ has a precise answer. This enables speed and depth of semantic retrieval, while securing decisions around access based on deeper meaning and provenance.

The architecture has undergone a formal security review covering credential management, secret rotation, data sovereignty, audit logging, and client data exclusion — with remediations documented and applied.

MCP server active  ·  Canada East region  ·  4 tools: stats, search_thoughts, browse_recent, capture_thought