Section 7 of 83
6. Interface Responsibilities
Stable section ID: S05-CON-005-SECTION-7 · 10 content blocks
Every interface shall assign responsibilities to the participating components and relevant lifecycle actors.
Component responsibilities shall include the capabilities, services, resources, protections, and information that each side is required to provide. These responsibilities shall be sufficiently explicit to prevent conflicting assumptions between independent manufacturers.
The provider side of an interface shall declare what it makes available. This may include structural capacity, electrical power, fluid supply, communication access, environmental protection, physical support, alignment, control authority, or digital services.
The consumer side shall declare what it requires and the conditions under which it can operate safely. It shall not demand resources, forces, permissions, environmental conditions, or performance beyond the limits established by the interface contract.
Where both sides provide and consume capabilities, the interface shall be treated as bidirectional. Responsibilities shall be defined separately for each exchanged function.
The interface designer shall be responsible for establishing the coordinated requirements governing interaction. The component manufacturer shall be responsible for demonstrating that the product conforms to the applicable side of the interface. The installer shall be responsible for correct assembly and verification. The inspector or commissioning authority shall confirm required evidence. The operator shall preserve permitted operating conditions. The maintainer shall follow approved procedures. The platform governance system shall control specifications, versions, compatibility classes, and certification rules.
Responsibility shall also be assigned for abnormal conditions. The interface contract shall determine which component detects a fault, which component communicates it, which component initiates isolation, which authority may override operation, and how recovery may occur.
No safety-critical responsibility shall remain implicitly shared. If multiple components participate in a protective function, their individual duties and collective behavior shall be defined and verifiable.
Where responsibility depends upon project configuration or regional regulation, the selected Engineering Profile shall identify the responsible party and preserve traceability to the applicable decision.
Responsibility may be transferred during the lifecycle, but it shall never disappear. Changes in ownership, maintenance providers, software services, manufacturers, or building configuration shall be recorded without breaking the chain of technical accountability.