Driver contracts

Normative driver contracts define driver interfaces, execution rules, and run-record expectations.

Driver contracts are not implementation documentation. Operational procedures belong under runbooks and guides.

Scope

A driver contract specifies:

• driver identity and supported profiles
• context, request, and result interface expectations
• execution and side-effect rules
• run-record expectations
• security rules
• change control expectations

Related contracts

• Global init behaviour: hyops init
• Module contracts: module contracts
• Init target prerequisites: init annexes

Placement

• Driver-specific contracts: <driver>.md

Standards

• Normative language only: MUST, MUST NOT, SHOULD, MAY.
• Contracts define stable behaviour and interfaces, not tool vendor documentation.
• Run-record expectations MUST be stated in terms of minimum records and redaction rules.