Contracts

Normative behavioural contracts and stable schemas for HybridOps.Studio components.

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

Contents

• Global command-family contracts:
• hyops init
• hyops preflight
• hyops setup
• DR execution and endpoint contracts:
• Decision-Driven DR Orchestration Contract
• Internal DNS and Cutover Contract
• PostgreSQL DR lane contracts:
• PostgreSQL managed DR contract
• Init target annexes: init/
• Module contracts and templates: modules/
• Blueprint contracts and templates: blueprints/
• Driver contracts and templates: drivers/

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.