Hawkfry

The company brain

A brain your agents can actually read.

Our company brain is a folder of plain markdown. It holds what no other system can: who people are, what was said, what was decided and why. People write in it. Agents read it, add to it and keep it tidy.

Ask it something

Watch a question travel through the brain.

Every dot is a note. Every line is a link. Pick a question a consultancy gets asked every week and follow the signal: which notes fire, in what order, and the answer the agent writes from them.

2 reads14 KB of context6 of 1,050 notes touched
  • Records
  • Compiled notes
  • Generated

Route

  1. 01Read the use case indexIndex/Use Cases Index.md · one line per use case
  2. 02Four descriptions matchno reads: the index line is the description
  3. 03Open the closest match, follow its linkKnowledge/Use Cases/Arc Health: Looker to Omni…

Answer

Yes, four times. At Arc Health we guided a 30-person data team through moving about 500 business users, using audits and scripts to decide what to keep, then training in waves. Lucky Quay was several hundred dashboards, with their engineers and analysts trained to run it themselves. Relayo took two weeks of daily co-development and went live before the old tool's deadline. Sendwell was customer-facing embedded analytics under a contract deadline. We also built a migration tool at Arc Health and have reused it since.

  1. 01Index
  2. 02Note
  3. 03Links
  4. 04Search
  5. 05Transcript

Cheap first. Stop the moment you have the answer. Most questions end on rung two or three.

Demo data from an anonymised copy of our own vault. Every client, company and person named is fictional, and figures are altered.

notes, one type each
1,050
links between them
16,619
decisions surfaced from meetings
729
lint errors allowed
0

Structure

Three layers. The layer decides who may change a note.

Every note sits in exactly one layer. That one rule stops the two things that rot a knowledge base: history being rewritten, and summaries going stale.

Compiled notes

Present tense. Rewritten freely when the evidence changes. One note per person, company, project, tool or method.

  • People/
  • Companies/
  • Projects/
  • Tech/
  • Knowledge/

Every claim traces to a record by link: "Edmund owns the Python asset models (since Jun 2026, [[meeting]])".

Example: People/Hamish Brackenbury.md

Anatomy

Every note says what it is before you open it.

The properties at the top are the retrieval surface. Pick a line to see what it buys the agent.

------# Norhaven Logistics <!-- generated:map:end -->

description

The line an index shows. An agent reads this, not the note, to decide whether the note is worth opening. Written as the answer to "why would I open this?".

Writing

The model judges. The script writes.

After a meeting, an agent runs the same seven steps every time. The model does the parts that need judgement. Code does everything that can be derived, so no one hand-keeps a list.

Script, no model

Sync, build, lint. vault sync-ids links new notes to the pipeline and ledger. vault build regenerates timelines, maps, decision logs and indexes. vault lint checks every note against the schema. Errors must be fixed before finishing.

Boundaries

The brain never holds live data. It holds the id.

Deal values, tasks, hours and balances change daily, so they stay in the systems that own them. A note carries the id of its record, which turns “look it up” into one exact query and never a name search.

  • Pipeline

    Deals, stages, values, contact details

    vault keeps: pipeline_company_id

  • Linear

    Tasks and tickets

    vault keeps: a project URL. No checkboxes.

  • Project ledger

    Time and billing

    vault keeps: ledger_project_ids

  • QuickBooks

    Money

    vault keeps: why, never how much

  • Google Drive

    Shared documents and deliverables

    vault keeps: a link

  • GitHub

    Code and technical docs

    vault keeps: a link

# "What stage is the Norhaven deal at?" is not a vault question.

$ pipeline opportunities get 2d802f18-db20-8781-3093-9c7451c30807

$ ledger projects status "Norhaven Web App Support"

The description is the most important field
One or two sentences answering "why would I open this?". It is what an index shows and what an agent reads to decide. Capped at 300 characters.
Links, never tags, for things
A client is companies: "[[Norhaven Logistics]]", not a tag with three spellings. Links are what the generated blocks are computed from.
One name, one note
Names are unique across the vault. People are linked by full name. An unresolved link is fine: it marks something worth a note later.
Size limits keep reads cheap
Compiled notes stay under 25KB. Generated lists show the latest 30 entries. Transcripts live apart and are opened last.

Want a brain your agents can read?

We turn how your business thinks and operates into a brain AI can use. Tell us about your business and we'll map where to start.