Hebbs
self-hosted
wired in this demo

Needs you

3 everything else the brain handled alone

Two sources disagree about the enterprise support SLA.

24 hours
48 hours

Both are cited, so both were kept. The brain will not pick a winner.

open 4 days

3 claims were blocked for bad citations. None entered the brain.

last Jul 27

The Q2 connector freeze expired. Renew it or let it archive.

expired Jun 30

New since you looked

14 facts · 6 commits

Enterprise moves to $4,200 per seat per year on August 1. Existing contracts hold their price until renewal.

decision

Vantage Corp was promised custom SAML SSO by September 15, in a signed addendum.

commitment

Amara Diallo joins as Head of Support on August 11, reporting to the COO.

fact

The brain

@ 8f3c21a
00-index1
20-domains47
30-decisions28
40-people41
50-pending6
60-daily30
99-archive83
312 facts · 1.2 MB · ⊘ 3 quarantined

Every fact is cited

this week
312accepted by the gate
3blocked and quarantined

Nothing uncited has ever entered this brain. A brain that never blocks anything is a brain that is not checking.

Last sleep cycle

6h ago · 8f3c21a
merged duplicates
47 → 12
revised stale facts
12
archived expired
8
new conflicts held
2

It tidied itself while nobody was watching, and it wrote down what it did.

Feeding the brainreadwaitingstate
⌕Slack meridian.slack.com 18,4020 ● live · 6m ago
▲Notion specs & runbooks 3120 ● live · nightly
⊙veylan.io/changelog competitor watch 1,8470 ● daily 9:00
▶YouTube 3 channels 41218 ● live · 1h ago
✉Gmail sales@, support@ —— ⚠ auth expired 2 days ago
✉ meridian@in.hebbs.ai forward or CC anything and it gets distilled

what’s our SLA?

Enterprise first response is 24 hours, confirmed with the customer on July 24. Sev-1 incidents page the on-call engineer within 15 minutes, around the clock.

There is an open conflict inside this answer. The support runbook still says 48 hours and nobody has ruled on it. Both versions are in the brain, both cited.

Receipts4 sources
⌕“we are committing to 24hr first response for enterprise” #sales · Dana KimJul 24
▲Vantage_MSA.pdf · p.4 · “first response within one business day” Notion · legalJun 28
⌕“sev-1 pages on-call directly, 24/7, no queue” #eng-platform · Jonas WeberApr 28
▲runbook.md · “first response: 48 hours for enterprise” Notion · supportMar 2

The brain is files. Open anything.

Distilled markdown in a git repo you own. Grep it, diff it, clone it, leave with it. Every state is a commit, so history is free.

312 facts · 1.2 MB
⊘ 3 quarantined lives in github.com/meridian/brain-data
20-domains/support/sla.md last commit 8f3c21a · 2h ago distilled from 6 messages 14 facts · 1 conflict

Support · Service levels

Facts

Enterprise first-response SLA is 24 hours.

commitment
⊗ Conflict · unruledheld 4 days
A

First-response SLA is 24 hours, committed on the Vantage renewal call.

B

First-response SLA is 48 hours per the support runbook.

both kept, both cited, neither deleted

Sev-1 escalation pages the on-call engineer within 15 minutes, 24/7.

fact

Enterprise support includes a named CSM and a shared Slack channel.

fact

Standard plan support is community plus email, best effort, with no SLA attached.

fact

Archived · kept with its citations

Holiday support rota runs through January 2.

expired · moved by the sleep cycle

What is the enterprise first-response SLA?

The brain found two answers and kept both rather than guessing. Conflict c_4a91b2, open since July 26.

Side A
24 hours
“Confirmed with Vantage on the renewal call: we are committing to 24hr first response for enterprise. It is in the addendum going out today.”
Side B
48 hours
“Runbook SLA for enterprise tickets is 48 hours first response. That has not changed since March.”
older by 144 days

Your ruling is committed to the brain with your name against it. Nothing is deleted: the losing side moves to 99-archive/ and keeps its citations, so the answer stays reversible with git revert. The same ruling can be made from chat, because list_conflicts and rule_conflict are MCP tools.

Claims the gate refused.

The citation gate is plain code with no model in it. It checks every claim’s citations against the messages that were actually ingested. None of these entered the brain.

“Vantage signed a three-year deal worth $480k.”

invented_citation cited a Slack permalink that is not in the ingested snapshot
would have landed in 20-domains/accounts/vantage.md · Jul 27

“Support SLA is 12 hours.”

dropped_citation the fact lost its source when it was re-distilled
would have landed in 20-domains/support/sla.md · Jul 25

“- - -”

unparseable not a statement
source: Notion · specs · Jul 22

Most products hide their rejections. Here the rejection is the feature. Three blocked out of 315 is the number that tells you the other 312 were checked.

Everything this brain is fed.

Raw messages stay where they live. The brain keeps the distilled fact and a link back to the source, which is why a dead connector is the worst failure it can have: the brain looks healthy while it goes stale.

⌕

Slack

meridian.slack.comlive
18,402messages read
42channels
0waiting
▲

Notion

specs & runbookslive
312pages read
nightlydiff sync
0waiting
▶

YouTube

3 channelslive
412items read
18waiting
1hsince last pull
Comments arrive as individually deep-linked items, so a fact distilled from one comment links back to that comment.
✉

Gmail

sales@, support@auth
—read since Jul 25
2dsilent
The token expired. Nothing has been read for two days and the brain did not tell you until now.

Watching the open web

Archive

one time · done Jul 12

veylan.io · 1,847 pages read, back to February 2023.

Every archived page carries its own publication date, so a 2023 page never reads as today and never distorts staleness.

Watching

daily 9:00 · next in 22h

14 meaningful changes in 30 days. 41 changes ignored.

Only the diff is sent for distillation on a change, never the whole page.

Tell me when

plain language, no rules to write

pricing changes, a new tier ships, or the SLA page moves. skip nav and blog reshuffles.

The inbox

Anything that lands here gets distilled. This is how a source with no connector still reaches the brain.

✉ meridian@in.hebbs.ai forward, CC, or one auto-forward rule
▣ drag files or whole folders PDFs, decks, transcripts, exports
⚿ POST https://in.hebbs.ai/v1/events bring your own connector

Who and what can reach this brain.

Permissions are shown as what they let you do, never as role names. Every read is counted against the thing that made it.

People

whocanreads / mo
parag@meridian.dev you runs everything 2,104
maya@meridian.dev rules conflicts, reviews blocked claims 880
dan@meridian.dev asks questions in Claude 1,431
priya@meridian.dev left revoked Jul 3 0

Her keys stopped working the same minute. Everything she taught the brain stayed, with her name on the commits.

Agents

agentcanreads / mo
Support triage asks questions · claude-haiku-4-5 3,381
Cowork asks questions · vertex 1,204
Claude Code asks questions · claude-opus-5 342
Fern contractor asks questions · expires in 12 days 44

Humans stay roughly constant. Readers multiply. 128,441 reads this month against 4 people, which is the shape of the bill and the reason the meter is per agent.

Use your brain inside the tools you already use.

One MCP endpoint, read-only, token-budgeted, every read logged. Sign in rather than paste a key.

https://brain.meridian.dev/mcp

In Claude: Settings → Connectors → Add, then sign in with Hebbs. OAuth 2.1 with dynamic client registration and PKCE, so there is no key to paste and no key to leak.

This brain is self-hosted, so the endpoint is your own domain. On Hebbs Cloud the same brain answers at https://mcp.hebbs.ai/meridian. Same binary either way.

Claude Claude Desktop Cowork ChatGPT Cursor Codex any MCP client

What your tools can do

✓get_orientationwhat this brain covers, rewritten after every sleep cycle
✓grep_brainsearch across every cited fact
✓list_brain_filessee the shape of the repo
✓read_brain_fileread one topic at a time, pinned to a commit
✓resolve_citationfetch the original message behind any fact, live, never stored
✓list_conflictsgovernors only
✓rule_conflictgovernors only
✓review_quarantinegovernors only

A teammate who can only ask questions does not get the last three. They are not greyed out and they do not return an error: they are absent from tools/list, so the model never learns they exist.

While you were away, the brain tidied itself.

Sleep cycle finished 6 hours ago and committed as 8f3c21a. Next one in 18 minutes.

Merged duplicates47 → 12

28 scattered mentions of the Vantage renewal became one fact: renewal moved to Q4, budget freeze until then, Lena Ortiz is the champion.

Revised stale facts12
Project Halo ships in June→Project Halo shipped in August
Dan is joining in February→Dan joined in February
Trial extensions go through sales→Trial extensions are self-serve since July
Archived8
Q4 2025 pricing termsexpired Jan 199-archive
Priya’s open action itemsperson left99-archive
Holiday support rotaran through Jan 299-archive

Nothing is deleted. Archived facts keep their citations and stay searchable.

New conflicts, held for a human2
Enterprise support SLA · 24h or 48hc_4a91b2
Self-serve trial length · 14d or 30dc_71d3e8