fig.00·a subdomain of ×marble · curation, not feed

The eventsworth showingup for.

Your knowledge graph, applied to the week.Most weeks, the answer is silence.

connect your marble →~5–8 min · one terminal command · KG stays local

   your KG ──●──┐
                │
                ●  marble — selection
                │
                ●──→  the irresistible few

fig.01·weekly verdict · most events fail the bar · n→0 by design

01selection

Marble grades each upcoming event against your graph. Most don't pass. The ones that do reach you with their reasoning attached.

Every Sunday, your laptop scores the week. You see the survivors, not the slush pile.

Graph, model, and scoring run on your machine. We see the picks, not the math.

iii

Most weeks reach you empty. That's not a bug — it's the point.

Each pick names the specific interest, belief, or identity it matched. No black box.

02boundary

We hold less than you'd think.

stays on your laptop	reaches our server
your raw knowledge graph	—
your LLM API key	—
any data you let marble learn from	—
—	~12 coarse interest labels
—	top picks (event ids + 120-char reasons)
—	a 3-color palette derived from your graph

03connect

One command. Five to eight minutes. The tab tells you when you're in.

i
open /connect
We detect your location at the edge. No pickers, no questions, no permission popups.
ii
paste one line
Installs events × marble on your laptop, pulls marble's library, builds your knowledge graph from your data, and scores this week.
iii
your tab redirects
The dashboard is ready when the laptop says so. No URLs to copy. No tokens to paste.