# W/ Learning Pathways

**Audience Program Portfolio** · WACK-LEARNING-ROADMAP-0001 · Public Planning Portfolio

> Different first door. Same authority boundaries. Every path must earn expansion through observed learner friction.

Track distinct audience doors into the governed Cluster of Wack body of work without cloning the underlying technical content or inventing audience-specific standards.

## Authority and release boundary

This is a practitioner planning portfolio. It is not PCI SSC guidance, not an accredited curriculum, not a certification program, not an assessment result, and not a promise that every proposed path will be produced. Established programs retain their own exact-digest review gates. Planned programs advance only after the named pilot evidence exists.

## Open now

A public program exists. The next investment is a real cold-reader or facilitator observation, not more speculative packaging.

### W/ Main Street — Chamber members, small merchants, and local business operators

**Reader problem:** Card acceptance creates recurring technology, provider, evidence, access, scanning, and incident duties that rarely arrive as one understandable operating story.

**First product:** The existing five-question member path, ten field guides, eight-module kit, and 30-minute Chamber session.

**Pilot gate:** Run one Chamber-member cold read and record the first payment-journey, provider, or recurring-work instruction that fails without oral explanation.

**Reuse basis:** WACK-CHAMBER-0001, WACK-GUIDANCE-0001

**Duplicate guard:** Keep this a plain-language projection over the same sources and methods; do not create a small-business PCI standard or a second eligibility checklist.

**Safety boundary:** No member evidence collection, automatic SAQ selection, scope conclusion, assessment result, or Chamber organizational position.

---

### W/ Campus — College students, faculty, student organizations, interns, and early-career practitioners

**Reader problem:** Learners need to practice payment-security reasoning before they possess production access, client evidence, or professional authority.

**First product:** The existing five-stream learning lab, ten guides, eight lab sheets, and 60-minute facilitator session.

**Pilot gate:** Run one student cold read and capture the first payment-story, authority, or lab instruction that fails.

**Reuse basis:** WACK-CAMPUS-0001, WACK-NOTATION-0001

**Duplicate guard:** Extend the approved project-based program only after learner observation; do not commission a parallel course, anthology, or slide universe.

**Safety boundary:** Fictional or sanitized systems only; no real account data, credentials, restricted architecture, unauthorized testing, accreditation, or qualification claim.

## Pilot next

The audience problem is distinct, the first product is bounded, and an existing governed content base can support a small pilot.

### W/ Faculty — Faculty, instructors, adjuncts, and curriculum designers

**Reader problem:** An instructor can find practitioner material yet still lack a teachable sequence, assessment rubric, safe lab boundary, and answer key that preserve source authority.

**First product:** A public pilot with one cumulative fictional case, five teaching moves, three 75-minute lesson plans, a six-dimension analytic rubric, six answer boundaries, five intervention cards, eight portable faculty records, ten reviewed readings, and a 90-minute design studio.

**Pilot gate:** One educator can run one session without oral rescue, and a second educator can apply the rubric to the same anonymous fictional artifact with a materially similar reasoning result.

**Reuse basis:** WACK-FACULTY-0001, WACK-CAMPUS-0001, WACK-AUTHORITY-0001, WACK-WML-LAB-0001

**Duplicate guard:** Package W/ Campus for instruction; do not rewrite its technical articles or present practitioner exercises as official courseware.

**Safety boundary:** No accreditation, official PCI SSC training, grading mandate, certification, or claim that classroom completion creates assessment authority.

---

### W/ Workforce — Career-transition programs, workforce boards, veterans, and displaced technology workers

**Reader problem:** Career guidance often names job titles without showing the concrete artifacts, reasoning moves, and adjacent skills that make payment-security work understandable.

**First product:** A 90-day role-to-project pathway connecting five fictional deliverables to architecture, operations, evidence, assurance, and communication roles.

**Pilot gate:** One counselor and three learners can map prior experience to projects without collapsing the field into a single PCI job.

**Reuse basis:** WACK-CAMPUS-0001, WACK-ROADMAP-0001

**Duplicate guard:** Reuse the Campus portfolio method and existing career-role map; do not create a hiring marketplace or guarantee employability.

**Safety boundary:** No employment guarantee, competency certification, assessor qualification, résumé verification, or collection of sensitive career data.

---

### W/ Builders — Software-engineering programs, bootcamps, developer communities, and product engineers

**Reader problem:** Developers learn payment APIs quickly but often miss the architecture, webhook, identity, deployment, provider, test, and evidence relationships around the code.

**First product:** A public pilot with one fictional hosted-payment architecture, five build moves, six checkpoints, four change drills, eight workbench records, twelve reviewed readings, and a 90-minute session.

**Pilot gate:** A developer unfamiliar with the method can explain both the account-data path and the security-influence path from the same fictional build.

**Reuse basis:** WACK-BUILDERS-0001, WACK-PT-RESEARCH-0001, WACK-CAMPUS-0001, WACK-APPLICABILITY-0001

**Duplicate guard:** Compose existing payment-boundary and modern-architecture methods into one capstone; do not fork a developer-only PCI interpretation.

**Safety boundary:** No live PAN, production credentials, unauthorized testing, insecure sample secrets, provider certification claim, or compliance result.

---

### W/ Founders — Incubators, accelerators, founders, and early product teams

**Reader problem:** A pre-launch team needs enough payment-boundary clarity to make reversible architecture decisions before product commitments harden into scope and operating debt.

**First product:** A 45-minute founder boundary session with a one-page payment-capability canvas and first-transaction evidence runway.

**Pilot gate:** One founder cohort can distinguish proposed, present, production-capable, and effective payment behavior before discussing validation direction.

**Reuse basis:** WACK-SERIES-0002, WACK-APPLICABILITY-0001, WACK-ROADMAP-0001

**Duplicate guard:** This is a facilitation wrapper over the Stealth Startup field guide, not a second startup technical series.

**Safety boundary:** No legal advice, investor diligence result, launch approval, automatic scope conclusion, or substitute for compliance-accepting-entity direction.

---

### W/ Finance — Finance teams, accounting students, internal audit, and reconciliation owners

**Reader problem:** The transaction reaches a ledger, settlement process, dispute queue, and evidence request, yet those owners are often absent from the payment architecture story.

**First product:** A from-transaction-to-ledger lab joining authorization, token or reference, settlement, reconciliation, exception, claim, and evidence ownership.

**Pilot gate:** A finance reader and a security reader can reconstruct the same fictional payment exception without relying on one another's oral history.

**Reuse basis:** WACK-CLAIM-TRACE-0001, WACK-CUTOFF-LAB-0001

**Duplicate guard:** Extend the claims-ledger and reconciliation methods; do not create a finance-only evidence store or accounting control framework.

**Safety boundary:** No accounting opinion, audit conclusion, control certification, financial-advice claim, or live transaction data.

## Research later

The need appears credible, but a domain reviewer, sharper boundary, or stronger reuse map is required before commissioning content.

### W/ Nonprofit — Nonprofits, associations, fundraising teams, and volunteer-led organizations

**Reader problem:** Donation pages, event readers, recurring gifts, outsourced platforms, volunteers, and seasonal operations can form a payment estate nobody sees as one system.

**First product:** A donation-journey kit covering web, event, phone, recurring, refund, volunteer, and provider handoffs.

**Pilot gate:** A nonprofit operator and payment provider reviewer confirm that the fictional journeys represent real operating patterns without oversimplifying eligibility.

**Reuse basis:** WACK-CHAMBER-0001, WACK-GUIDANCE-0001

**Duplicate guard:** Adapt the Main Street journey and responsibility tools; do not commission nonprofit-specific cases unless they materially change the operating story.

**Safety boundary:** No donor data, charitable-law advice, provider endorsement, SAQ selection, or treatment of volunteer status as a control.

---

### W/ Public Service — Municipalities, libraries, public institutions, and shared-service technology teams

**Reader problem:** Distributed counters, portals, departments, contractors, procurement paths, and shared infrastructure obscure ownership of the public payment estate.

**First product:** A public-service payment-estate map and procurement-to-operation responsibility workshop.

**Pilot gate:** A public-sector practitioner validates the fictional procurement, shared-service, records, and authority assumptions before a pilot is commissioned.

**Reuse basis:** WACK-CHAMBER-0001, WACK-GUIDANCE-0001, WACK-CLAIM-TRACE-0001

**Duplicate guard:** Reuse the payment-journey, provider, claim, and evidence models; do not create a public-sector compliance overlay without domain review.

**Safety boundary:** No procurement, records-retention, legal, or government-authority position; no real public-system architecture or incident facts.

---

### W/ Healthcare Payments — Healthcare payment, security, privacy, revenue-cycle, and patient-experience teams

**Reader problem:** Payment and healthcare workflows can share interfaces, identities, devices, vendors, and support paths without making one framework answer the other's questions.

**First product:** A dual-boundary fictional case that traces one patient payment across account-data, security-influence, privacy, support, and provider responsibility views.

**Pilot gate:** Healthcare security and privacy reviewers agree that the fictional case preserves separate authorities and does not imply equivalence.

**Reuse basis:** WACK-PT-RESEARCH-0001, WACK-APPLICABILITY-0001

**Duplicate guard:** Teach boundary interaction using the existing graph; do not merge PCI DSS with healthcare law or invent a universal cross-framework control map.

**Safety boundary:** No patient data, healthcare legal advice, HIPAA conclusion, framework equivalence, or assessment result.

---

### W/ ISV Academy — Independent software vendors, SaaS product teams, implementation partners, and customer-success leaders

**Reader problem:** An ISV can publish a strong product claim while leaving customers unable to distinguish software assurance, deployment responsibility, service coverage, and retained PCI duties.

**First product:** A customer-claim laboratory joining product capability, deployment pattern, provider assurance, customer configuration, evidence, and change responsibility.

**Pilot gate:** One product team and one customer implementation team can derive the same bounded responsibility statement from a fictional deployment.

**Reuse basis:** WACK-CONTENT-0119, WACK-CLAIM-TRACE-0001, WACK-PT-RESEARCH-0001

**Duplicate guard:** Turn the existing ISV field manual into a teachable customer-handoff lab; do not create a vendor certification or product listing.

**Safety boundary:** No product validation, vendor endorsement, compliance certificate, customer result, or substitution of marketing language for assessed facts.

---

### W/ Boardroom — Executives, boards, investors, and accountable business owners

**Reader problem:** Leadership receives compliance status but rarely sees the operating dependencies, decision authorities, missed occurrences, and evidence limitations underneath it.

**First product:** A 20-minute claims-and-consequences briefing built around one payment journey, five operating questions, and three decision requests.

**Pilot gate:** An executive reader can name the decision, owner, evidence limit, and reopening trigger without being taught PCI terminology first.

**Reuse basis:** WACK-ROADMAP-0001, WACK-CLAIM-TRACE-0001, WACK-CUTOFF-LAB-0001

**Duplicate guard:** Project existing approved material into an executive decision format; do not create another technical source or generic risk dashboard.

**Safety boundary:** No board assurance, investment advice, risk acceptance, compliance conclusion, or replacement for management and compliance-program authority.

---

_The Cluster of Wack is independent and is not affiliated with or endorsed by PCI SSC._