One record out.
Every card starts with a source. The source determines the verification tier. The tier determines the badge. The record is yours regardless.
Some cards are built for you. AuditForge builds your Audit Card automatically — every completed engagement, every control signed off, every hour logged goes into the schema without you touching anything. The card is a read view of your work, not a form you fill out.
Link a third-party account and the platform reads your data directly. Ticketmaster purchase history. A state license board lookup by license number. An employer verification API. The connection is the proof.
Email a confirmation, certificate, or official document to your Ledger inbox. The system parses it — event name, date, issuer, credential type. Supported at launch: ticket confirmations, course certificates, professional licenses. Parser rules live in an editable table — adding a new document type is a config change, not a deploy.
Type it in. Name, date, what happened. No photo, no receipt, no connection. Pure memory and honest record-keeping. ‘I taught 94 students over 9 years. I don’t have a governing body. But I was there.’ That’s enough. The record accepts it.
Self-reported cards are first-class citizens. No penalty, no visual downgrade, just clearly labeled. The badge says Self-reported, not Sorry.
Photograph a physical document, ticket stub, certificate, or boarding pass. Claude Vision API reads the image — extracts name, date, issuer, credential type, and any barcode text. The system pre-fills the card form with extracted data. You confirm or correct.
If the OCR extraction matches a known issuer or event record, it lands as High Confidence. If no match, it lands as Self-reported with the OCR data attached — still richer than a blank manual entry.
The input changes. The record doesn’t.
Photo, connection, document, keyboard, vertical — five doors into the same room. Every card lands in the same schema, gets the same privacy controls, surfaces the same way in your Stack. The method of entry is metadata. The record is permanent.
Data came from a known, structured source — a vertical, an account connection, or a verified document issuer. The system can trace the data back to its origin.
Data was extracted via OCR or matched against a public record. The match is strong but not a direct API handshake. The system did the work — you confirmed it.
You entered it. No external source. Clearly labeled, never penalized. The record of what you showed up for is yours to keep regardless of what receipts you held onto.