← API reference
CANONICAL TYPE REFERENCE

RecordRequirementEvidenceInput

Record or correct a version-linked typed fact

requirement; explicit scope and evidence, never lifecycle permission

plannedDeliveryItemId; explicit scope and evidence, never lifecycle permission

observation; explicit scope and evidence, never lifecycle permission

completeBoolean!

Whether this fact covers all of the addressed scope; matching partial evidence cannot prove satisfaction

occurredAt; explicit scope and evidence, never lifecycle permission

attribution; explicit scope and evidence, never lifecycle permission

requestKeyString!

requestKey; explicit scope and evidence, never lifecycle permission

correctsEvidenceId; explicit scope and evidence, never lifecycle permission

reasonString

reason; explicit scope and evidence, never lifecycle permission

View exact SDL
"""Record or correct a version-linked typed fact"""
input RecordRequirementEvidenceInput {
  """requirement; explicit scope and evidence, never lifecycle permission"""
  requirement: RequirementReferenceInput!
  """
  plannedDeliveryItemId; explicit scope and evidence, never lifecycle permission
  """
  plannedDeliveryItemId: PlannedDeliveryItemID
  """observation; explicit scope and evidence, never lifecycle permission"""
  observation: RequirementObservationInput!
  """
  Whether this fact covers all of the addressed scope; matching partial evidence cannot prove satisfaction
  """
  complete: Boolean!
  """occurredAt; explicit scope and evidence, never lifecycle permission"""
  occurredAt: DeliveryTimeInput
  """attribution; explicit scope and evidence, never lifecycle permission"""
  attribution: RequirementAttributionInput
  """requestKey; explicit scope and evidence, never lifecycle permission"""
  requestKey: String!
  """
  correctsEvidenceId; explicit scope and evidence, never lifecycle permission
  """
  correctsEvidenceId: RequirementEvidenceIDSpecTypedID
  """reason; explicit scope and evidence, never lifecycle permission"""
  reason: String
}

One stable address across all schema views. Follow a field’s type to explore connections between domains.