# From Working Feature to Reviewable Payment Architecture

**Audience:** Software and product engineers, Cloud, platform, and site-reliability teams, Architects and technical product owners, Developer communities, bootcamps, and engineering programs  
**Duration:** 90 minutes  
**Program:** WACK-BUILDERS-0001

## Session outcome

One fictional payment narrative, one two-path architecture, one provider responsibility record, one test proposition, and one change fan-out that another engineer can reconstruct.

## Run of show

1. Fifteen minutes: read the fictional build and narrate normal, failure, refund, support, and administrative behavior.
2. Fifteen minutes: map account-data and security-influence relationships without drawing a scope circle.
3. Fifteen minutes: assign exact provider, customer, shared, assessor, and accepting-authority statements.
4. Fifteen minutes: give ephemeral workloads, identities, public endpoints, and deployments durable record identities.
5. Fifteen minutes: derive one test proposition, complete population, representative environment, evidence, and retest condition.
6. Fifteen minutes: run one change drill and decide which records reopen before the release can close.

## Facilitation test

Do not rescue the first participant from a missing relationship. Record the first point where the material requires oral context, repair the shared artifact, and retest the same task with another cold reader.

## Facilitator boundary

W/ Builders is independent practitioner education and a fictional pilot. It is not PCI SSC guidance, not official training, not a provider certification, not an eligibility decision, not a PCI DSS assessment, not a compliance result, and not permission to test a real system. It does not substitute for assessor judgment or compliance-accepting-entity direction. Use only fictional or explicitly sanitized environments. Never enter account data, credentials, provider secrets, client evidence, restricted architecture, or targets the participant is not authorized to test.