v2 Beta · Integration preview
Assessment and review
State which checks ran and what their results mean.
The beta includes versioned profiles, policies, evaluation receipts and reproducible assessment summaries. Their purpose is to make the basis of an assessment inspectable.
Four distinct questions
- Structural: Does the document match its declared contract?
- Semantic: Are relationships within the supplied documents consistent?
- Profile: Does it meet a specific profile's requirements?
- External: Which supplied artifacts or outside facts were checked, and within what scope?
Do not display an unrun check as passed. A valid record can still lack the information needed for a research conclusion.
Vocabulary and attributed assessments
Technology and biologics observable definitions describe reported characteristics. The Origin Classification System (OCS) organizes possible explanations. These vocabularies do not establish that a characteristic occurred or that a proposed explanation is correct.
The OCS adapts Col. Karl Nell’s proposed taxonomy of UAP origin hypotheses. The Origins explorer retains its framework attribution.
Use claim histories to record an assessment with its author, method, inputs and reasoning. Evaluate the relevant documentation and instrument profiles separately. The worked example shows why a passed measurement binding profile still leaves scientific review unperformed.
Read external checks within their profile
The document, testimony and physical-sample evaluators can return external: passed for matching selected source bytes. Release, speaker and custody authenticity remain explicitly unchecked. External status alone does not establish independent review or scientific validity. The provenance examples show these outcomes alongside every remaining interpretation limit.