Core
Brain
The store every component reads from and writes back to. It ships empty, fills from the onboarding interview, and then grows on its own every time a component finishes a job.
Recent writes
livefinance/invoicesAcme pays on 20th, not 7th. Terms corrected.marketing/brand-voiceNever say 'leverage'. Added to vocabulary.finance/reconciliationStripe fees post a day late. Match on T+1.marketing/cold-outreachRetail ICP replies at 2x on Tuesdays.
Nothing here was typed by hand. Each line is a component recording what it learned while doing something else.
How it behaves
Pages, not rows
Everything the Brain holds is a page with a title, a type and links to other pages. A client, a decision, a price, a process. Links are how an agent gets from the job in front of it to the thing it needs to know.
Written by the work
No one sits down to fill it in. A component writes back at the end of a run, in the words that were actually used, and the page is there the next time anything looks.
Read before acting
A component reads the Brain before it drafts, prices or sends. That is the whole difference between an agent running on a generic prompt and one running on your business.
Corrections win
When something in the Brain turns out to be wrong, the fix replaces it rather than sitting underneath it. A page that contradicts itself is worse than no page.
Why it starts empty
Most tools arrive full of somebody else's assumptions about how a business runs, and the first month is spent arguing with them. Bastion arrives with none. The cost is that it knows nothing on day one. The return is that by the end of the first month it knows things no competitor's tool can be told.
Your data sits in your own schema, isolated at the database, and no component can reach another tenant's. Nothing sends, posts or pays without a person deciding.
Seeding it
The onboarding interview seeds the Brain once. After that, install a component and it starts contributing on its first run.
bastion onboard