Evidence and claim taxonomy
Separate a design contract, an implementation, its evidence, and a publication claim.
PLLM documentationView Markdown ↗
| Axis | Meaning |
|---|---|
| Normative contract | Intended invariant; not implementation proof |
| Semantic adapter support | Model configuration lowers to neutral semantics |
| Compiler coverage | Named profile covers reported operators |
| Runtime support | Locked plan executes in tested implementation scope |
| Benchmark evidence | Measurements bound to environment, workload, and cohort |
| Generation quality | Predeclared output-quality result for model/workload |
| Privacy evidence | Scoped formal or empirical assurance result |
| Deployment maturity | Tested placement, authentication, recovery, and operations scope |
| Source-reported claim | Original publication statement, not PLLM result |
| Reproduction fidelity | Match to locked source/oracle in recorded scope |
Unknown is never zero or pass. Every claim links exact artifact, date/version, cohort, limitations, and applicable assurance. Use research evidence records to inspect those scopes and limitations before repeating a claim.