Skip to main content

Job kinds and compositions

Scope​

koto7 models logistics intents as job kinds that are assembled into composition patterns.

Invariants​

  • Each job kind must define a state machine contract.
  • Composition patterns must be explicit and versioned.
  • State transitions must be validated at domain-command level.

Failure Modes​

  • Composition-level deadlocks from invalid dependency ordering.
  • Silent transition rejection from incompatible job state assumptions.
  • Event payload mismatch between composed job boundaries.

Out of Scope​

  • Customer-specific state diagrams.
  • Proprietary optimization heuristics for composition selection.
  • Internal cost model details.