Expand description
Fleet outbox foundation (open-core seam, Stage 0): the appliance-side read API over the durable,
ordered transactional outbox (outbox table) plus a tiny unauthenticated site-identity endpoint.
GET /api/v1/outbox?since_seq=&limit= is the cursor a future edge->cloud uplink (or an
out-of-process app) polls to drain committed detection batches in seq order WITHOUT running a
message broker on the box — the DB is the log. It is admin-only and audited. GET /api/v1/site
reports this node’s identity (HELDAR_SITE_ID, build version, boot time) so a fleet controller can
correlate outbox cursors with the site they came from; it carries no secrets and needs no auth.