# W/ Founders — Launch Friday

**Room:** ROOM-02 · **Portfolio stage:** Next  
**Audience:** Founders, incubators, accelerators, early product teams, and technical co-founders

> Your first transaction is an architecture event, not merely a revenue event.

## Consequential question

Which payment capabilities become present, production-capable, or effective before the first dollar arrives?

## Fictional scenario

A fictional startup embeds provider-hosted payment fields, receives a public webhook, grants two founders production access, and has not yet processed a transaction.

**Pressure:** The board wants launch approval Friday; the team has a provider badge, a pitch deck, and incomplete operating records.

## Five working artifacts

- [ ] Payment-capability state ledger
- [ ] Pre-launch boundary map
- [ ] Provider responsibility brief
- [ ] First-transaction evidence runway
- [ ] Launch reopening triggers

# Four practice moves

## 1. Separate

**Prompt:** Distinguish proposed, present, production-capable, and effective behavior.

**Output:** Capability-state table

## 2. Trace

**Prompt:** Map account-data and security-influence paths through page, identity, deployment, callback, and provider.

**Output:** Dual-path map

## 3. Commit

**Prompt:** Name the operating obligations the architecture creates before revenue.

**Output:** Owner runway

## 4. Gate

**Prompt:** State the facts required for a bounded launch decision and what would reopen it.

**Output:** Launch decision record

## Bounded decision output

A reversible payment-boundary decision and first-transaction operating runway.

## Pilot format

A 45-minute founder boundary session using one fictional architecture and one material late-stage change.

## Stop rule

Stop if the room becomes launch approval, legal advice, investment diligence, an SAQ-selection engine, or a provider endorsement.

## Reviewed reading route

- WACK-CONTENT-0138
- WACK-CONTENT-0140
- WACK-CONTENT-0139
- WACK-CONTENT-0105
- WACK-CONTENT-0097

## Program boundary

W/ Practice Rooms is practitioner-developed commissioning material. It is not PCI SSC guidance, not an assessment, not a compliance result, not an accredited curriculum, not professional certification, and not legal, financial, healthcare, public-sector, employment, or product-validation advice. Every room uses fictional facts and requires its named pilot before expansion.