supply-intelligence/docs/POLLER_RUNTIME_BOUNDARY.md

Gateway poller runtime boundary

Current repository stage:

• package publish writes a pending gateway event
• gateway consumer can poll, apply, and ack that event
• the repository implementation in this repo is still in-memory only

This means:

• published means the upstream package event was recorded
• applied / failed means the in-process consumer flow handled the event during the current process lifetime
• this repo does not yet claim durable database persistence for gateway event ack state

Runtime shape in the current repo:

• HTTP debug/manual endpoint: POST /internal/supply-intelligence/gateway/consume-once
• background runtime path: application startup wires a minimal ticker-driven poller loop

Non-goals for the current stage:

• no MQ / Redis / external scheduler
• no claim that a full durable publish state machine is complete
• no claim that in-memory ack state survives restart