Independent verification for AI-built apps
The seal, and the register it points to.
Every VulX verification is a numbered entry in a public register. The badge is the seal stamped on the app; the page it links to is the live record. Synthetic records below — verified, under review, not verified, expired, revoked — and the page a stranger finds when a badge lies.
FIG. 01Badge — pill
FIG. 02Badge — card
FIG. 03In situ
The badge keeps its own exposure on any host — the plate and hairline border read as a struck seal, not a themed component. Click any badge to open the record it points to.
FIG. 04Embed code
FIG. 05Badge — states
The badge renders the register’s current state, not the builder’s claim — a builder can remove the badge, but can’t make it lie. Green leaves the seal the moment a verification lapses; a revoked seal is struck through in ink. Red never means status.
FIG. 06The register
Each record is the public page its badge links to — badge and page can’t disagree because they read the same entry. Open the full register → · Follow a forged badge’s link to see what a stranger finds →
FIG. 07The certificate
The formal document view of a record — framed plate, print-ready (⌘P saves a PDF on the bone exposure). Open ShareSpace’s certificate → · see a voided certificate →. A certificate of a lapsed record is stamped VOID: validity lives on the register, not on paper.
FIG. 08The method
Where “didn’t grade their own homework” gets its full argument — independence, the three finding tiers, the scope, the seal’s lifecycle, and what verification is not. Read the method →
FIG. 09The builder profile
One shareable page listing all of a builder’s registered apps — the register filtered to one name, honest posture included. Open Fieldnote Labs’ profile → · a single-app builder → · no profile exists →