---
typeId: req
recordId: benac-sys-004
fields:
  title: Station profile publication
  statement: >-
    Each Benac Station shall publish a machine-readable Station Profile describing known
    Station information useful for planning, inspection, diagnostics, conformance, and
    user review.


    A Station Profile shall describe Host Platform, Host Implementation, Host artifact
    or Host version where available, known Benac semantic interfaces, known package
    document versions, known schema rulesets, known artifact availability mechanisms,
    known fixture execution behavior, known package inspection behavior, known package
    approval behavior, known capability identifiers the Station can mediate where known,
    known authentication features, known cryptographic features, known replication
    features, known storage features, known compute features, known calling conventions,
    and conservative policy-relevant constraints.


    A Station Profile shall publish known package-authoring and operation limits where
    known, including maximum package document size, Package Bundle size, schema size,
    fixture size, artifact size, request size, descriptor config size, output size,
    memory, operation time or fuel policy, log size, evidence record size, and effect
    record size.


    A Station Profile shall not be treated as a complete list of everything the Host
    Platform can do.


    A Station Profile shall not be treated as proof that a requested capability is
    currently available.


    A Station Profile shall not be treated as proof that a requested operation will
    succeed.


    A Station Profile shall not be treated as proof that required artifacts, physical
    resources, external services, platform permissions, network connectivity, storage
    offers, compute offers, authentication state, or Local Policy grants are currently
    available.


    A Station Profile shall not be treated as approval.


    A Station Profile shall not be treated as a capability grant.


    A Station can update known status after inspection, Local Policy decisions, allowed
    probes, allowed attempts, platform permission decisions, resource checks, artifact
    checks, failures, or completed operations.


    A Station Profile shall not classify packages.


    A Station Profile shall not classify how package work is performed.
  rationale: Agents, users, and package authors need a starting map for planning and
    review, but actual use is governed by Local Policy, capability grants, leases,
    offers, allowed probes, allowed attempts, conformance traces, and failure records.
  verification: Validate the Station Profile schema. Conformance tests inspect the profile
    for known Station information and published limits, then verify behavior through
    inspection, package approval, invocation, evidence, effect, and failure records.
    Tests verify that Station Profile information does not grant authority and does not
    prove current resource availability.
  testable: true
  status: draft
  area: BENAC-SYS
  sourceDocument: user-requested schema-first requirements cleanup
  sourceVersion: 2026-05-06
  sourceSections:
    - Host neutrality and platform coverage
  order: 34
---
