ratemyserverlisted

# RateMyServer Judge whether a real service can preserve its promises under traffic, retries, concurrency, dependency failure, restart, and operator intervention. Review observable behavior and server-enforced invariants, not framework reputation or textbook completeness. Read `references/review-contract.md` for every review. It is the single source of truth for evidence, findings, gates, decisions, the opening issue list, and re-review identity. ## Stable server invariants | Invariant | Required behavior | |---|---| | Authority | Authenticate the caller and enforce role, ownership, and tenant policy on the server for every reachable operation. | | Effect identity | Give each consequential operation a stable identity so retry, redelivery, replay, or resume cannot silently duplicate it. | | State integrity | Keep authoritative state and externally visible effects consistent across concurrency, partial failure, and restart. | | Bounded work | Bound admission, queues, fan-out, retries, memory, connections, execution time, and cancellation. | | Truthful completion | Report success only after the promised durable state or effect is established, or expose an honest pending state. | | Recoverability | Preserve enough durable state, checkpoints, backups, and procedures to resume or restore without inventing progress. | | Operability | Make saturation, failure, retry storms, data drift, and recovery visible and attributable to an immutable release. | ## Resolve the two review set