Trust is a system, not a badge.
Release history, evidence levels, source and license boundaries, validation notes, known limitations, and corrections are published together so a reader can see what was checked — and what was not.
A claim travels with its boundary.
A build, local functional check, synthetic example, independent replay, and field validation are different states. We label them separately and do not promote one state into another without a dated record.
One shared vocabulary for public claims.
| Level | Meaning | Permitted wording |
|---|---|---|
| E0 · Concept | Architecture or workflow proposal; no functional run | Concept, proposed, illustrative |
| E1 · Sourced | Primary or official source mapped to the claim | Documented, source-mapped |
| E2 · Local check | Local build or deterministic functional check recorded | Locally checked under stated conditions |
| E3 · Reproducible | Public package, inputs, steps, and expected output available | Reproducible package published |
| E4 · Independent replay | A named external party replayed the procedure | Independently replayed, with scope |
| E5 · Field or authority validation | Field trial or authority acceptance with dated evidence | Field-validated only within recorded scope |
Inspect the evidence chain.
- Dated change historyP0
Updates
Material releases and policy changes, without synthetic activity entries.
Detail → - Evidence and release gatesP0
Methodology
How claims, builds, checks, and corrections move through review.
Detail → - Provenance boundariesP0
Sources & Licenses
Upstream sources, licenses, and what UAM Korea Tech authored.
Detail → - Comparable checks onlyP1
Benchmarks
Published quality gates and the benchmarks we have not yet run.
Detail → - Checked vs not checkedP1
Validation Notes
Release-level verification records and their exact scope.
Detail → - Stop before overclaimP1
Known Limitations
Public limitations for browser tools, data, compliance, and field use.
Detail → - Now, next, laterP1
Roadmap
Planned evidence upgrades; not promises of delivery or performance.
Detail → - Issue and evidence intakeP1
Contribute
How to report a defect, propose a test, or contribute documentation.
Detail → - Input and retention mapP2
Data Provenance
Where public tool inputs originate and where processing occurs.
Detail →
Publication, source mapping, and local checks are not certification, endorsement, legal advice, operational approval, or a warranty of field performance. Each release record states the narrower claim it supports.