Private product previewReview the controlled design-partner evaluation path.Explore

The operating model

Every state should leave evidence behind

The current source stops at synthetic local release. Carrier booking, labels, and provider reconciliation remain separate future boundaries.

Order spine · DEMO-10428
CONTROLLED SYNTHETIC EXAMPLEHELD · WEIGHT MISMATCH · V4
01

Capture

The source contract models idempotent synthetic intake with a stable order identifier and replay protection.

request key · received state
02

Normalise

Canonical records and bundle expansion are product direction.

planned lineage · expansion map
03

Validate

The source models deterministic, versioned validation evidence for synthetic correction flows..

attempt log · ruleset version · fingerprint
04

Correct

The source models bounded field changes with a reason while preserving the original synthetic capture..

before/after value · actor · reason
05

Decide

Rules and explainable outcomes remain a source-backed design direction rather than a live decision service..

planned match · priority trace
06

Approve & release

The source separates local correction, validation, approval, and release states.

policy version · approval · local operation
07

Execute & reconcile

Provider work is a future, separately accepted boundary.

future request key · provider result

Each state is separate. A correction is not a release, and a release is not a carrier booking. The example above is synthetic and does not perform provider work.

Seven stages, each with its own evidence

What changes, who changed it, and why it moved are part of the record — not a note added later.

01 · Capture

Capture

The source contract models idempotent synthetic intake with a stable order identifier and replay protection. No live channel is connected.

Evidence: request key · received state

In source

02 · Normalise

Normalise

Canonical records and bundle expansion are product direction. Provider-specific transformations are not active.

Evidence: planned lineage · expansion map

Roadmap

03 · Validate

Validate

The source models deterministic, versioned validation evidence for synthetic correction flows.

Evidence: attempt log · ruleset version · fingerprint

In source

04 · Correct

Correct

The source models bounded field changes with a reason while preserving the original synthetic capture.

Evidence: before/after value · actor · reason

In source

05 · Decide

Decide

Rules and explainable outcomes remain a source-backed design direction rather than a live decision service.

Evidence: planned match · priority trace

In source

06 · Approve & release

Approve & release

The source separates local correction, validation, approval, and release states. Release is not carrier execution.

Evidence: policy version · approval · local operation

In source

07 · Execute & reconcile

Execute & reconcile

Carrier booking and provider reconciliation remain discovery work. No provider handler is active.

Evidence: future request key · provider result

Discovery
Seven waystones along a coastal trade road

The principle behind the flow

Uncertainty should become visible work. It should never become an invisible assumption.

TraceableThe source record remains traceable.
ExplicitTransformations are explicit, not implied.
HonestUncertainty produces a hold, not a guess.
AuthorisedSensitive change requires authority, and authority is recorded.
RecoverableEvery outcome can be reconstructed after the fact.

Walk a safe example through it

A proposed review would use synthetic or irreversibly redacted examples, with scope and data handling agreed before anything is shared.