01 · tool · Knowledge substrate
2nd brain
What your agency knows lives on disks, in mailboxes and in heads. What you recommended on a comparable case sits in an archive nobody can question.
You ask your agency what it knows, and the answer comes back in seconds with the notes it came from.
- Each source filed for you, one note
- Search by meaning, not by keyword
- Every answer arrives with its source notes
Your own keys, a rebuildable index, Markdown and JSON exports: if a tool dies one day, you take it elsewhere.
01
What the tool does today
One app, one screen: what the agency knows, and the deliverable that comes out of it. The Second Brain is the first layer.
Contexte, Connexions, Cadence
Three columns, one screen. On the left, the client's Contexte, Connexions and Cadence. In the centre, the agents that read them brief after brief; on the right, what they produce.
One source, one note
Every source becomes a clean Markdown note: the substance is pulled out and set in the same shape as the rest, never copied in as-is. One note stands for one unit of knowledge.
Answers before the index exists
Ask in your own words: the match is made by meaning, not by exact keyword. With no live index yet, it falls back to a local keyword search instead of failing, so it answers before the index is built.
Nothing goes live untested
An index is not usable because it was built. Recall is tested on questions whose answers are already known, the results are checked, and only then does anyone use it.
Every answer, sourced
A question comes back answered in seconds, with the notes behind it. You open them and check for yourself. Never a claim floating free of its source.
02
How it works
One pipeline, from scattered material to an answer you can check. No step is skipped, and the index opens for use only once it has proven it recalls right.
- 01
Sources
Disks, mailboxes, heads: the material as it actually sits today.
- 02
Normalisation
Each source becomes a clean Markdown note, one note per unit of knowledge.
- 03
Index
The notes are indexed so a question can find them by meaning.
- 04
Acceptance check
Recall is tested on known questions before anyone gets to use it.
- 05
Recall
An answer in seconds, with the notes it came from.
03
How it can grow
V1 stops at the agency's own material. That is a matter of sequence, not a smaller promise.
V1 · your own material
Your own material only, recalled by meaning, with a local fallback before the index exists and a separate space per client. Your own keys, a rebuildable index, Markdown and JSON exports.
V2 · past engagements join in
Once the base is alive and the team owns it, the archives of past engagements join it and answer the same way. An extension, not a narrower v1.