After accepted launch and 30-day stabilisation, the firm chooses who will monitor the system, coordinate providers, handle exceptions and govern change. Handover is a complete option—not a disguised path into a retainer.
Human-reviewed workflowPrices shown are the current operating model, not an automatic continuation. Final responsibility, hours, usage and dependencies are defined in the governing agreement.
A broad promise to keep the system working hides both risk and labour. The operating agreement names the activity, response boundary and retained human authority.
Who notices failed runs, degraded retrieval, provider changes and abnormal exception volume?
Who owns provider accounts, permissions, user administration and credential rotation?
Who investigates an operating exception, and where does professional authority remain?
What is correction, what is optimisation and what requires a new scope or risk review?
The initial system stays governable when operating defects, routine assurance, optimisation and new scope are treated as distinct changes.
An accepted behaviour does not perform as agreed. During stabilisation, Build n Bloom corrects and retests the in-scope defect.
The accepted workflow needs a named inspection of controls, versions, providers, exceptions or performance.
The same bounded workflow can be improved within an agreed responsibility and capacity envelope.
A new workflow, source, permission, integration, decision or risk boundary requires explicit assessment and agreement.
The relevant measures are selected during the Blueprint. They allow the owner to see whether the workflow remains useful without inventing a universal ROI guarantee.
Monitoring creates evidence for a decision. It does not grant the system authority to change itself.
Execute the accepted workflow version
Retain inputs, steps, latency and exceptions
Compare behaviour with written tests
A person classifies defect, drift or new need
Change the bounded logic or control
Retest and approve a new version
Usage, retrieval, exceptions and reviewer behaviour remain visible to the named owner.
Defect, provider drift, new source or expanded scope follows its own authority and acceptance route.
Time to find the applicable source, precedent or prior decision.
Human handling time from accepted intake to review-ready material.
Correction loops, unresolved questions and senior reviewer handling time.
Source coverage, required-field completeness and unsupported-claim stops.
Unowned commitments, missing decisions and time to an accepted operating record.
Exception-routing performance, defects, rollback tests and version integrity.
The correct operating model depends on the workflow, internal owner, provider risk and recurring responsibility—not a preference for recurring revenue.
