W/?W/!W/✓

W/ML v0.1 / PRACTICE RELEASE

Stop admiring the grammar. Use it.

Exercise W/ML in three bounded working contexts before the draft language is treated as stable.

Download complete lab data

THREE CONTEXTS / ONE BOUNDED LANGUAGE

Put the notation under pressure.

Exercise W/ML in three bounded working contexts before the draft language is treated as stable.

12 minutes

Follow an omitted workload into dependent claims

Reconcile one service that appears in runtime evidence but not in the maintained inventory or diagram.

Download practice file
01W/![INVENTORY]{asset=PAY-API-07}

Runtime evidence confirms that PAY-API-07 exists while the maintained inventory omits it.

02W/?[SCOPE]{asset=PAY-API-07}

The omission creates a scope question; the notation does not answer it.

03W/?[CONTROL]{requirement=1.2.4}

Control applicability and coverage must be evaluated against the actual architecture.

04W/?[EVIDENCE]{source=NETWORK_DIAGRAM}

The diagram evidence can no longer be relied upon without reconciliation.

WORKING CLUSTERW/{INVENTORY → SCOPE → CONTROL → EVIDENCE}!

Read this as an investigation boundary. The cluster does not create a finding or decide applicability.

DEBRIEF / DO NOT SKIP THE QUESTIONS

  1. Which source first established that the workload exists?
  2. Which downstream claims depended on the incomplete inventory?
  3. What evidence would support a bounded W/✓ disposition?

REFERENCE IMPLEMENTATION

The Wack Engine starts narrow.

./scripts/wack lint FILE.wml

Validate grammar and report bounded notices without judging PCI DSS compliance.

./scripts/wack explain FILE.wml

Translate each parsed expression into plain practitioner language.

./scripts/wack cluster FILE.wml

Report explicit clusters and connected object sets without producing a score or finding.

The lab describes observations and relationships. It does not determine PCI DSS applicability, produce an assessment result, assign risk, or decide compliance acceptance.

Search