Case 01 · Workflow control

Workflow Change Composer

Change an operating rule in plain language, see exactly what it affects, and prove the resulting behavior before trusting it.

Open the change dossier

Primary decisionKeep approval human

Primary resultChange verified locally

LimitationThe public lab is local and synthetic. Native runtime binding remains unverified, and recorded patch generation used a deterministic replay bank rather than proven live model generation.

Change dossier · synthetic

One request. Every consequence.

Command

Written change

Keep approval human. If it waits more than four hours, create an escalation record for Finance Operations.

Locked constraintHuman approval must remain.

Affected workflow

Awaiting impact trace

eventRequest received

humanHuman review

gateDecision

new4h timer

newEscalation record

eventComplete

Semantic diff

Hidden until mapped

Advance the replay to explain the change in operating language.

Decision rail

v4.0 → v4.1

01
Command
Bounded request received
02
Impact
Pending
03
Diff
Pending
04
Validation
Pending
05
Replay
Pending
06
Receipt
Pending

Validation

Assertions appear only after the candidate diff is inspectable.

Same case, different behavior

Baseline at 4h01Pending replay

Candidate at 4h01Pending replay

Inspect proof and limits

Default fixture outcome

Change verified locally

At 4h01 an escalation record exists while approval remains human.

Synthetic replay · network none · mutation none

Inspect evidence boundary

MaturityTechnical product

EvidenceRecorded source · synthetic replay

The operating problem

A workflow edit is easy to request and hard to trust.

The change itself is only one part of the job. A safe operating system must expose impact, preserve human constraints, validate the new path, compare behavior, and leave a recovery receipt.

What the system controls

Control survives the change.

Human stays in the loop

A fixture can preserve the checkpoint or fail closed when a request attempts to remove it.

Validation is not the finish line

A structurally valid change can still fail its synthetic behavior probe.

Recovery is forward and visible

Rollback creates another local receipt pointing to the last verified behavior.

Proof and limits

Three kinds of truth

Recorded

Owner-controlled source artifacts record the typed edit, validation, versioned release, and rollback lifecycle. Recorded patch generation used a deterministic replay bank; live model generation is not claimed.

Synthetic

This portfolio interaction uses three credential-free fixtures with deterministic outcomes and no network.

Unverified

Native orchestration-runtime binding and real job execution are not claimed.

Written-first handoff

Need a controlled workflow change?

Start with the rule, the constraint that must survive, and the evidence needed before rollout.

Open the written brief