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

# PCI DSS v4 Flywheel Continuity Ledger

> Turn annual assessment reconstruction into a living, traversable operating loop across ten connected PCI disciplines.

**Expected output:** A continuity ledger connecting one bounded assessment claim to payment and data-flow boundaries, cross-referenceable inventory, responsibility and authority, time-based obligations, control execution, evidence lineage, testing, exceptions, change reconciliation, and claim disposition.  
**Working time:** 150 minutes  
**Derived from:** WACK-CONTENT-0126

## Working context

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

## 01 / Find — Locate the stopped spokes

Inventory the current records, systems, owners, cadences, evidence, tests, exceptions, changes, and claims used across the assessment period.

- [ ] **Where does one operating fact have to be manually re-entered or reinterpreted?**

  Notes: ________________________________________________

- [ ] **Which spoke exists only because the assessor asks for it?**

  Notes: ________________________________________________

## 02 / Map — Connect the ten-spoke loop

Give every subject and occurrence a durable key, then connect it to the central claim and every affected spoke.

- [ ] **Can one asset be traversed through scope, ownership, operation, evidence, testing, exception, change, and claim?**

  Notes: ________________________________________________

- [ ] **Which record should reopen when this fact changes?**

  Notes: ________________________________________________

## 03 / Explain — Separate facts, methods, and decisions

Classify PCI SSC source language, entity representations, provider statements, assessor judgment, practitioner methods, and accepting-entity decisions.

- [ ] **Who has authority to make this statement?**

  Notes: ________________________________________________

- [ ] **Does the statement cover the same subject, service, version, and period as the evidence?**

  Notes: ________________________________________________

## 04 / Reduce — Remove rotational drag

Retire duplicate stores, silent translations, orphaned tasks, stale exceptions, and broad claims that prevent operating facts from circulating.

- [ ] **Which manual join can become stable metadata or emitted evidence?**

  Notes: ________________________________________________

- [ ] **Which record survives only because another record is incomplete?**

  Notes: ________________________________________________

## 05 / Prove — Complete one full rotation

Trace one component, one obligation, one change, one exception, and one claim around all ten spokes and preserve every unresolved break.

- [ ] **Can another qualified person reproduce the traversal?**

  Notes: ________________________________________________

- [ ] **Would the system keep turning if the assessment date moved by six months?**

  Notes: ________________________________________________

## Completion check

- [ ] The central claim identifies its entity, environment, payment channel, services, period, standard or program, and compliance-accepting party.
- [ ] Every material subject has a stable identifier shared across scope, inventory, ownership, controls, evidence, tests, exceptions, changes, and claims.
- [ ] Recurring obligations preserve expected and actual occurrence histories, including misses, failures, corrections, and evidence.
- [ ] Material changes reopen every affected spoke instead of updating only a ticket or diagram.
- [ ] One complete end-to-end traversal can be reproduced without waiting for the assessor to reconstruct it.

## 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._