Claims with their boundaries visible

How records are assembled

A versioned adapter reads the captured app metadata formats, preserves existing raw metadata URLs, and emits a separate normalized public registry. Unknown source license, language, storage or configuration remains unknown. The public export excludes private repository paths and internal release reports.

Each evidence inspector links to the exact public overview, runtime, metadata and notices when available. The observation date is a capture date, not an invented app release date. A public page is evidence of a published claim; it does not establish that every implementation was inspected.

Deterministic discovery

Search uses case and accent normalization, literal matches, a short curated synonym list, then a maximum one-character edit for terms of four or more characters. Every query term must match. Capabilities are tags derived from published wording with an inspectable rule and evidence link. No query is sent to an AI or analytics service.

What the visuals mean

The four-layer 2.5D object illustrates device/origin, model assumptions, published evidence and human review. Motion is optional. The workflow demonstrator is a bounded local simulation: no external agent executes, no engineering test is performed and no approval is granted.

What testing can establish

Build and browser checks can establish routes, interactions, markup and observed example results for a particular revision and environment. Lab performance measurements do not establish field INP or a field Core Web Vitals pass. Automated accessibility checks are partial evidence, not WCAG certification. Private backend and physical-device coverage require separate proof.

Medical, financial and engineering examples are educational demonstrations. Their app-specific limits stay next to their launch links.