Blueprint contracts

Normative blueprint contracts define multi-step orchestration behaviour, safety boundaries, state dependencies, and evidence expectations for HybridOps blueprint families.

Blueprint contracts are not runbooks. Operator procedures belong under runbooks. Module implementation detail belongs in module contracts.

Scope

A blueprint contract specifies:

• blueprint identity and orchestration purpose
• required step families and step ordering boundaries
• required inputs and guard conditions
• consumed and published state contracts
• failure semantics and evidence expectations
• destructive-operation controls

Related contracts

• Global init behaviour: hyops init
• Preflight semantics: hyops preflight
• Module contracts: modules

Placement

• Template: blueprint contract template
• Blueprint-specific contracts: 2026E/<blueprint>.md (by epoch)

Current draft target-state blueprint contracts:

• 2026E/dr-postgresql-cloudsql-standby-gcp.md
• 2026E/dr-postgresql-cloudsql-promote-gcp.md
• 2026E/dr-postgresql-cloudsql-failback-onprem.md

Standards

• Normative language only: MUST, MUST NOT, SHOULD, MAY.
• Blueprint contracts define orchestration boundaries and stable interfaces, not tool-specific implementation detail.
• Step contracts SHOULD refer to canonical module contracts where available.
• Safety guards and destructive controls MUST be explicit.