{
  "schema_version": "1.0",
  "program_id": "WACK-FOUNDERS-0001",
  "room_id": "ROOM-02",
  "pathway_id": "LEARN-06",
  "name": "W/ Founders: Launch Friday",
  "short_name": "W/ Founders",
  "title": "Your First Transaction Is an Architecture Event",
  "status": "public-pilot-pending-practitioner-review",
  "purpose": "A bounded, fictional 45-minute decision room for founders, incubators, accelerators, early product teams, and technical co-founders who need to distinguish payment capability from revenue, reconstruct the payment boundary before launch, and preserve a decision another person can reopen later.",
  "promise": "Leave with a reversible payment-boundary decision and a first-transaction operating runway—not a badge, a launch blessing, or a shortcut to a validation answer.",
  "authority_classification": ["PCI_SSC_SOURCE", "PRACTITIONER_POSITION", "PRACTITIONER_METHOD", "AI_ASSISTED"],
  "reading_ids": ["WACK-CONTENT-0138", "WACK-CONTENT-0140", "WACK-CONTENT-0139", "WACK-CONTENT-0105", "WACK-CONTENT-0097"],
  "roles": [
    {"id": "ROLE-01", "name": "Founder / decision owner", "job": "State the launch decision, business pressure, and authority actually held."},
    {"id": "ROLE-02", "name": "Product or engineering owner", "job": "Describe deployed behavior, identities, configuration, and change paths without relying on the pitch deck."},
    {"id": "ROLE-03", "name": "Security or operations owner", "job": "Challenge unsupported exclusions, evidence gaps, provider assumptions, and operating readiness."},
    {"id": "ROLE-04", "name": "Cold recorder", "job": "Preserve facts, decisions, limitations, owners, and reopening triggers without rescuing the group."}
  ],
  "fictional_case": {
    "name": "Launch Friday at Signal Cart",
    "brief": "Signal Cart is a fictional pre-revenue software company preparing to accept its first subscription payment. The application uses provider-hosted payment fields inside a company-controlled checkout page. A public callback updates subscription state. Two founders have production access. No customer transaction has completed, but the payment path is deployed and can be enabled with one configuration change.",
    "pressure": "At 09:00 Friday, the board asks whether the team can launch at 17:00. The evidence packet contains a provider badge, a pitch deck diagram, a staging test, and an incomplete responsibility spreadsheet.",
    "facts": [
      {"id": "FACT-01", "state": "present", "statement": "The company-controlled checkout route and production DNS are live."},
      {"id": "FACT-02", "state": "present", "statement": "Provider-hosted fields are embedded in the checkout page; the provider receives entered payment data directly."},
      {"id": "FACT-03", "state": "present", "statement": "The checkout page, script policy, deployment pipeline, and production configuration remain company-controlled."},
      {"id": "FACT-04", "state": "present", "statement": "A public callback hostname terminates at a company-managed gateway and invokes company application code."},
      {"id": "FACT-05", "state": "present", "statement": "Two founders hold production administrator roles; one role can change checkout configuration and callback secrets."},
      {"id": "FACT-06", "state": "production-capable", "statement": "A feature flag can expose checkout to customers without a new deployment."},
      {"id": "FACT-07", "state": "production-capable", "statement": "Live provider credentials and callback configuration are present in the production environment."},
      {"id": "FACT-08", "state": "observed", "statement": "Only staging transaction behavior has been exercised end to end."},
      {"id": "FACT-09", "state": "documented", "statement": "The provider assurance packet names a hosted-field service, but the customer responsibility row is incomplete for script and callback operation."},
      {"id": "FACT-10", "state": "asserted", "statement": "The founders assert that PCI DSS begins after the first successful customer payment."},
      {"id": "FACT-11", "state": "unknown", "statement": "The current external scan and penetration-test populations do not identify the callback termination."},
      {"id": "FACT-12", "state": "proposed", "statement": "Support wants a session-replay script added to the checkout shell before launch to diagnose abandonment."}
    ],
    "nodes": [
      {"id": "customer", "label": "Customer browser", "kind": "experience", "owner": "Customer"},
      {"id": "checkout", "label": "Signal Cart checkout shell", "kind": "company-code", "owner": "Product engineering"},
      {"id": "hosted-fields", "label": "Provider-hosted payment fields", "kind": "provider-service", "owner": "Provider + relationship owner"},
      {"id": "callback", "label": "Public callback receiver", "kind": "public-interface", "owner": "Payments engineering"},
      {"id": "subscription", "label": "Subscription service", "kind": "company-service", "owner": "Product engineering"},
      {"id": "identity", "label": "Founder and workload identity", "kind": "control-plane", "owner": "Platform owner"},
      {"id": "pipeline", "label": "Source, build, and deployment", "kind": "deployment-plane", "owner": "Engineering"},
      {"id": "evidence", "label": "Logs, alerts, and retained records", "kind": "evidence-plane", "owner": "Security + operations"}
    ],
    "edges": [
      {"from": "customer", "to": "checkout", "relationship": "LOADS"},
      {"from": "checkout", "to": "hosted-fields", "relationship": "EMBEDS"},
      {"from": "customer", "to": "hosted-fields", "relationship": "SUBMITS_ACCOUNT_DATA"},
      {"from": "hosted-fields", "to": "callback", "relationship": "CALLS_PUBLIC_ENDPOINT"},
      {"from": "callback", "to": "subscription", "relationship": "UPDATES_STATE"},
      {"from": "identity", "to": "checkout", "relationship": "ADMINISTERS"},
      {"from": "identity", "to": "callback", "relationship": "ADMINISTERS"},
      {"from": "pipeline", "to": "checkout", "relationship": "DEPLOYS"},
      {"from": "pipeline", "to": "callback", "relationship": "DEPLOYS"},
      {"from": "callback", "to": "evidence", "relationship": "EMITS"}
    ]
  },
  "capability_states": [
    {"capability": "Customer checkout route", "proposed": false, "present": true, "production_capable": true, "effective": false, "stopping_question": "What exact event makes the route available to a customer?"},
    {"capability": "Provider-hosted payment collection", "proposed": false, "present": true, "production_capable": true, "effective": false, "stopping_question": "Which deployed configuration and service mode define the current provider relationship?"},
    {"capability": "Public payment callback", "proposed": false, "present": true, "production_capable": true, "effective": false, "stopping_question": "Which hostname, gateway, code revision, secret, and test population describe it?"},
    {"capability": "Founder production administration", "proposed": false, "present": true, "production_capable": true, "effective": true, "stopping_question": "What can each role change, invoke, approve, export, or cause another system to do?"},
    {"capability": "First-transaction monitoring", "proposed": false, "present": true, "production_capable": true, "effective": false, "stopping_question": "Which expected events and failures are observable before the first customer arrives?"},
    {"capability": "Incident and support response", "proposed": false, "present": true, "production_capable": false, "effective": false, "stopping_question": "Who can act, with what access and retained evidence, during a payment failure?"},
    {"capability": "Production evidence runway", "proposed": false, "present": true, "production_capable": false, "effective": false, "stopping_question": "Which required operating histories cannot exist until time and occurrences accumulate?"},
    {"capability": "Checkout session replay", "proposed": true, "present": false, "production_capable": false, "effective": false, "stopping_question": "What can the script observe or influence, and which prior boundary claims must reopen?"}
  ],
  "session": {
    "duration_minutes": 45,
    "outcome": "A bounded launch decision record, capability-state ledger, two-path boundary map, provider responsibility brief, first-transaction evidence runway, and explicit reopening triggers.",
    "phases": [
      {"id": "PHASE-01", "minutes": 5, "name": "Name the decision", "instruction": "Write the exact decision requested, the deadline, who can make it, and what the room cannot conclude."},
      {"id": "PHASE-02", "minutes": 7, "name": "Separate capability states", "instruction": "Classify each payment-relevant capability as proposed, present, production-capable, or effective. Preserve disagreements."},
      {"id": "PHASE-03", "minutes": 8, "name": "Trace two paths", "instruction": "Map where payment data moves and what identities, code, public endpoints, providers, and deployment systems can influence its security."},
      {"id": "PHASE-04", "minutes": 8, "name": "Assign retained work", "instruction": "Separate provider performance from customer configuration, operation, evidence, testing, change, incident, and reporting responsibilities."},
      {"id": "PHASE-05", "minutes": 7, "name": "Build the evidence runway", "instruction": "Name what must exist before launch, at first transaction, after each occurrence, and only after an operating period."},
      {"id": "PHASE-06", "minutes": 10, "name": "Inject change and decide", "instruction": "Introduce the session-replay request, reopen affected facts and claims, then record one bounded decision with conditions, owners, limitations, and triggers."}
    ]
  },
  "records": [
    {"id": "FOUNDERS-REC-01", "name": "Payment Capability State Ledger", "purpose": "Keep proposed, present, production-capable, and effective behavior from collapsing into one launch narrative.", "fields": ["capability", "current state", "activation event", "owner", "evidence", "open fact", "reopening trigger"]},
    {"id": "FOUNDERS-REC-02", "name": "Pre-Launch Boundary Map", "purpose": "Join account-data movement to the identities, code, endpoints, providers, and deployment paths that can influence it.", "fields": ["subject", "relationship", "data or influence", "owner", "provider dependency", "evidence", "uncertainty"]},
    {"id": "FOUNDERS-REC-03", "name": "Provider Responsibility Brief", "purpose": "Turn provider reliance into exact service, activity, configuration, evidence, and retained-customer-duty statements.", "fields": ["service", "provider activity", "customer activity", "assurance source", "implementation evidence", "conflict", "reverification event"]},
    {"id": "FOUNDERS-REC-04", "name": "First-Transaction Evidence Runway", "purpose": "Separate pre-launch proof from first-occurrence evidence and evidence that requires operating time.", "fields": ["evidence event", "before launch", "first transaction", "recurring occurrence", "period required", "owner", "retention"]},
    {"id": "FOUNDERS-REC-05", "name": "Launch Decision and Reopening Record", "purpose": "Preserve the decision the named owner actually made without turning the room into approval, assessment, or acceptance authority.", "fields": ["decision requested", "current facts", "decision", "conditions", "owner", "limitations", "reopening triggers"]}
  ],
  "decision_states": [
    {"id": "DECISION-01", "label": "Proceed with bounded conditions", "meaning": "The accountable business owner can proceed only with named conditions, owners, timing, and reopening triggers; this is not a compliance result."},
    {"id": "DECISION-02", "label": "Hold for facts", "meaning": "A material factual uncertainty prevents a responsible business decision until it is resolved."},
    {"id": "DECISION-03", "label": "Change the boundary", "meaning": "The current architecture creates obligations or uncertainty the team elects to redesign before launch."},
    {"id": "DECISION-04", "label": "Escalate validation direction", "meaning": "The team needs direction from its compliance-accepting entity and qualified professional; the room cannot supply it."}
  ],
  "change_injection": {
    "title": "The Thursday Replay Request",
    "trigger": "Support asks engineering to add a third-party session-replay script to the company-controlled checkout shell before launch so founders can diagnose abandonment.",
    "required_reopens": ["checkout script inventory", "account-data and security-influence map", "provider integration constraints", "content and script policy", "software and provider inventory", "testing population", "change evidence", "launch decision"],
    "anti_shortcut": "Do not conclude that the script is automatically in scope, out of scope, compliant, or prohibited. Establish what it can observe or influence, where it loads, how it is governed, and which claims no longer survive unchanged.",
    "stopping_question": "Which exact boundary statement can remain true after this script is enabled, and what evidence supports it?"
  },
  "facilitator_rules": [
    "Use only the fictional Signal Cart facts. Do not invite participants to disclose a real company architecture, provider tenant, customer, investor, or assessment.",
    "Do not explain the intended answer during the first pass. Record the first fracture in the material or sequence.",
    "Require facts and authority before conclusions. A founder title, provider badge, dashboard color, or planned remediation is not the missing evidence.",
    "Preserve minority uncertainty. Do not force consensus by hiding a material unknown in the decision notes.",
    "End with a business decision record, not a PCI DSS compliance result, SAQ choice, provider endorsement, or assessor conclusion."
  ],
  "pilot_observation_fields": ["session_date", "tested_surface", "audience_roles_present", "first_fracture", "authority_overreach", "expected_move", "observed_move", "oral_rescue", "smallest_repair", "retest_condition", "decision_signal", "known_limitation"],
  "success_conditions": [
    "A cold founder can separate proposed, present, production-capable, and effective behavior without facilitator correction.",
    "The group can reconstruct both the account-data path and the security-influence path from retained artifacts.",
    "Provider assurance is treated as evidence about exact services and activities—not as customer launch approval.",
    "The late change reopens the affected records before the group records a decision.",
    "Another reader can identify the decision owner, conditions, limitations, and reopening triggers without founder oral history."
  ],
  "boundary": "W/ Founders is independent practitioner education using a fictional company and fictional facts. It is not PCI SSC guidance, not an assessment, not a compliance result, not an SAQ-selection or eligibility decision, not legal or investment advice, not launch approval, not provider certification or endorsement, and not direction from a compliance-accepting entity. It does not authorize testing. Never enter account data, credentials, provider secrets, client evidence, restricted architecture, customer information, investor information, or identifying startup facts.",
  "next_gate": "Scott Norton records an exact-digest practitioner disposition, then one real founder, incubator, or accelerator partner runs the fictional 45-minute room. Preserve the first fracture, smallest repair, and second-reader retest before commissioning slides, a campaign, credentials, or a broader startup program."
}