[ THE GAP · 02 ]
Decisions made in one team rarely reach another.
Patterns settled last quarter get re-litigated by this quarter’s hire.
Your AI gives confident answers to questions your org already closed.
[ 01 · CAPTURE ]
A team makes a decision.
[ 02 · STORE ]
It becomes context.
[ 03 · RECALL ]
Anyone can ask, anywhere.
[ 04 · APPLY ]
The AI cites the source.
Let's use server actions for forms
OK — with which validation?
zod, single schema both sides
Forms: Server Actions + zod (shared schema, both sides).
— @mira · captured automatically
Forms: Server Actions + zod
[ MECHANICS · 03 ]
[ 01 ]
Shared, organizational drawers. Where every team’s decisions, patterns, and constraints live — readable by every member, queryable by every AI.
[ 02 ]
Personal context. Half-formed thinking, working notes, what’s still yours alone — until you choose to publish it to a Space.
[ 03 ]
Decision · constraint · pattern · entity · open question · event · preference. Every drawer is typed, so retrieval lands the right thing at the right moment.
[ PROTOCOL · 04 ]
§ READ
Every session starts with a read. The AI checks what your org has already settled — decisions, constraints, patterns — and aligns to them, instead of generating a clean-room answer that quietly contradicts what your team agreed last month.
§ WRITE
When a session produces a real decision, a new pattern, or a constraint worth remembering, it lands in the right Space — typed, searchable, available to the next member or session that needs it.
[ INTEGRATIONS · 05 ]
— BEGIN —
One context layer. Every team. Every session.