---
typeId: req
recordId: benac-data-001
fields:
  title: Minimum logical data object CID fields
  statement: Benac shall define minimum logical data object schemas using CID
    terminology where exact content identity is required. The name_binding
    object shall associate a human-readable name with a CID or principal. The
    artifact_ref object shall reference a blob artifact with DASL CID, size,
    media type, encryption metadata if applicable, and availability metadata.
    The blob_manifest object shall describe structured or chunked blobs,
    including chunk CIDs and top-level content identity. The blob_location_claim
    object shall claim that a Storage Station or Peer Station may have a blob or
    chunk identified by CID. The invocation object shall record one package
    operation attempt, including package, descriptor, selected package interface, request,
    output, evidence, effect references, parent invocation references, and child
    invocation references by CID where applicable. The storage_lease_request object
    shall describe a requested storage authorization scope and shall not itself
    authorize storage effects. The compute_lease_request object shall describe a
    requested compute authorization scope and shall not itself authorize compute effects,
    data egress, storage staging, decryption, or plaintext disclosure. Causal reference
    fields shall link related records, actors, sessions, invocations, requests,
    approvals, evidence, effects, diagnostics, package drafts, package CIDs,
    invocation contract snapshot CIDs, descriptor snapshot CIDs, build reports, validation reports,
    and fixture results where applicable without granting authority. Mediated child
    invocation requests shall identify target package/interface/descriptor context,
    initiating package, parent invocation, requested data class, and granted scope where
    applicable. The storage_receipt object shall bind storage-operation evidence or
    claims to relevant operation, blob, chunk, request, or manifest CIDs where
    applicable.
  rationale: The logical data model must use the same CID vocabulary as the
    requirements so implementers do not fall back to ambiguous bare hashes.
  verification: Schema and conformance fixtures reject portable logical object
    records that use bare digest identity where these object definitions require
    CIDs.
  area: BENAC-DATA
  sourceSections:
    - 12. Minimum logical data objects
  order: 194
  testable: true
  status: draft
  sourceDocument: /home/johnb/Downloads/benac_syrs_v0_4_integrated_authentication.md
  sourceVersion: v0.4
---
