---
tool_id: WACK-TOOL-0001
concept_id: WACK-CONCEPT-0001
playbook_content_id: WACK-CONTENT-0020
status: draft
technical_review: pending
artifact_type: working_worksheet
---

# Cluster Mapping Canvas

> Get competing architecture stories into one visible, assignable fact model.

**Expected output:** A dated map of components, relationships, unknowns, owners, and verification actions.  
**Working time:** 90 minutes  
**Derived from:** WACK-CONTENT-0020

## Working context

Organization / environment: __________________________________________  
Facilitator / owner: __________________________________________________  
Participants: _________________________________________________________  
Date: ____________________  Review trigger or next date: ______________

## 01 / Find — Assemble the competing stories

Bring the records and people that currently describe the environment.

- [ ] **Which diagrams, inventories, scope records, exception lists, TPSP records, and evidence indexes are in use?**

  Notes: ________________________________________________

- [ ] **Which teams or owners would describe the same system differently?**

  Notes: ________________________________________________

## 02 / Map — Draw facts before conclusions

Represent observable components and relationships without deciding scope in advance.

- [ ] **What stores, processes, transmits, administers, authenticates, monitors, deploys, or can affect the environment?**

  Notes: ________________________________________________

- [ ] **Where are the trust boundaries, provider seams, shared services, and inherited dependencies?**

  Notes: ________________________________________________

## 03 / Explain — Name disagreement and uncertainty

Treat contradictions and unknowns as useful output.

- [ ] **Which relationship has conflicting explanations, and what evidence would resolve it?**

  Notes: ________________________________________________

- [ ] **Who owns the fact, the decision, and the next verification step?**

  Notes: ________________________________________________

## 04 / Reduce — Choose one simplification

Turn the shared model into a bounded reduction decision.

- [ ] **Which unnecessary path, duplicate label, stale record, or orphaned exception can be removed?**

  Notes: ________________________________________________

- [ ] **What is the safest sequence and rollback point for that change?**

  Notes: ________________________________________________

## 05 / Prove — Publish the baseline

Make the result usable after the meeting ends.

- [ ] **Where will the dated baseline and decision log live?**

  Notes: ________________________________________________

- [ ] **What trigger requires the map to be reviewed or changed?**

  Notes: ________________________________________________

## Completion check

- [ ] Every unknown has an owner and date.
- [ ] Every material relationship has a source or verification action.
- [ ] The team selected one concrete reduction move.

## Decision and next action

Decision: _____________________________________________________________  
Owner: __________________________  Due date: ___________________________  
Evidence or artifact location: ________________________________________

---

_Working practitioner worksheet pending technical review. It does not determine PCI DSS compliance, replace the standard, or replace instructions from an assessor or compliance-accepting entity. The Cluster of Wack is an independent resource and is not affiliated with or endorsed by PCI SSC._