Our own · BrainRunning (our own)
Brain.
The planning system OCTYN runs its whole portfolio on. It knows the state of every project, it is not allowed to build or deploy anything, and it will not mix two projects into one answer.
For your leadership teamInside: long-term memory · project state · planning that never deploys
The Brain, at a glance.
Running: this is OCTYN’s own system, drawn on Paper from its real screen. It is static here. The sessions and systems on it are anonymized.
- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
Repo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
Company dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Resume
Open tasks and the last session's decisions load first.
Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
Nothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
Drag sideways to read the whole screen.
In shortBrain is the planning system OCTYN runs its portfolio on. It knows the state of every project, it plans and teaches, and it never builds or deploys.
- Every system has its own session, and they run at once.One row per system, ten shown and eight more behind them.Read how
- Planning ships no code. Learning keeps its own state.The firm workspace is cross-linked and read only.Read how
- Three stores hold what lasts, and memory is always loaded.Repo, vault and memory. A session reads at the start and writes back at the stop.Read how
- Anything that wants a person lands in a queue.A plan ready, a decision. It is pushed to a screen or a phone.Read how
- No session starts cold.Recall, load, work, write back, and the next session begins from what was written.Read how
The deep dive.
The same screen, taken apart: what each region holds, the rules behind it, one session walked from recall to write back, and the three ways it breaks.
Every morning the context had to be rebuilt.
Twenty-one codebases, and one person in front of all of them. The limit is not typing speed and it is not compute. It is that each morning the context has to be rebuilt: what state a project was in, what was decided about it, and the reason for a decision that now looks strange.
The workspace audited on 2026-07-24 held more than twenty repositories and roughly 34,853 files, with 141 markdown notes across 15 subprojects. Nobody holds that in their head, and a system that tries to hold all of it at once does not help either.
The obvious build is a search over everything, and it fails twice. The costly failure is not a missing answer but a blended one, a confident reply that quietly merges how two projects deploy. And loading the whole workspace to answer one question is the habit the system is meant to cure.
The Brain screen, taken apart.
The screen has three columns and a foot: sessions on the left, the three stores in the middle, what a person reads on the right, and one session’s path along the bottom. Here is each part in turn.
One map of how the memory is used.
Sessions on the left, the three stores in the middle, what a person reads on the right, and one session’s path along the foot. The header counts the system sessions reading and writing.
- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
Repo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
Company dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Resume
Open tasks and the last session's decisions load first.
Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
Nothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
- The screen
One map of how the memory is used.
Sessions on the left, the three stores in the middle, what a person reads on the right, and one session’s path along the foot. The header counts the system sessions reading and writing.
- Left · Sessions
One session per system, all running.
Each row is a session on one system. A filled marker is a session working now; a hollow one has been quiet for hours or a day. The time at the right says when it last moved. Eight more sit behind the ten shown.
Sessions, in parallelone per system- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
- Left · Roles
Roles that stay out of each other’s way.
Planning sequences the work and ships no code. Learning keeps its own state, kept apart. The firm workspace is cross-linked and read only. A role that never touches the others cannot blend them.
Sessions, in parallelone per system- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
- Centre · Stores
What lasts is held in three places.
The repo holds architecture plans, the task mirror and a map of what every file does. The vault holds notes: product definitions, progress logs and portfolio status, plus two knowledge banks. Memory holds short linked facts about how the work is done and what was decided, and it is always loaded. Sessions read at the start and write back at the stop.
Sessions, in parallelone per system- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
- Right · Read out
The state of every system, for a person.
A company dashboard shows drift, tasks and momentum for every system, with a daily digest. A review screen queues anything a session wants a person to look at. The phone carries screens, files and alerts for review away from the desk. The stores are ingested every 15 minutes.
Sessions, in parallelone per system- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
- Right · Review queue
The only way Brain asks for anything.
Each line is something waiting on a person: a plan ready, new shots, a decision. It says whether it goes to the screen or the phone. Brain plans and teaches, so its output is a thing to review, not a thing done.
Sessions, in parallelone per system- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
- Foot · One session
No session starts cold.
Resume, load only what is needed, work with every step tracked, then write back. The last step feeds the first step of the next session. The next session begins from what this one wrote down.
Sessions, in parallelone per system- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
The rules Brain runs on.
Brain runs today, on OCTYN’s own portfolio. These figures play the rules the write-up records, one at a time. They are drawings of the rule, not a recording of a session.
How a session reads, and where it stops.
QuestionA question that status alone answers.
- 01Recallopen tasks and the last decisions
- 02Statusportfolio status
- 03Mapwhat every file does
- 04Definitionthe product definition
- 05Historythe progress log
Stopped after status. The rest stay unread.
How an answer stays one project’s.
QuestionA question about system 04.
The other project was never mixed in.
Where Brain’s work stops.
One session, from recall to write back.
The foot of the screen, played one step at a time. The step that changed is marked, and the stores a step touches stay lit.
Open tasks and the last decisions load first.
Resume is the first thing a session does. Memory is always loaded, so what was decided and why is already there, and the task mirror says what was open.
- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
Repo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
Company dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Resume
Open tasks and the last session's decisions load first.
Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
Nothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
When it breaks.
Three failures, in increasing order of what they cost. The one that cannot happen is a wrong deploy, because Brain cannot deploy.
- Sessions, in parallelone per system
- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
A miss.
The loader stops too early and the answer comes back thin. The person asks again with a pointer. It costs little, and it is the failure the tiering is biased toward on purpose, because it is the recoverable one.
- Sessions, in parallelone per system
- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
A blend.
Two projects merged into one answer, delivered fluently. The defence is structural: separate workspaces and a rule against mixing, stated rather than hoped for. There is no automated detection of it. The person who asked is the one who spots it.
- Sessions, in parallelone per system
- system 01now
- system 024m
- system 039m
- system 04now
- system 052h
- system 0612m
- system 071d
- system 086m
- system 095h
- system 1031m
- + 8 more
- Planning
- sequences the work, ships no code
- Learning
- its own state, kept apart
- Firm workspace
- cross-linked, read only
→reads at startwrites back at stop←Brain, three storesdurableRepo
plans · tasks · mapsArchitecture plans, the task mirror, and a map of what every file does in every system.
Vault
notesProduct definitions, progress logs and portfolio status, plus two knowledge banks.
Memory
always loadedShort linked facts: how the work is done, what was decided and why.
ingested every 15 min→Read outfor a personCompany dashboard
Drift, tasks and momentum for every system, and a daily digest.
Review screen
Queues anything a session wants a person to look at.
Phone
Screens, files and alerts for review away from the desk.
Review queuewaiting on a personsystem 04 · plan readyscreensystem 01 · new shotsscreensystem 08 · a decisionphonepushed to a person when ready to reviewOne session, start to finishno session starts cold01 · recall→Resume
Open tasks and the last session's decisions load first.
02 · load→Only what's needed
Status, map, definition, history, in order, and it stops once the question is answerable.
03 · work→Tracked as it moves
Every multi-step job becomes tasks, mirrored to disk as they change.
04 · write back↺ next sessionNothing is lost
Decisions, progress, tasks and the file map are written back for the next session.
A stale recall.
A fact that was true in July, recalled in September with no sense of its age. This is the one to watch as memory carries more. It is why tracing a recall back to its source mattered more than recall quality when memory moved to Alchemyst.
- Reads what is queueda personA plan ready, new shots, a decision. Brain puts it in the queue and waits.
- Catches a blendthe person askingA blended answer is obvious to whoever knows which two projects were merged. It is caught by a person, not a test.
- Asks again after a missthe person askingA thin answer gets a pointer and a second question.
- Changes the setupthe person who runs itAdding a project, adding a learning track, changing the reading order. Configuration, no code.
What Brain does, and what it does not.
- Recorded 24 July 2026
- 20 plus repositories, about 34,853 files under one workspace.
- Recorded 24 July 2026
- 141 markdown notes across 15 subprojects.
- Recorded 14 September 2026
- Two roles, five context tiers.
- Recorded 14 September 2026
- No retrieval accuracy measured.
- The line it holds
- Brain plans and Brain learns, and Brain never builds or deploys. That is not a limit waiting to be lifted. It is what makes it safe to consult, because the worst outcome of a wrong answer is a wrong answer.
- What was built
- One workspace over everything. Two roles that stay out of each other’s way, a planner and a learning partner. A tiered context model where stopping early is the default. Company memory on Alchemyst, so context carries between sessions and a recall can be traced to its source. A business workspace beside it on the same memory.
- What it does not do
- It does not act. Letting Brain act would be a different system with its own containment. It assumes one reader at a time, and more than one reader with different permissions is a different data model.
- Not measured
- There is no fixed question set for context selection, so no one can say what share of answers pulled the right project’s material. That is the biggest gap in the system, and it sits where the design lives.
- What changes in six months
- Adding a project, a learning track or a reading order is configuration, with no code. Another role is an addition, not a rework.
- What we would do differently
- Build the test set first. Pick where memory lives before the corpus grows. Write the reading order as a file that changes with the code, so it stops describing a system that no longer exists.
Something like this, for your company?
The first conversation is with the people who would build it. If there is a fit, the Consult comes next.