§ 404 · PRINTER STATUS

Paper jam.

That page is not in this ledger.

Return to the counter ↗
Receipts · Midnight / Cobalt / Lime Component docket Return to the letterhead →
§ 00
TYPE & STOCK

The reveal is the interface.

A working component sheet for the Midnight · Cobalt · Lime. The receipt below is rendered from the first saved vault record; its state and barcode come from that record.

§ 01
INKS

Midnight, cobalt, lime

black · base
black-2 · surface
black-3 · raised
paper · receipt stock
text · foreground
cobalt · structure
cobalt-soft · small text
lime · active
danger · destructive
§ 02
TYPE

Bricolage, Instrument Sans, IBM Plex Mono.

Your AI remembers.
Receipts proves it.
Instrument Sans · The source stays beside the remembered fact.
IBM PLEX MONO · REC-ASYNC1 · 091% · 00:01.4
§ 03
STAMP PAD

States are printed, not colored alone.

FreshFadingStale SupersededVerifiedForgottenQuarantined
§ 04
CONTROLS

Buttons, double ink focus, and disabled state.

§ 05
SPECIMEN

Receipt card · real saved record

Warming the printer…

§ 06
LEDGER ROW

Dotted leaders keep the columns aligned.

REC-—Waiting for the saved record ·········—%—
§ 07
REVEAL

Hidden provenance on a black surface.

§ 08
PRINTER

Metadata belongs at the foot.

Bricolage Grotesque, Instrument Sans and IBM Plex Mono are self-hosted under static/fonts/ with their OFL notices.

RECEIPTS
← Home
§ 01 · CHAT

Ask, then verify.

Ask what the vault remembers. Read the source behind each answer.

Sovereign Assistant Nebius / NVIDIA Nemotron
Hello Hari. I am Receipts, your sovereign memory layer. Ask a question to see the answer and the receipts behind it.
Receipts Engine • Local First
YOUR MEMORY, WITH RECEIPTS

What would you like to remember?

Start with a question. You can inspect the source behind every cited memory.

§ 02 · VAULT

Every fact. Its source. Its clock.

Open a record to inspect provenance, confidence and review history.

All memories live exclusively in your local SQLite database (./data/vault.db). Nebius and NVIDIA Nemotron only see minimal context on-demand.
Sovereign healthFreshness weighted
Total receipts0Stored locally
Fresh0Recently confirmed
Decaying0Review when useful
Stale0Needs confirmation
CATEGORY:
STATUS:
§ 03 · GRAPH

Relationships have receipts.

Explore relationships derived from saved receipts.

Not your data · uses saved half-life categories
§ 04 · COPILOT

The audit desk.

Review stale and conflicting records with their evidence in view.

100% Health Score

Sovereign Vault Health

Calculated in real-time by weighting active fresh facts against decaying and stale memories.

Fresh: 0
Decaying: 0
Stale: 0
SUGGESTION ENGINE

Configured provider or local rules

Recommendations use the configured model when available and local rules as a fallback. Each result shows its generating source.

Proactive Staleness Alerts

Auto-flagged by exponential decay curves

Focus an alert card, then press R Reaffirm, C Correct, or F Forget. Forget asks you to confirm.

Maintenance Recommendations

Suggestion source: waiting for analysis
§ 05 · TOUR

Inspect the system.

Walk through the current receipt, vault, graph and provider checks.

SOVEREIGNTY WALKTHROUGH

Run an inspection step to open the related receipt or tool. Provider checks show when an API key is needed.

Checks navigate the existing local demo. Nothing is saved until you confirm an edit or export.

STEP 1 • PROVENANCE REASONING

1. Query Assistant on Sprint Planning

Ask how sprint meetings should be scheduled. The current response may use live Nebius inference or the clearly labelled local fallback.

Prompt: "How should we schedule the sprint planning meeting?"
STEP 2 • AUDIT RECEIPT CARD

2. Inspect the Receipt Card

Examine the receipt for REC-ASYNC1, including its stored email excerpt, displayed confidence, and configured half-life.

Receipt: REC-ASYNC1 • Email Thread: Q4 Sprint Cadence
STEP 3 • SOVEREIGN USER CORRECTION & CONFLICT CHECK

3. Live Correct the Memory

Change your preference from async to: "User now prefers live 15-minute morning syncs over async communication." Watch the audit trail capture your edit with timestamps.

Correction: Update preference & reset confidence clock.
STEP 4 • VERIFY SYSTEM REFLECTS CHANGE

4. Re-Query Assistant

Ask the same question again and inspect the result. The response depends on provider availability and the selected receipt context.

Re-test: Assistant answers with updated fact and cited receipt.
STEP 5 • TAVILY SOURCE VERIFICATION

5. Verify Web Source via Tavily

Run a live verification on REC-NEMO3. Tavily checks the live URL to confirm the excerpt is intact and flags if content drift has occurred.

Target: REC-NEMO3 (Nebius Token Factory Model Directory)
STEP 6 • ENCRYPTED CROSS-DEVICE SYNC

6. Export AES-256-GCM Encrypted Vault

Export a copy of the local vault encrypted with a passphrase using AES-256-GCM and PBKDF2 (100,000 iterations).

Action: Open Encrypted Sync modal to export or import.