deliver-and-verify

Topics in the source

• Deliver and verify
• Step 0: Route the acceptance cases
• Coordinate the work
• Establish the acceptance cases
• Execute and verify
• Domain references

Carry the authorized outcome through execution and verification at the user, partner, or operator surface. Use the existing grants and release path; preserve user data and authorized spending limits. When changing a game, app or SaaS user journey, remaking a product, or publishing assets or configuration that change the experience, or comparing engines, read parity.md before defining the acceptance cases. It owns the screen-and-feature comparison, engine benchmarks, live evidence and automated release checks. For engine or SDK changes affecting controls, account entry or host lifecycle, including restored integrations, read shipping-host verification. Native tests and browser previews can exercise different input and feature paths. For credential import, guest restoration or account-continuity changes, read guest continuity before defining tests; decoding a retained value is not proof that its production consumer keeps it. Shared implementations follow the three architectural invariants: neutral mechanisms with caller-configured policy, zero domain leakage in code/prompts/verifiers/fixtures, and exact causal state/data/authorization guards that fail closed on unreadable required st

This is an excerpt. Refer to the complete source and its current requirements.