Proof center

Inspect a public usage receipt.

Start with a real public aggregate: what was counted, which provider rollups exist, what trust context cannot affect, and where the receipt was published. The bundled contract remains below for operators who need the complete scan-to-share specification.

Vibers UniteC0vibe.appNO FAKE PROOF

PUBLIC RECEIPT SOURCE@b-etterdigitalGITHUB VERIFIED

VTK://PUBLIC-RECEIPT//@b-etterdigital//AGGREGATE-ONLY

@b-etterdigital public receipt

Follow one published aggregate from counted operations through provider mix, score input, trust context, local review, and C0VIBE relay.

LIVE PUBLIC AGGREGATEUNRANKED

Snapshot fingerprint1EA944F0Deterministic ID, not a cryptographic signature

Evidence tierATTESTEDDeclared by the latest public upload

Counted operations65,120Aggregate rows only

Provider sources11Public provider rollup

Trust signals2Context only, never usage

Latest publish2026-07-15UTC calendar date

VERIFIER MATRIX

Decode what this receipt can actually claim.

CLAIM 01 / 04

PUBLIC VALUE65,120Aggregate rows only

PROVES: 65,120 accepted aggregate operations are present in the reviewed public payload.
READ FROM: reviewed public aggregate / record_count
DOES NOT PROVE: Prompts, files, token-level billing, effort, quality, or business outcome.

receipt@public1EA944F0

+------------------------------------------------------------+
| VTK://PUBLIC-BLACK-BOX//@b-etterdigital//C0VIBE.APP        |
| seal 1EA944F0 // reviewed aggregate live                   |
| records 65,120 // providers 11 // active days 331          |
| trust 2 NOT USAGE // rank impact 0                         |
| prompts 0 // outputs 0 // secrets 0 // raw files 0         |
| profile, heatgrid, score, and C0VIBE relay share stream    |
| Vibers Unite // public replay is aggregate-only            |
+------------------------------------------------------------+

Fingerprint is a deterministic public snapshot ID. It is not a cryptographic signature or independent attestation.

usage

Aggregate capture

usage counted

65,120 opslocal ledger -> reviewed upload

Feeds profile totals, score mass, and public spend estimate.

PUBLIC LINE: usage.records=65120; prompts=0; outputs=0
BOUNDARY: Only aggregate rows are replayed publicly.

USAGEaccepted aggregate rows can feed totals, score, provider mix, heatgrid, and spend estimates.

NOT USAGEGitHub and creator context is labelled separately and cannot change rank, spend, credits, or operations.

LOCAL ONLYprompts, outputs, secrets, pasted keys, and raw files stay off the public replay.

PUBLISHc0vibe.app receives only the reviewed aggregate stream after local approval.

Open the bundled proof contract

read this page as a contract

Blueprint, not your live receipt.

This page walks through the product contract with bundled fixtures. It proves how evidence is separated; it does not inspect this browser, your machine, or a provider account.

bundled fixture

no machine scanno account queryno upload

Proven by this contract

Usage receipts pass through an acceptance gate before public totals.
Local preview, trust context, and publish approval stay on separate rails.
The same reviewed aggregate can feed score, profile, heatgrid, and leaderboard.

Not proven on this page

No machine logs or provider credentials were read by this page.
No spend total, identity, signature, or publish approval belongs to you here.
No percentage below is product readiness or account verification.

Prove your own run

Audit the local receiptnpx vibetrack auditValidate source adapters, secret boundaries, and accepted records locally.
Preview what leavesnpx vibetrack upload --dry-runSee the redacted aggregate before any explicit publish step.
Explain every railnpx vibetrack auditPrint the usage, local-only, trust, and publish contract in the terminal.

VTK://DATASTREAM-SPINE//SCORE-PROFILE-PUBLISH//TRUST-SIDECAROne reviewed receipt, four honest surfaces

The visible contract: usage can feed public score/profile surfaces, local preview protects the machine, trust stays labelled as not usage, and C0VIBE publish remains explicit.

spine@proof89% FIXTURE

VTK DATASTREAM SPINE // SAME RECEIPT
$ npx vibetrack audit
[usage] accepted aggregates -> score/profile/heatgrid
[local] dry-run preview -> 0 hidden uploads
[trust] sidecar context -> +0 usage writes
[relay] c0vibe.app -> reviewed publish only
motto: Vibers Unite

score feeds from usageprofile feeds from receipttrust is not usagec0vibe.app

USAGEReviewed usage receipt

USAGE 
RECEIPT
SEALED

SCORE 
PROFILE
BOARD

1 usage gatenpx vibetrack sync --receipt

Score, heatgrid, profile, and leaderboard read the same accepted aggregate receipt.

LOCAL ONLYMachine boundary

LOCAL 
DRYRUN
FIRST

0 RAW 
PROMPT
SHIP

0 hidden uploadsnpx vibetrack upload --dry-run

The preview is visible before relay; raw prompts, files, secrets, and private paths stay blocked.

NOT USAGETrust sidecar

TRUST 
SIDE  
CAR

HIGGS 
MCP +0
USAGE

0 usage writesnpx vibetrack trust list

GitHub, Higgsfield MCP, creator cadence, and package signals explain credibility without changing spend.

PUBLISHC0VIBE relay

C0VIBE
.APP  
RELAY

VIBERS
UNITE 
LIVE

1 publish gatenpx vibetrack upload

c0vibe.app receives reviewed aggregates plus labelled trust context only after the user approves publish.

VTK://PROOF-CENTER//LOCAL-FIRST//NO-FAKE-PROOF//NO-HIDDEN-UPLOADSFAST / HONEST / TRACEABLE

proof@localTRACEABLE

$ npx vibetrack sync --demo
[scan] Higgsfield prism -> local ledger
[scan] Codex builder trace -> local ledger
[gate] schema ok / secrets rejected
[trust] GitHub cadence == NOT USAGE
[relay] Vibers Unite // c0vibe.app

Vibers Unitec0vibe.appdry-run first

 HF  CX 
<=SCAN=>
 LM  UI

SCAN

Provider scanUSAGEnpx vibetrack sync

Adapters read usage receipts into the local ledger; provider failures show recovery instead of silence.

 [OK]  
  ||   
[DROP]

CHECK

Ingest gateUSAGEschema + secret scan

Records are normalized, schema checked, and secret-shaped fields are rejected before upload.

MASK **
LOCAL  
DRYRUN

LOCAL

Privacy previewLOCAL ONLYnpx vibetrack upload --dry-run

The dry-run preview shows what would leave the machine and keeps prompts, files, and secrets out.

GIT YT 
!= $$$ 
SIGNAL

SIDE

Trust railNOT USAGEnpx vibetrack trust list

GitHub, Higgsfield MCP, YouTube, packages, and creator cadence are labelled NOT USAGE and never change spend.

C0VIBE
APP >>
UNITE

RELAY

C0VIBE relayPUBLISHnpx vibetrack upload

Only reviewed aggregate usage and explicit trust signals can feed c0vibe.app.

No prompt/content uploadUsage records stay about provider, cost, tokens, ops, and source proof.

Trust never changes spendGitHub and creator cadence are public context, not usage totals.

Verified and self-reported stay splitLeaderboards do not blend backend-fetched and user-entered evidence.

Provider errors are visibleBroken OAuth, missing CLIs, and stale tokens get fix paths, not fake data.

VTK://PROOF-BRIDGE//OPERATOR-QUESTIONS//ZERO-HIDDEN-UPLOADSVerification bridge

The operator-facing handoff between local proof and public profile: every gate answers what counts, what leaves, what is not usage, and when C0VIBE updates.

bridge@proof89% FIXTURE

+--------------------------------------------------------------+
| VTK://PROOF-BRIDGE//OPERATOR-QUESTIONS//ZERO-HIDDEN          |
|--------------------------------------------------------------|
| what counts -> validated provider usage only                 |
| what leaves -> dry-run aggregate after review                |
| trust proof -> NOT USAGE sidecar with 0 usage writes         |
| Vibers Unite // c0vibe.app // explicit publish               |
+--------------------------------------------------------------+

1 usage gate1 local gate1 not usage0 trust usage writes0 hidden uploads

USAGEUsage seal

USAGE 
SEAL  
OK

SCHEMA
PASS  
COUNT

BAD   
DROP  
SAFE

What counts?

Only validated provider receipts become usage totals.

npx vibetrack ledger verifyaccepted aggregates only

schema passadapter sourcerankable aggregate

LOCAL FIRSTMachine boundary

LOCAL 
FIRST 
GATE

DRYRUN
VIEW  
ONLY

0 HIDE
UPLOAD
FOUND

What leaves?

The dry-run preview shows the aggregate payload before upload.

npx vibetrack upload --dry-run0 hidden uploads

redaction previewsecret scanreview before relay

NOT USAGETrust split

TRUST 
SIDE  
CAR

HIGGS 
MCP   
+0USE

GITHUB
HEAT  
+0RANK

What is proof context?

GitHub, Higgsfield MCP, creator, package, and social signals stay in a sidecar.

npx vibetrack trust list0 usage writes

NOT USAGE+0 scoreseparate public label

PUBLISHC0VIBE relay

C0VIBE
RELAY 
READY

PROFILE
SCORE 
BOARD

VIBERS
UNITE 
LIVE

When public?

Only explicit reviewed upload feeds the profile, score, badges, and board.

npx vibetrack uploadreviewed publish only

explicit publishtier visiblesame receipt

VTK://BLACK-BOX//CUSTODY//NO-RAW-PROMPTS//0-HIDDEN-UPLOADSUSAGE + TRUST + PRIVACY + PUBLISH

custody@localBUNDLED

VTK BLACK BOX // LOCAL FIRST
01 capture receipts -> schema gate
02 dry-run review -> redaction preview
03 trust sidecar -> NOT USAGE labels
04 C0VIBE relay -> reviewed aggregates only
status: NO RAW PROMPTS / 0 hidden uploads / NO FAKE PROOF
motto: Vibers Unite // c0vibe.app

NO RAW PROMPTS0 hidden uploadsNOT USAGE labelsVibers Unitec0vibe.app

USAGEProvider receipts

  HF  
 H  F 
  HF

 CODEX
 >_ OK
 TRACE

 LM/O 
 LOCAL
 READY

Usage enters as receipts, never vibesnpx vibetrack sync --receipt

Tokens, credits, generations, model IDs, and cost evidence can count only after adapter validation.

adapter sourceschema passtimestamped

LOCAL FIRSTReview vault

DRYRUN
ONLY  
LOCAL

NO RAW
PROMPT
UPLOAD

0 HIDE
UPLOAD
FOUND

The machine shows the payload firstnpx vibetrack upload --dry-run

The dry run labels raw prompts, files, secrets, and private paths as blocked before C0VIBE relay.

NO RAW PROMPTS0 hidden uploadsredaction preview

TRUSTSignal sidecar

TRUST 
!=USE 
SIDE

 GIT  
 HEAT 
 GRID

HIGGS 
 MCP  
SIGNAL

Public proof stays separate from usagenpx vibetrack trust list

GitHub heatgrids, Higgsfield MCP, YouTube cadence, and package publishing are useful trust signals, not spend.

NOT USAGEseparate railscore labelled

PUBLISHC0VIBE datastream

C0VIBE
 .APP 
RELAY

VIBERS
UNITE 
READY

PUBLIC
PROOF 
TIERS

Reviewed aggregate proof can go publicnpx vibetrack upload

The user profile, vibe score, and public badges read from reviewed aggregates plus clearly labelled trust signals.

explicit publishtier splitprofile feed

VTK://PROOF-REPLAY//TAMPER-EVIDENT//LOCAL-FIRST//NOT-USAGE-SIDECARTamper-evident replay

A compact proof recorder that shows every scan-to-profile handoff, what was sealed, and which rails are usage, local-only, trust sidecar, or public relay.

replay@proof5 EVENTS

+--------------------------------------------------------------+
| VTK://PROOF-REPLAY//TAMPER-EVIDENT//LOCAL-FIRST              |
|--------------------------------------------------------------|
| events 5    sealed 2    avg proof 89%                        |
| capture verify redact sidecar relay                          |
| trust sidecars are NOT USAGE and never mutate rank           |
| Vibers Unite // c0vibe.app // reviewed aggregates            |
+--------------------------------------------------------------+

2 sealed1 local1 not usage1 publish89% fixture

CAPTURE

Provider receipt packetSEALED

HF/CX
RCPT 
SEALED

TOKENS
COSTS 
MODELS

SRC OK
TIME  
UNIT

npx vibetrack sync --receiptusage ledger intake

Provider records enter as timestamped receipts with adapter, unit, model, and confidence labels.

sha256:8f3a-vtk-capture

HFCXLM

VERIFY

Schema sealSEALED

SCHEMA
 PASS 
SEAL

SECRET
SCAN  
CLEAN

BADKEY
DROP  
SAFE

npx vibetrack ledger verifynormalizer + secret scanner

Records are normalized, bounded, and rejected when hostile keys, secret-shaped values, or fake tiers appear.

sha256:2c91-schema-ok

OKNODROP

REDACT

Dry-run payload previewLOCAL

LOCAL 
ONLY  
MASK

0 RAW 
PROMPT
SHIP

DRYRUN
BEFORE
RELAY

npx vibetrack upload --dry-runlocal-only review vault

The user sees the outbound aggregate first; prompts, files, secrets, and private paths stay on-machine.

sha256:77bd-local-mask

DRY0RAWMASK

SIDECAR

Trust sidecar attachNOT USAGE

TRUST 
SIDE  
CAR

HIGGS 
MCP   
LABEL

NOT   
USAGE 
RANK

npx vibetrack trust listgithub + creator + mcp context

GitHub cadence, Higgsfield MCP, creator posting, package signals, and profile links stay separate from spend.

sha256:5aa0-sidecar-nu

GHHFYT

RELAY

C0VIBE profile feedREADY

C0VIBE
 .APP 
FEED

VIBERS
UNITE 
LIVE

PUBLIC
TIERS 
CLEAR

npx vibetrack uploadreviewed aggregate datastream

The vibe score, public profile, badges, and leaderboard consume reviewed aggregates plus labelled trust context.

sha256:c0vibe-profile-feed

C0VSPUB