Section 68 of 105
66. Capability Declaration and Negotiation
Stable section ID: S05-CON-014-SECTION-68 · 19 content blocks
Assets connected through capable System05 Interfaces shall declare the capabilities necessary for safe and compatible operation.
Capability declarations may include:
- Identity and asset class.
- Interface version.
- Supported functions.
- Structural or operational capacity.
- Voltage, pressure, flow, temperature, or data limits.
- Required resources.
- Current condition and state.
- Safety restrictions.
- Maintenance status.
- Optional features.
- Known limitations.
- Authorization level.
Capability negotiation may occur through physical keying, markings, configuration records, digital exchange, or a combination of methods.
The negotiated result shall not exceed the verified capability of the least-capable participating asset.
Optional capability shall not become an undeclared requirement for mandatory functions. A legacy asset that supports the required minimum capability should remain operable when continued compatibility has been approved.
Safety-critical compatibility shall not depend solely on an uncertain network connection, unavailable cloud service, unverified sensor, or AI inference.
Incomplete, contradictory, unauthenticated, or unavailable capability information shall cause the Interface to enter an appropriate safe or restricted state.