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

# Diamond Fulcrum Formation Alignment Record

> Reconcile one consequential payment capability across authoritative facts, scope, applicability, implementation and responsibility, evidence, assessor testing, and change.

**Expected output:** A versioned formation record with one fact chain, four bounded position claims, owners and authority, contradictions, change fan-out, validation procedures, disposition, and reopening triggers.  
**Working time:** 75 minutes  
**Derived from:** WACK-CONTENT-0165

## Working context

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

## 01 / Find — Establish the fact fulcrum

Choose one payment capability and record its current asset, service, environment, data, identity, public presence, provider, configuration, responsibility, change, and occurrence facts with attributable sources and effective dates.

- [ ] **Which facts are directly observed, documented, asserted, or still unknown?**

  Notes: ________________________________________________

- [ ] **Which system owns each fact and its freshness?**

  Notes: ________________________________________________

## 02 / Map — Place four formation claims

Write separate Scope, Applicability, Implementation and Responsibility, and Evidence claims. Link every claim to exact facts, owner, authority, consumer, and contradiction.

- [ ] **Can every claim traverse to the same environment version?**

  Notes: ________________________________________________

- [ ] **Which claim depends on provider evidence or external direction?**

  Notes: ________________________________________________

## 03 / Explain — Define validation without transferring ownership

State the entity representation, the assessor procedure, the evidence population and period, the bounded validation result, and the conclusion that remains outside the record.

- [ ] **What does the entity own?**

  Notes: ________________________________________________

- [ ] **What must the assessor independently test?**

  Notes: ________________________________________________

## 04 / Reduce — Repair formation drift

Resolve copied conclusions, duplicate fact stores, ownerless responsibilities, stale evidence, and document-only updates. Preserve unresolved contradictions rather than forcing alignment in prose.

- [ ] **Which artifact is stale because one fact changed?**

  Notes: ________________________________________________

- [ ] **Which duplicate can become a deliberate projection?**

  Notes: ________________________________________________

## 05 / Prove — Fly one change maneuver

Inject or select one significant change. Identify every fact, claim, inventory, diagram, provider record, testing population, obligation, evidence contract, and report response that must reopen; then record test, disposition, and next trigger.

- [ ] **Which position moved first?**

  Notes: ________________________________________________

- [ ] **What proves all dependent positions moved with it?**

  Notes: ________________________________________________

## Completion check

- [ ] The fact chain is attributable, versioned, and separate from conclusions.
- [ ] Scope, Applicability, Implementation and Responsibility, and Evidence are four distinct claims joined to the same facts.
- [ ] Entity ownership and assessor validation are explicitly separated.
- [ ] Provider performance does not erase customer configuration, governance, evidence, testing, or change responsibilities.
- [ ] Contradictions remain visible until an accountable disposition resolves them.
- [ ] One significant change has been traced through every affected claim and downstream artifact.
- [ ] The record states its non-claims and reopening triggers.
- [ ] The aviation metaphor is labeled as independent practitioner analysis, not PCI SSC language or Navy doctrine.

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