Appendix: operating and migration worksheets

A completed hold identifies known and missing evidence, the responsible role and the permitted act. Its release condition and authority make it an accountable decision even while an evidence item is absent. An unanswered prompt remains a template. Attaching the missing item to a defined prohibition makes the consequence inspectable rather than suggesting that a filled record has resolved the question.

The appendix records illustrative decisions with fictional enterprise roles and declared evidence identities. Frozen cases supply actual computational evidence; the operating evidence is required and absent. No real document receipt or sponsor approval is asserted. Read each filled record for the act its missing proposition holds, preserving the distinction between a completed decision and obtained evidence.

Each record contains a bounded use or commitment, a role with the relevant decision responsibility, evidence identity and status, an event before which the evidence is required and an authority to stop or release the action. Event-based deadlines are used because no real calendar has been supplied. Before automatic posting or before cutover are precise operating boundaries. They do not pretend that a fictitious date is a verified delivery commitment.

The service owner should retain relationships among the records. Data meaning supports migration acceptance; authority supports automation; funding supports continuing exception handling; exit evidence supports provider dependence. A record should not be treated as complete in isolation if its required upstream condition remains absent. The companion dependency map can expose a declared prerequisite, but the operating record identifies the evidence needed to make that prerequisite usable.

Adapt a record with actual authority, scope, evidence and deadlines, keeping analytical assumptions separate from acceptance evidence. Retain independent challenge when the consequence warrants it. The worked logic helps define that decision; completing its fields does not certify a programme.

The service record for the fictional exception capability accepts bounded discovery of case handling and authority. The operating service owner is responsible for defining the included population and obtaining a legitimate decision route. Evidence E-SERVICE-CASE is required and not supplied. Production use remains held until a changed-instruction case demonstrates that the service can reach accountable resolution. The investment chair may authorise a narrower learning scope but cannot infer production readiness from the analytical selection.

The data record for availability meaning retains the automated-promise hold. The data owner defines permitted states, while stores confirms the physical interpretation. Evidence E-AVAILABILITY-USE is required and absent. Before any automatic promise, the authorised operating owner must accept the intended population and its unknown-handling route. A populated field or a lower model readiness score does not release that condition. The record joins meaning, evidence and authority rather than using a data-cleanliness label.

The ownership record identifies technical equivalence and commercial approval as different powers. Engineering owns substitution suitability for the stated use; finance owns expenditure under its real delegation. Evidence E-DELEGATION-COVERAGE is required and not supplied. A substitute cannot be released merely because a workflow offers an approval action. The relevant delegated role retains the hold until legitimate authority and unavailable-role coverage are documented.

These records illustrate how the synthesis changes the operating commitment. The analytical app can include data and ownership in a positive bundle, while the production use remains held. The sponsor can fund work to obtain evidence without claiming that the evidence already exists. This is a more precise decision than either unconditional rollout or an indefinite statement that the enterprise is not ready.

The records should be revised when evidence arrives. An accepted bounded population can release that use while leaving wider scope held. A failed case test can direct repair or stop. The owner should preserve the original condition and the new evidence so a later reviewer can understand why the action changed. A current status alone would lose that causal history.

The cutover record separates the included routine population from complex substitutions retained in the legacy route. Evidence E-CUTOVER-CHANGED-CASE and E-ROLLBACK-RECONCILIATION are required but absent in this illustrative record. Before a real cutover, the service owner must obtain accepted evidence that meaning, legitimate approvals and transition events remain intelligible. The operating release owner can hold the stage if those conditions fail, even if the technical data-load report is successful.

The rollback obligation preserves legitimate work performed after cutover. A restoration event cannot erase approvals or physical actions. The completed record therefore assigns reconciliation to the service owner and requires an authorised source-of-truth decision before restored production use. It does not specify an invented recovery time. A real programme would need actual technical and operating evidence to establish a usable continuity target.

The benefit record keeps the model's annual benefit assumption separate from measured outcomes. Evidence E-BENEFIT-MECHANISM is required for a claim that conflict handling has changed usefully. Evidence E-FINANCIAL-CONSEQUENCE is required for a financial effect. Both are absent here. The benefit owner may use the frozen model for conditional comparison, but cannot declare realised savings. The finance decision owner retains authority over any actual financial acceptance.

The event for the next benefit decision is before expansion justified by a claimed realised effect. The sponsor can expand for a different legitimate reason if its evidence and authority support that reason, but should not use a benefit claim whose evidence remains absent. This makes the record useful under pressure: it governs the argument for the commitment as well as the commitment itself.

A real evaluation may produce a mixed result. The service can improve clarity while increasing maintenance burden, or achieve operating benefit without a cash effect. The record should allow that evidence to revise the proposition. It should not require the evaluator to convert every useful outcome into a favourable financial result. The accepted decision should match the evidence actually available.

The exit record requires a usable history package and independent interpretation before broad dependence is accepted without qualification. Evidence E-EXIT-CHANGED-CASE is required and not supplied. The enterprise architecture owner defines the necessary meanings and the commercial owner obtains the actual contractual review. Neither the illustrative record nor a provider's general export claim establishes a legal right. The sponsor may accept a bounded temporary dependence if its burden and resolution are consciously recorded.

The exit event is before broad rollout or a renewal decision that relies on portability. The stop authority is the sponsor responsible for that commitment, informed by operating and specialist evidence. A product can remain useful while this condition is unresolved, but the programme should not call the service portable. The record distinguishes a consciously accepted dependence from a proven exit capability.

The challenge record preserves independent review of the central method. It asks whether the exact cases support their printed interpretations, whether operating gates actually change a branch and whether completed records contain a usable authority. The author does not score acceptance. A reviewer should inspect the frozen outputs, source content, manuscript and actual rendered artifact. Findings should identify a concrete contradiction, omission or unsupported claim rather than merely reward length or visual polish.

Trace the next action through its evidence identity and status, role, event boundary and stop authority. Missing evidence holds a particular use; new applicable evidence can change that branch. The worked records make this route inspectable, while a real organisation must supply the evidence, powers and behaviour needed to operate it.