Customer Acceptance
role · created
Evidence record
- What is verified
- Uses in published workflows: 2
- Revision
- Version 0.1.6
- Validation status
- Public-sanitized publication; no independent validation is claimed.
What this is and why
The customer-side role that decides whether delivered work is accepted in the two-sided execution model. It reviews each delivery pull request criterion by criterion against the acceptance criteria stated in the originating issue and records the decision on the pull request itself: merge means accepted, request-changes means returned with the failed criterion named. The role never repairs a delivery and never invents criteria after the fact; work the customer had to fix counts as work that was not delivered.
Where it was applied and what it helped deliver
Metadata and provenance
- id
- tal-role-customer-acceptance
- type
- role
- version
- 0.1.6
- origin
- created in Talomnia
- lifecycle
- public_sanitized
- tags
- role, two-sided-model, talo-0024
The source is the private knowledge repository; only the sanitized public projection reaches this site.
verified · tal-role-customer-acceptance · v0.1.6