Knowledge map
Organize the selected notes, reference material and source links your workflow needs. Agree what belongs in the workspace and what stays out.
Buyer guide · Reviewed 23 October 2026
What is a second brain?
A second brain is a personal or business workspace that helps you keep, find and use the knowledge behind your work. It brings together selected notes, project context, decisions and workflows so you can continue with less repeated searching and restarting.
ARCHon builds your second brain around one recurring workflow. Start with one owner, the knowledge you need to keep and a clear way to pick up where you left off.
Follow one update through the workflow Build my second brain01 / The useful distinction
A place for the thinking that should survive the day.
Most people already have fragments of a second brain: documents, messages, decisions, bookmarks, checklists and project handoffs. The problem is that these fragments are hard to reconnect when the next decision arrives.
A custom build gives selected notes, decisions and source links an agreed home. For your first workflow, the aim is to make it easier to find why a decision was made, see what remains open and continue the next task with the relevant context.
The system is designed around your information and responsibilities. It does not automatically remember everything, train a model on your content, or remove the need for review.
Recorded workflow / Fictional project
One update.
A handoff you can trace.
A launch changes. When you return to the project, you need the decision, the open question and the source together.
This is a recorded isolated run using ARCHon’s captured storage and context code. Northstar Sample Studio and every record below are fictional. Selecting a step replays saved evidence; it does not run an AI, contact a provider or touch a live workspace.
Step 1 of 5Draft source
Keep the original update
A fictional launch note is saved as a draft. It is stored, but not yet eligible for selected context.
Launch moved to 12 November 2026. No budget is approved. Next: confirm the revised launch checklist.
Verified in the isolated run: saved source text matches the original.
Original source shown. Recorded controls require JavaScript.
How this was verified, and what it does not prove
On 22 October 2026, the captured Store.save, Store.get and Store.context code was executed against a new temporary local vault. The run saved a draft, retained a revision, rejected a stale edit, selected reviewed project evidence, saved a draft handoff and reopened that handoff in a new Store instance.
Sixteen checks passed, including rejection of draft, restricted and other-project selections. Review in this run is a record status, not an independent reviewer event. Hosted/cloud persistence, owner login, integrations, automatic synchronization and customer results were not tested.
The handoff text was assembled deterministically from its source. No AI model, agent, email or external action was called.
Read or download the recorded evidenceSource release: Office36 / 483499d. The receipt includes source hashes, fictional record IDs, revisions and the individual checks.
Fit first / No new system by default
Build around a recurring problem.
A custom second brain may fit when you repeatedly search old messages for a decision, restart a project without its context or struggle to turn scattered notes into a useful next step.
Start with one workflow you already do: keeping a client project up to date, preserving decisions or preparing a project handoff. These are possible uses, not measured customer results. The first build is scoped for one owner; team access is a separate discussion.
If a small notes collection or an existing template meets the need, that may be the better starting point. A custom build should solve a specific problem you can test.
02 / What a custom build can include
Start with one owner and one workflow.
Project continuity
Keep project updates and handoffs that show what is done, what is uncertain and what to do next. Reopen the saved context when you return.
Decision record
Keep decisions with their reasoning and source references, so you can revisit why you chose a direction.
Workflow guidance
Define repeatable steps, review points and the information needed for the next task. Where useful, include text-based Skills: saved instructions you can review and reuse.
These capabilities guide the scope; they are not a fixed package. Integrations, AI-assisted routines and scheduled work are assessed separately. Any included automation needs agreed inputs, provider access, usage limits and review rules. Saving a Skill does not install software or grant tool access.
Build process / Agreed before work starts
Three clear stages before the system becomes yours.
- 01
Understand
Choose one recurring workflow, the information it needs and a practical example of a successful result. Identify your existing tools and what must stay out of scope.
- 02
Design and build
Agree the workspace structure, tools, access, ownership and acceptance examples. We then build the agreed workflow around those requirements.
- 03
Test and hand off
Test the agreed flow with you, including saving and reopening an update, finding its source and preparing the next handoff. Document what was delivered, known limits and maintenance responsibilities.
Price and delivery are agreed case by case before work begins. The proposal distinguishes the build fee from any provider subscriptions, AI usage, hosting, integrations or ongoing support. Additional users or workflows need a separate scope agreement.
Before we agree the build
Know what will be handed over.
Use this checklist to agree the first build for one owner and one workflow. Confirm which items are included, changed or excluded before work starts.
- Structure: knowledge areas, project index, decision records and the source material that belongs in each.
- Working flow: the capture, review, retrieval and handoff steps that should work, with concrete acceptance examples.
- Access and ownership: who owns accounts and files, who can change them, and how access can be removed.
- Handoff and upkeep: the delivered notes, known limits, maintenance responsibilities and any separately agreed support.
- Separate costs: provider subscriptions, AI usage, integrations, hosting or ongoing work where applicable.
Bring one example of work that is hard to continue, the tools holding its information and the result you want to achieve. Describe what must stay out. You do not need to upload private records to start the conversation.
Questions / Before you ask us to build
Useful questions, answered plainly.
Who is the first build for?
One owner with one recurring workflow and useful context spread across notes, project updates or decisions. We check the fit against an actual task before agreeing the build. Team access and additional workflows are scoped separately.
How much does it cost, and how long does it take?
Price and delivery are agreed case by case. They depend on the workflow, tools, access requirements and acceptance checks. We agree the scope, delivery plan and build fee before work begins, with any provider, hosting or ongoing support costs identified separately.
Can it use my private content?
Only within the agreed scope and access rules. Before including it, we agree what may be used, where it will be stored, who can access it and what must stay out. Data handling and recovery requirements need to be agreed for your deployment.
Will it work with my current tools or AI subscriptions?
We assess your existing setup first. A connection or AI routine is included only when it is explicitly scoped and tested. Provider access, subscriptions and usage costs are discussed separately; automatic synchronization across every tool is not assumed.
Who owns it after handoff?
Account and file ownership, access removal, maintenance and support are written into the agreed scope and handoff. Confirm which accounts you control, what is delivered and which ongoing responsibilities or charges remain.
Your next step / Start with the work
Tell us what keeps getting lost.
Tell us about one workflow you keep restarting or one decision you struggle to find again. We will discuss the fit, scope, price and delivery before any build begins.