Recovery is part of the product

Reliability is designed according to consequence. A marketing notification and a payment action should not share the same approval, permission, logging, or recovery standard.

ROUTE PAUSEDPermission expired
Record preserved
Owner alerted
Manual path available

Control model

The happy path is the demo. Recovery is the product.

Eight controls shape how a system validates work, limits authority, exposes failure, and returns control to an operator.

CONTROL / 01

Selected control

Validation

Required fields, schemas, formats, ranges, and business rules.

Release questionWhich inputs are valid before the route can continue?
ExpectedContinue with evidence
ExceptionPause for an owner
RecordPreserve useful context

AI controls

AI may assist the system. It does not inherit authority.

Deterministic software remains responsible for permissions, calculations, validation, confirmation, and stable controls. Financial, legal, employment, deletion, publication, and reputation-sensitive actions remain behind explicit authority.

Security honesty

No system is secure because a services page says so.

The proposal should state the security scope, threat assumptions, testing, hosting, dependencies, data categories, and client obligations.

STATUS / EXAMPLE

We detected an issue affecting the reporting workflow. The route is paused, the manual path is available, and the next update is scheduled.

Start with the stuck part

What should the system do when the expected path fails?

Show us the friction