Branches with a controlled carrier

Part of Allocate scarce stock and review scenarios.

Complete stack

System	Role	Owner	State	Version source	Failure contract
bijection	Objects, operations, branches, review and publication	Application owner	Operational state in PostgreSQL; file storage owned by the backend	Explicit native build manifest, CLI digest and application source digest	Accepted requests retain their identity through lost replies and process restart.
carrier	Shipment booking and reconciliation	Customer companion service	Booking records keyed by external call identity	Controlled carrier source captured with the journey	An ambiguous reply remains unknown until reconciliation.
postgres	Operational persistence	Qualification resource owner	Disposable local cluster with an exact resource record	Installed PostgreSQL executable version recorded by harness	Only the recorded cluster is stopped by cleanup.

Connections

bijection → postgres: Transactional operational persistence. Identity: Backend database credential.
bijection → carrier: Durable booking intent and status reconciliation. Identity: Run-scoped carrier capability.

Deployment inputs

build (file, required): Source-bound native build manifest.
cli (file, required): Bijection CLI executable.

Bounds and cleanup

One loopback backend and one disposable PostgreSQL cluster; bounded fixture; no cloud runtime. Maximum duration: 2400 seconds. Maximum captured log: 4194304 bytes. Estimated cost: No provider usage for this recipe. Uses the selected local machine. Cleanup: The qualification owner stops its exact child processes, removes credentials and stops its owned PostgreSQL cluster. A run passes only after cleanup is observed. The executable runbook is maintained at examples/northstar/recipes/controlled-carrier/runbook.md. A declared journey is verified only when every named check appears in a successful execution report and cleanup has been observed.

Get Started

Use-case atlas

Platform

Data and Operations

Guides

Client Libraries

Tools

API Reference

Branches with a controlled carrier

Complete stack

Connections

Deployment inputs

Bounds and cleanup

​Complete stack

​Connections

​Deployment inputs

​Bounds and cleanup

Complete stack

Connections

Deployment inputs

Bounds and cleanup