Semogram Docs
Reference

Assertions and evidence

Claims, assertion lifecycles, evidence links, and verification.

Where runs keep execution proof, assertions keep truth claims: checked statements about data and state, each with evidence, confidence, status, and review. Related: Runs and evidence.

Assertion types

TypeClaims aboutExample
EntityThat a thing exists as described"Acme is an enterprise account"
PropertyA field value"Order 8814 totals €4,200"
RelationshipA link between things"Acme placed order 8814"
ClassificationA label assignment"Ticket 991 is billing"
ClaimAnything else checkable"Churn risk exceeds threshold"

Assertion lifecycle

StatusMeaningNext
ProposedMachine-stated, uncheckedReview it
ApprovedHuman-confirmedUsable downstream
CorrectedFixed with reasonsSupersedes the proposal
RejectedRefused with reasonsDead, but recorded
SupersededReplaced by a newer revisionFollow the newer one

Review decisions

DecisionMeaning
ApprovedRight as stated
CorrectedFixed — the highest-value feedback
RejectedMisleading, with reasons

Claims and confidence

FieldMeaning
KindSource observation, extracted claim, human assertion, derived assessment
Subject / predicate / objectThe statement in triple form
Source reliabilityHow much the origin is trusted
Claim confidenceHow much the statement is trusted — stated separately from forecast probability
Match confidenceHow sure the entity linkage is
Forecast probabilityLikelihood, only with a separate claim confidence
Validity rangeWhen the claim holds true
{
  "claimKind": "extracted_claim",
  "subjectRef": "cust-acme",
  "predicate": "at_renewal_risk",
  "assertionType": "claim",
  "confidence": { "sourceReliability": 0.8, "claimConfidence": 0.7 },
  "evidence": [{ "captureId": "…", "relation": "supports" }]
}
RelationMeaningExample
SupportsEvidence backs the claimTicket thread showing outage complaints
ContradictsEvidence undermines itUsage actually grew 40%
RepeatsIndependent second sightingSame figure in the billing export

Selectors pinpoint the evidence: text spans with quotes, page regions, time ranges, or structured-data pointers — each hashed so tampering shows.

Verification and derivations

  • Verification tasks: named checks with instructions and stated limitations; findings record what was checked and concluded.
  • Derivations: how assertions and artifacts produce each other — recorded, so impact flows both ways when a source claim changes.
  • Corrections: merges, splits, reversals, and resolutions against expected revisions — identity teaches what "same" means here.

Image: claim with confidence bars, supporting and contradicting evidence, and its derivation trail.