---
typeId: req
recordId: benac-pkg-009
fields:
  title: Invocation contract identity
  statement: >-
    Benac shall define a stable invocation contract snapshot for use in approval,
    invocation, audit, storage, compute, evidence, and effect records.

    An invocation contract snapshot shall identify the exact schema-bound package
    contract relied upon for a package operation.

    An invocation contract snapshot shall include package CID, package interface
    identifier, request schema CID, descriptor config schema CID where relevant, output
    schema CID where relevant, descriptor snapshot CID or descriptor scope where
    relevant, declared capability identifiers relevant to the operation phase, artifact
    CIDs relevant to the operation phase, resource requirements relevant to the
    operation phase, evidence behavior, effect behavior, data class where relevant, and
    Local Policy context where relevant.

    An invocation contract snapshot shall not include a package class.

    An invocation contract snapshot shall not include package-work taxonomy fields.

    An invocation contract snapshot shall not include a field whose purpose is to
    classify how package work is performed.

    The invocation contract snapshot CID shall be the DASL CID of the DRISL-encoded
    invocation contract snapshot.

    Artifact CIDs and schema CIDs can be components of invocation contract identity, but
    shall not by themselves replace the invocation contract snapshot CID unless the
    schema explicitly defines a narrower snapshot rule.

    A Station shall not infer authority, trust, approval, invocation eligibility, or
    content validity from labels, names, filenames, provider names, product names, model
    names, repository names, URLs, or human-readable descriptions.
  rationale: Invocation, approval, trust, audit, storage, and compute records need to
    identify exactly which package interface, schemas, descriptor scope, artifacts,
    capabilities, resources, evidence behavior, and effect behavior were relied upon.
    This identity is a schema-bound operation contract, not a classification of package
    internals.
  verification: Multi-interface package fixtures produce deterministic invocation contract
    snapshot CIDs across Host Platforms. Changing request schema, descriptor config
    schema, output schema, descriptor scope, declared capabilities, artifact CIDs,
    resource requirements, evidence behavior, or effect behavior changes the invocation
    contract snapshot CID. Adding a class label is not required and does not produce a
    valid invocation contract snapshot.
  area: BENAC-PKG
  sourceSections:
    - Package model, descriptors, and package claims
  order: 82.5
  testable: true
  status: draft
  sourceDocument: user-requested schema-first requirements cleanup
  sourceVersion: 2026-05-06
---
