# W/ Faculty Analytic Reasoning Rubric

This rubric evaluates the quality and reproducibility of reasoning. It does not calculate PCI DSS compliance, scope, eligibility, or professional qualification.

## Performance levels

- **Emerging** — Names isolated facts or conclusions but leaves the reasoning path mostly implicit.
- **Visible** — Makes the main facts and artifacts visible but leaves important joins or limitations unexplained.
- **Connected** — Connects facts, sources, owners, tests, and evidence with bounded reasoning and explicit uncertainty.
- **Defensible** — A cold reader can reproduce the reasoning, locate its authority, see its limits, and identify what reopens it.

# Six dimensions

## FACULTY-RUBRIC-01 · Behavior coverage

**Evaluate:** Does the work cover normal, alternate, failure, refund, support, and administrative behavior rather than only the happy path?

**Do not grade:** Do not award certainty merely because the diagram is visually polished.

## FACULTY-RUBRIC-02 · Relationship quality

**Evaluate:** Are account-data, connectivity, security influence, administration, provider, and change relationships explicit?

**Do not grade:** Do not reward a scope circle that hides why components were included or excluded.

## FACULTY-RUBRIC-03 · Authority discipline

**Evaluate:** Can the reader tell which statements come from published sources, organization assertions, assessor judgment, practitioner method, or student analysis?

**Do not grade:** Do not let citation count substitute for correct authority or applicability.

## FACULTY-RUBRIC-04 · Claim-to-proof fit

**Evaluate:** Does each cited artifact or test actually support the bounded subject, period, population, and proposition claimed?

**Do not grade:** Do not treat screenshots, reports, dashboards, or provider documents as self-authenticating.

## FACULTY-RUBRIC-05 · Uncertainty disclosure

**Evaluate:** Are assumptions, missing facts, contradictions, non-claims, and stopping points visible?

**Do not grade:** Do not punish a learner for refusing to invent a fact the case does not provide.

## FACULTY-RUBRIC-06 · Change propagation

**Evaluate:** When one fact changes, does the learner reopen every affected narrative, inventory, owner, test, evidence object, and claim?

**Do not grade:** Do not accept a change ticket as proof that dependent records remain current.

## Record

| Dimension | Level | Observable basis | Feedback | Retest |
| --- | --- | --- | --- | --- |
| Behavior coverage |  |  |  |  |
| Relationship quality |  |  |  |  |
| Authority discipline |  |  |  |  |
| Claim-to-proof fit |  |  |  |  |
| Uncertainty disclosure |  |  |  |  |
| Change propagation |  |  |  |  |

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