Contracts

Normative behavioural contracts and stable schemas for HybridOps components.

Contracts define release-stable behaviour and interfaces. Procedures and tutorials belong in runbooks, guides, and how-to content.

Contents

• Operation contracts:
• Operation authority
• Decision-Driven DR orchestration
• Internal DNS and cutover
• Global runtime contracts:
• hyops init
• hyops preflight
• hyops setup
• Implementation-specific contracts:
• NetBox export hook
• PostgreSQL managed DR
• Extension contracts:
• Init target annexes
• Module contracts and templates
• Blueprint contracts and templates
• Driver contracts and templates

Standards

• Normative language only: MUST, MUST NOT, SHOULD, MAY.
• Target annexes do not repeat global contract content.
• Vendor documentation is not duplicated; supporting guides may reference external sources where required.
• Contracts are published on the docs site; runtime distributions do not embed long-form contract documentation.

Change control

Breaking changes to contract-defined behaviour require an explicit change note. Where stability is intended long-term, a superseding ADR is required.