- Forgets everything when the thread ends
- Your data lives in someone else's account
- Switch models and you start from zero
- You never own what you built with it
Rent the model.
Own the brain.
A portable, file-based AI workspace installed around your business. Any capable model plugs in to think — your identity, memory, tools, and work live in plain files you keep, and the brain compounds.
Most AI tools are the model.
When the chat ends, the context is gone. Switch providers and you start over. Second Brain OS inverts that — the intelligence is the only interchangeable part.
- Plain files on your machine that never reset
- Your context, memory, and tools stay yours
- Any capable model plugs in — swap freely
- It compounds, and you keep all of it
No vendor is load-bearing.
A single startup file tells any model how to wake up as your brain; thin wrappers point each runtime at it. Point a sharper model at the same folder next year and your assistant is fully present — every memory and skill intact.
It doesn't reset — and it doesn't go stale.
Two layers run underneath: durable facts injected at every session start, and daily logs built automatically from your transcripts — a searchable record of what got built, decided, and why. A weekly synthesis pass keeps it clean and ages stale facts to current reality.
The major labs now rent this "self-freshening" memory inside their runtime. Second Brain OS gives you the same shape as portable files you own and any model can read.
A workspace of plain files you own.
Any capable model can inhabit it. FCT's contribution is the framework, the setup, and the wiring — not the content. The content is yours from day one.
The persona — how the assistant wakes up as yours every session.
Who you are, your business, and how you work.
Your active plan, todos, and ideas.
Durable facts plus daily logs built automatically from your sessions.
Repeatable workflows and tool abilities it knows how to run.
How your tools were installed, authed, and wired.
Scheduled tasks that run on their own.
Links, transcripts, research, and stored output.
Layer on what your business runs on.
Optional packages on the base setup — bought upfront or added later.
Accounting
Receipt, expense, contribution, withdrawal, and subscription tracking through Google Workspace.
Coding
A projects folder, repo conventions, and build/test/release patterns for owners working across codebases.
Business Integration
Company context, products and services, and a revenue-framing plan for owners running a business with clients.
Installed with you, owned by you.
Base setup is usually done in 1 to 2 weeks. You own the AI account (~$20/month to start); day to day, you just open the folder and talk to your assistant.
- 01
Clone the template
FCT clones the Second Brain OS framework into your own workspace folder.
- 02
Onboarding interview
A guided skill interviews you to fill in identity, plan, memory, and business context — and names your assistant.
- 03
Wire your tools
We connect the stack you live in — Apple, Google Workspace, Telegram, Cloudflare, GitHub, MCP servers.
- 04
Layer add-ons
Optional packs and automations — Accounting, Coding, Business Integration — added to fit how you work.
- 05
Verify and hand off
We confirm startup context, memory writes, and at least one skill-backed tool before the brain is yours to run.
FCT runs on its own Second Brain OS.
The same architecture we install for clients is the operating layer behind FCT — research, drafts, memory, automations, and follow-through. We don't sell a system we don't run ourselves.
Second Brain OS, answered
01 What is Second Brain OS?
Second Brain OS is a portable, file-based AI workspace FCT installs around your business. Instead of being the model, your assistant is a folder of plain files on your machine — Markdown, structured data, and scripts — that holds who you are, your business context, a memory of everything you have done, and the skills and tools to act on it. A capable AI model like Claude plugs in to supply the thinking, and for that session it becomes your assistant; swap in a sharper model next year and the brain stays exactly where you left it. The workspace is organized into clear folders: identity, context, workspace, memory, skills, setup, automations, and database. Base setup usually completes in one to two weeks. The intelligence is the only interchangeable part — everything that makes the assistant yours lives in files you own and keep, not a chat thread that disappears when the session ends.
02 How is Second Brain OS different from ChatGPT or Claude?
Second Brain OS differs from ChatGPT or Claude by separating the intelligence from the brain. Most AI tools are the model: when the chat ends the context is gone, and when you switch providers you start over, renting the intelligence while owning nothing you built. Second Brain OS inverts that. A single provider-agnostic startup file tells any model — Claude, Codex, GPT, or whatever comes next — how to wake up as your assistant, with all of its memory and skills intact. No vendor is load-bearing and no account holds your data hostage. Underneath runs a memory system on two layers: durable facts injected at every session start, and daily logs built automatically from your transcripts, so the assistant reads back the whole arc instead of waking up blank. A weekly synthesis pass keeps that memory clean and current. You rent the thinking; you own the brain, as files on your own machine.
03 Do I own my data, and what does it run on?
You own every file in the workspace from day one. Second Brain OS lives as plain files on your own machine — identity, context, memory, skills, automations, and more — and FCT's contribution is the framework, the setup, and the tool wiring, not the content. Move the folder to a new machine, hand it to a different model, or read it yourself ten years from now and it all still works. It runs on your own AI runtime, Claude Code or Codex, which needs a paid account starting around 20 dollars a month; you own that account and pay the provider directly, while FCT recommends one and sets it up during onboarding. Day to day you just open the folder and talk to your assistant. It works on Windows and Mac. Handoff includes documentation of what each folder does and how to extend it, plus an optional retainer for upkeep, drift prevention, and ongoing improvement.
04 How does the memory actually work?
Second Brain OS memory works on two layers so the assistant never resets between sessions. The first layer is durable facts injected at every session start — the things that should always be true in context. The second is daily logs built automatically from your session transcripts: a searchable record of everything that got built, decided, and why. Start a fresh session and the assistant reads back the whole arc instead of beginning blank. A weekly synthesis pass keeps the memory clean and ages stale, time-anchored facts to current reality, so the assistant does not silently go out of date — the same self-freshening shape the major AI labs now tout as background memory, but delivered as portable files you own and any model can read. On top of that, a growth loop reads your recent logs, finds the workflows you repeat, and surfaces them as new skill candidates you approve. The longer you run it, the more it knows you.
05 How long does setup take, and what add-ons are available?
Base setup of Second Brain OS usually completes in one to two weeks, with add-ons extending the timeline based on scope. Setup runs in five steps: FCT clones the template into your workspace folder, a guided onboarding skill interviews you to fill in identity, plan, memory, and business context and names your assistant, FCT wires the tools you live in — Apple, Google Workspace, Telegram, Cloudflare, GitHub, MCP servers — optional add-ons or automations are layered on, and FCT verifies startup context, memory writes, and at least one skill-backed tool before handoff. Three add-ons are available: Accounting, which tracks receipts, expenses, contributions, withdrawals, and subscriptions through Google Workspace; Coding, which adds a projects folder, repo conventions, and build, test, and release patterns; and Business Integration, which adds company context, products and services, and a revenue-framing plan for owners running a business with clients. Each can be bought upfront or added later.
Want one installed around your business?
Tell us how you work and what you run on. We'll scope the right setup, the add-ons that fit, and what the brain should know on day one.