◌ how it works

Not a notepad. A knowledge engine.

The resume card is one read of a deeper store. Every capture records the reasoning, not just the files — and the engine distills it into a preamble: a coverage-banded map of what you know, growable from the web, queryable from anywhere.

◌ the resume card

Everything you need to re-enter. Nothing you don't.

▸

the latest hypothesis

One line, written at capture — the thing you were actually trying to do.

▸

a snapshot trail

7 timestamped states behind the card, so the history is there if you need it.

▸

a coverage band

rich / sparse / gap — how much real signal the card is built from. Click the chip to cycle it.

◌ br8n · dev 3 minutes ago

HYPOTHESIS

Wiring SupabaseStore behind get_store() so the cloud tier carries the per-request token.

7 snapshots │ 4 files

WHERE YOU WERE

▸src/br8n/store/supabase.py cursor+84−12

·src/br8n/api/deps.py +22−3

·src/br8n/store/__init__.py +6−1

git diff --stat 4 files +112 −16

◌ under the hood

From snapshot to a context spine.

Each capture moves through four stages. The output isn't a pile of notes — it's a single, coverage-banded map of what this repo and branch actually know.

capture──▶ distill──▶ map──▶ tap

01capture

Reasoning, not files

Each snapshot becomes a finding — your hypothesis and intent, kept alongside the diff and cursor. The thinking is the payload.

02distill

A standing synopsis

The engine rolls findings into a synopsis — your standing topics, each tagged with a coverage band so you know how grounded it is.

03map

One context spine

Findings link across sessions into a single preamble — the map of what this repo and branch actually know, not a pile of notes.

04tap

Grow on demand

Thin coverage? The gap-fill pipeline — plan, search, crawl, extract, merge — pulls from the web and folds it back into the map.

◌ br8n · dev · preamble

<preamble>
  <synopsis>
    <entry topic="Storage tiers">Local SQLite vs cloud Supabase behind one get_store() seam.</entry>
    <entry topic="Per-request token">SupabaseStore carries the access_token so RLS scopes correctly.</entry>
    <entry topic="Coverage banding">rich / sparse / gap — how much real signal a card is built from.</entry>
  </synopsis>
</preamble>

● the same spine the resume card reads — and what every surface taps

Run the loop yourself.

Two lines, on 127.0.0.1. Capture, then come back to the card.

$ /plugin marketplace add anthonysuherli/br8n

$ /plugin install br8n@br8n