developer-product-experience-reviewlisted

# Developer Product Experience Review Produce one **Developer Adoption Contract** that makes a developer product fast to evaluate, safe to integrate, observable in production, and maintainable across versions. Treat docs, SDKs, errors, sandboxes, dashboards, certification, and support as one product journey rather than separate content projects. ## Atomic boundary Own the external developer jobs and personas, discovery-to-production state model, success evidence, developer-facing surfaces, sandbox experience, integration certification, diagnostics, lifecycle communication, support route, experience metrics, and automation contract. Consume API/SDK implementation, identity, quota, billing, analytics, security, privacy, and delivery facts from their canonical owners; do not redesign those systems here. ## When not to use - Do not use for API/SDK implementation, compatibility architecture, low-level rate limiting, infrastructure capacity, or release engineering; hand the experience requirement to the owning engineering project under `engineering-standard` and `delivery-standard`. Use `software-distribution-readiness` when the independent job is selecting, implementing, or verifying CLI install and update channels. - Do not use for developer quota/free-credit abuse policy or generic product abuse; use `developer-quota-credit-abuse-review` or `product-abuse-risk-review` respectively. - Do not use for a whole app, analytics implementation, pricing/package design,