SAAS ENTITLEMENT ACCEPTANCE BRIEF
Status: proposed, unexecuted
Product owner: approve3/10project limits, active-count definition, T and G, grace experience, accepted-job rule
Billing integration owner: map chosen confirmation evidence, pending states, effective revision and reconciliation
Application owner: enforce same account/action/time decision in UI/API/job admission; role authorization remains separate
QA: On Pro create5fictional projects. Before T premium starts allowed; at T new starts denied and5projects readable. Accepted jobs follow captured entitlement subject to security revocation.
QA: Archiving frees capacity only under approved active-count definition. Test concurrent create/restore at boundary.
QA: Upgrade pending until confirmation effective; then verify a newly permitted action. Repeat delayed/duplicate evidence without regressing revision.
QA: Before G approved grace remains; at G no new projects or premium starts, existing data readable.
Support: show effective state, pending change and action-specific reason.
Acceptance evidence: screenshots of customer state plus server decision revision, persisted project counts and job admission record.