Point
Evidence bounds maturity claims
Normative, implemented, demonstrated, intended, open, and historical statements remain explicit so one kind of evidence cannot impersonate another.
- Posture
- asserted
- Lifecycle
- active
The current specification can establish what conforming data and processors must do. A complete valid resolved result establishes format validity for that revision. A Check pass from the Meta-Atlas evaluator establishes only the recorded project-policy requirements for its baseline, change set, subjects, evaluator, and evidence. Neither result establishes semantic truth, completeness, usefulness, or product value beyond those explicit claims.
Code and tests can establish current implementation behavior. Independent agreement can establish a bounded interoperability result. Atlas Portal establishes implemented reader behavior without establishing publication hardening or reader benefit. A plan establishes intended scope, while open questions and history establish neither current behavior nor product benefit.
Every Meta-Atlas record therefore declares an x-claim-basis and uses standard posture and lifecycle independently. Release prose and checks must preserve those distinctions. Passing a protocol, registering a Resource, or writing detailed acceptance criteria cannot be described as a completed user outcome.
Claim disciplineClaim-basis classification and standard posture and lifecycle keep contract, implementation, evidence, intent, and history from collapsing.
Every conclusion must name whether it rests on contract text, implementation inspection, executable evidence, intended design, open inquiry, or consequential history.
The evidence register states both established and unsupported claims. A later result should identify its corpus, revision, participants, tool build, control, task, and limitation so readers can decide which Point posture or lifecycle the result can legitimately change.
Conformance evidenceContract text and executable comparisons support format and processor claims only within their tested scope.
Product evidenceProduct conclusions require observed task outcomes, not structural validity or self-hosting.
Learning agendaExplicit claim basis shows which unanswered questions can legitimately change as new evidence arrives.