instibrain
instibrain  /  context engineering

Your AI knows who it is, what is true, and how you work.

Context engineering decides what your AI holds in mind before it answers. A brain keeps three kinds of it as pages, each shared with its own people, and your AI loads them a step at a time. What happened, and your files, stay out.

Left out: last week's thread, and the signed contract, which your AI opens only when the quote needs a clause.

five kinds

Five kinds of thing reach your AI. A brain keeps three.

The field has a word for each, and one test tells them apart. Mix them on one page, and your AI reads a story where it needed a rule.

What it isThe field's wordThe testIn a brain
Who your AI is, and the rules it keepssystem prompt, instruction fileChange it, and every task changesKept, and read first: instibrain's identity.md, then your user-profile.md, then the space's rules
What is true in your companysemantic memorySomeone owns it and would correct itKept: a page for each subject, in a space shared with the people who may read it
How the work is done, kind by kindprocedural memoryIt starts from a situation and ends in stepsKept: a specialist, shared with its own people; a tool page for each system your AI reaches
What happened, and who said whatepisodic memoryIt has a date and a storyKept where it ends: a room holds the talk for 30 days, an operation's folder the work until it closes
What your company has: files, records, tickets, maildata; the environmentYou search it; nobody reads it allKept out: in your own systems, through your AI's connectors; a page says where each lives

Your AI reads the first kind before anything, an index of the next two, and a page when the task needs it: progressive disclosure. A brain of thousands of pages starts it with its rules and the index; the rest waits until a task names it. Which page it opens is the AI's call.

what happened

What happened stays out. What it taught goes in.

A thread buries the rule under who said what, and the next model reads every word of it. A page holds the rule as it stands, and the next model reads that.

pricing/floors.md · as savedthe writing check
# Pricing floors The floor for a yearly plan is $28k. 2026-11-03: Ben asked whether Acme could go to $26k. Mara agreed to $26k if Acme signs for two years. We decided to keep $28k for everyone else. The quote template was updated the same day. instibrain's writing check found this in pricing/floors.md (the system's identity, How a page reads); fix it now: - line 5: history: a line that starts with a date, 2026-11-03. - line 7: history: "we decided". - line 8: history: "was updated". State what is true now; the page's versions keep the rest.
pricing/floors.md · as it standswhat every AI reads
# Pricing floors The floor for a yearly plan is $28k. A two-year term may go to $26k; Mara approves it. Who asked, who agreed, and when: in the room where it was said, for 30 days, and in this page's earlier versions, for the people who recover them.

The page and its people are an example; the check's answer is the product's own, run on it. The check reads what each save adds and refuses nothing; it asks your AI to fix the lines in the same turn. The inbox and a log page hold history by design. Version history.

your files

Your files are the world your AI works in.

A contract, a ticket, a customer's record: needed, and never read whole. Your AI finds them through your own connectors; the brain holds what your company knows about them.

a page · in the brainWhat your company knows about the contract.
  • The Acme contract runs to March 2027
  • It sits in Drive, under Legal / Acme
  • Legal owns it; a renewal goes to Dana
  • Your AI may quote its term, never its price
the file · in your own storeThe contract itself, opened when a task needs a clause.
  • The signed PDF, where your team keeps it
  • Found by your store's search, through your AI's connector
  • Read for the clause the task needs
  • Never stored or indexed by us

The contract and its people are an example. A page grants no access: your store decides who opens the file. Pages know. Retrieval finds.

a repo, a skill, a project

A repo, a skill, and a project each hold one pile.

Each does a real job. None keeps the kinds apart, gives each its own people, and reaches every AI you use. A personal second brain is one such pile for one person: what a company's adds.

The questionA markdown repoA skillA project in your AI's appA brain
What does it hold?Whatever is committed, every kind side by sideOne method: how to do one kind of taskInstructions, and files your AI looks things up inWho your AI is, what is true, and how the work is done, kept apart; your files stay where they are
Who reads which part?Everyone with the repo reads all of itEveryone given it gets the same methodEveryone it is shared with reads all of itEach space, its own people; a label on each page; a sealed space opens on their computers alone
Which AIs read it?An AI with a copy, or a connector to where it is hostedAn AI that loads skills from where it is keptThat app's AIEvery AI you connect, on the web and the phone too
What loads first?Whatever the AI opensIts description; the rest when a task matchesWhat the app decidesWho it is, then the index, then a page when the task needs it
Who fixes a wrong line?Whoever may commitWhoever keeps the skillWhoever may edit the projectAnyone who may write the space, in the browser or as a file, each version kept with its writer

A small technical team can keep its pages in a repo, and the brain's folder is markdown that git keeps too: a brain beside a Git repo. A method a team shares is a specialist here, and it reads each person's own facts.

build it yourself

A repo is the first weekend. A team's brain is the rest.

Files, history, and a diff come with git. A team that puts its AIs on those pages needs eight more things, and each is built and tested here.

  • Its own peopleEach space shared whole, each AI held to what its person gives it
  • Pages we cannot readA sealed space, encrypted on your computers, the path included
  • Every AI, one addressClaude Code, Codex, and Claude on the web and the phone
  • The same files everywhereOn every computer; when two edit at once, your AI merges both
  • A save that checks itselfA secret refused; pay and health refused where others read, until the owner allows them
  • Text that stays putAfter a confidential read, a write that carries it wider waits for a manager
  • A method shared apartA specialist, reading each person's own facts
  • AIs that ask each otherRooms, where you read every word

How each part works, with the real payloads · every limit, beside its guarantee.