# Turn Assertions Into Attributable Claims

**Session:** FACULTY-SESSION-02  
**Duration:** 75 minutes  
**Program:** WACK-FACULTY-0001

## Learning objective

Students can distinguish observed facts, documented statements, asserted interpretations, validated results, and unresolved questions.

## Reviewed pre-reading

- WACK-CONTENT-0156
- WACK-CONTENT-0157
- WACK-CONTENT-0129

## Opening provocation

> The provider says it is compliant. Which university claim did that sentence actually prove?

## Activity

Teams classify statements by authority and reconcile Expected, Observed, Documented, Asserted, and Validated states.

## Student artifact

A claim-evidence-authority matrix with explicit non-claims and unresolved contradictions.

## Misconception to surface

A source with more institutional authority automatically proves every implementation claim.

## Facilitator stop

Stop any answer that uses assessor judgment, provider assurance, or a dashboard result without naming its subject and limitation.

## Exit ticket

Rewrite one absolute conclusion as a bounded claim that identifies subject, period, source, and authority.

## Authority boundary

W/ Faculty is independent practitioner education and a public pilot. It is not PCI SSC guidance or official PCI SSC training. It is not an accredited curriculum, a certification program, an assessor qualification, an eligibility decision, a grading mandate, or a compliance result. It is not a PCI DSS assessment and does not substitute for assessor judgment, organizational policy, or compliance-accepting-entity direction. Use only fictional or explicitly sanitized environments. Never enter account data, credentials, provider secrets, client evidence, restricted architecture, student records, or targets the class is not authorized to test.