Skip to main content
Compare allocation policies, publish an exact reviewed decision, and reconcile a shipment without duplicate effects.

​
Business capabilities

ontology, operations, branches, scenario-comparison, review, external-calls

​
Dataset

Synthetic four-order shortage at a fixed business time; exact integer stock and whole orders. License: Repository license; synthetic data authored for this example. Bound: 4096 rows, 1048576 bytes.
  • Bijection Northstar example authors; bijection/dataset.ts is the source of initial facts.

​
Journeys

​
Compare allocation policies

Actor: Warehouse planner. Four orders request 16 units; Lyon has 10 headlamps.
  1. Preview and run allocation on an isolated branch. Expected: Preview leaves both live and branch data unchanged.
  2. Compare the allocation against the pinned starting state. Expected: The comparison retains its original basis.
  3. Change allocation code in the branch. Expected: The reviewed code and resulting allocations agree.

​
Publish an exact reviewed decision

Actor: Warehouse approver. A planner has allocated stock in a branch.
  1. Try to publish a stale saved review. Expected: A stale review cannot publish.
  2. Review the bounded operation comparisons. Expected: The review carries an exact continuation.
  3. Request shipment in the branch. Expected: No carrier booking occurs from the branch.

​
Recover an accepted publication and carrier booking

Actor: Operations engineer. An accepted request may lose its reply or its backend.
  1. Kill the backend after acceptance and continue the same review. Expected: The accepted publication completes without duplicate allocations.
  2. Lose the carrier reply and reconcile the booking. Expected: Unknown delivery is reconciled to one booking.
  3. Discard every runtime branch. Expected: Discarded branch credentials no longer work.

​
Recipes

​
Source and evidence

Application: examples/northstar/bijection. The example’s overview, walkthrough and adaptation guide live beside usecase.json. Catalog source digest: 977f8f45a37d387d9103687a6438ef707b1c26f579e2b1efb161ba61a7a240b4. This identifies example inputs; it is not a successful execution or a runtime build claim.