at-least-once-deliverylisted
Install: claude install-skill wntic/pyhouse
# At-least-once delivery — a unit delivered until it is acknowledged
The obligations a program owes each **unit another party delivers to it and delivers again until it is
acknowledged** — a broker's message, a record read from a stream, a webhook request from a third party.
They hold in any project, whatever its architecture and whatever delivers the unit. None binds a broker:
the limit and the dead letter are the delivery mechanism's configuration, declared with the deployment,
and the code that receives the unit — a consumer wrapper, a route, an inbound adapter — is written
under the project's own entrypoint skill. Rule 6 is the same guarantee from the other side: a program
relaying an effect it recorded with a committed write is that sender to whoever receives it.
## When to use vs. neighbours
- The consumer process, its wrapper and the HTTP route that apply these rules in a flat-layered service
→ `flat-entrypoint`, in the `pyhouse-flat` plugin; the inbound adapter of a hexagonal service →
`hex-architecture`, in the `pyhouse-hex` plugin. Both are examples; with neither installed, the
project's own entrypoint applies them.
- An older write never replacing a newer one for the same key, and deduplication left to the store →
`persistence` (rules 15–17); rule 4 here only says when that applies to a delivered unit.
- A failure after a committed write — whether its effect is recorded with the write at all, or stopped
and logged when it fails — and a failure stopped