---
typeId: req
recordId: benac-pkg-003
fields:
  title: Package document schema
  statement: >-
    Benac shall define a versioned package document schema.

    A package document schema shall be closed by default.

    A Host Implementation shall reject unknown required package document fields.

    A Host Implementation shall reject unknown required package interface fields.

    The package document schema shall include stable fields for package document
    version, package metadata, schemas, schema ruleset identifiers, package interfaces,
    request schema references, descriptor config schema references, output schema
    references, declared capabilities, artifact references, resource requirements,
    fixtures, documentation references, storage needs, compute needs, evidence behavior,
    and effect behavior.

    The package document schema shall not include a field whose purpose is to assign the
    package to a named package class.

    The package document schema shall not include a field whose purpose is to classify
    how package work is performed.

    The package document schema shall not include a field whose purpose is to pre-decide
    operation eligibility.

    The package document schema shall not include a field whose purpose is to classify
    unsupported behavior.

    A package document shall remain content-valid when the current Station cannot
    currently mediate an operation requested by a package interface, unless that
    operation is required for package import or package validation.

    A package document shall remain content-valid when Local Policy has not granted a
    capability required only for approval, fixture execution, invocation,
    package-requested effects, retrieval, storage, or compute.

    A package document shall remain content-valid when an artifact required only for
    approval, fixture execution, invocation, package-requested effects, retrieval,
    storage, or compute is unavailable.

    A Host Implementation shall record those conditions by operation phase.
  rationale: Independent implementations need compatible package document interpretation
    and fail-closed handling for fields they do not understand. Package content validity
    is separate from Local Policy, artifact availability, resource availability, and
    current Station ability to mediate an operation.
  verification: Unknown required field fixtures fail validation. Valid package documents
    for greeting, calculator, todo reducer, notes reducer, schema-bound behavior, and
    multi-interface packages validate consistently across conforming implementations. A
    package document containing a retired class field fails validation. A package whose
    requested invocation operation is not currently mediated by the validating Station
    remains content-valid when import and validation requirements are otherwise
    satisfied.
  testable: true
  status: draft
  area: BENAC-PKG
  sourceDocument: user-requested schema-first requirements cleanup
  sourceVersion: 2026-05-06
  sourceSections:
    - Package model, descriptors, and package claims
  order: 77
---
