This package only records package-published events and emits gateway-consumable change records. It does not implement a full publish state machine, admission workflow, or downstream routing synchronization.

Current repository boundary:

published means the upstream package event has been recorded
pending means the downstream gateway consumer has not yet confirmed handling
applied / failed means the current repository's consumer flow updated event state during the running process
current gateway event state in this repo is in-memory only, not durable across restart

Current runtime shape:

manual/debug entry: POST /internal/supply-intelligence/gateway/consume-once
minimal background path: application startup also runs a ticker-driven gateway poller

This avoids claiming that published = applied, and also avoids claiming that the current in-memory repository is a durable production persistence layer.