01 local first
No raw Claude Code session data leaves your machine.
The reveal runs locally. Publishing sends bounded derived metrics only. No free-text goals or friction leave device.
version 1 promises
Proof without surveillance.
Vibestats turns local Claude Code behavior into a GitHub-claimed build profile. The card is shareable because the boundary is strict: raw sessions stay local, public profiles are derived-only, and discovery is opt-in.
Raw Claude Code sessions stay local.
Prompts, session summaries, project paths, session ids, tool maps, language maps, and free-text friction do not sync.
Only derived metrics sync.
Saved profiles store archetype, scores, coarse metrics, signature, badges, and bounded match-intro/outcome events.
Owned by the builder
Profiles start unlisted. They are GitHub-claimed, exportable, deletable, and use revocable CLI tokens.
02 opt-in discovery
Public visibility is a choice.
Saved profiles start unlisted. Browse, leaderboard, match, and contact links require explicit public opt-in from the owner.
03 no ranking trap
No single hireable score.
Vibestats describes build style, rarity, trajectory, and fit. No employer people search, and no employer-searchable rank.
04 bounded graph
Match feedback starts with safe aggregates.
Intro intent records goal, archetypes, target handle, source, and action. It does not store message text, contact URLs, IP address, or headers.
05 delete means leave
Delete means leave.
Settings includes export and account deletion. Local-only reveal remains valid for people who never want a persistent profile.
06 stable canon
The eight archetypes stay stable.
Rarity grows through signatures, facets, achievements, and trajectory. We do not add noisy archetypes that break scoring and sharing.
The short version
Vibestats should be useful because it is narrow and falsifiable: "this is how I build, this is how rare it is, this is how we might pair." It should never become a developer credit score, employer search database, or raw telemetry sink.