SWT3 Auditor Display Standard

This guide is the practical companion to SWT3-SPEC Section 23 (Auditor Display Requirements) and Section 24 (Conformity Evidence Package). It provides reference CSS, worked examples, anti-patterns, and a conformity checklist for any tool that renders SWT3 Witness Anchors to human assessors.

The normative source of truth is the SWT3-SPEC. This guide is informative.

1. Single Anchor Decomposition

When an assessor examines a single anchor, the display MUST decompose all nine required fields (Section 23.1). Here is a conforming example:

Key requirements: Full anchor untruncated in monospace. Verdict has semantic color (green = PASS). Timestamp in ISO 8601 UTC. Fingerprint in monospace lowercase, all 12 characters visible. Verification link requires no account or authentication.

2. Tabular Multi-Anchor Display

When rendering multiple anchors, columns 1-2 MUST appear in the specified order. Columns 3-4 MUST be present but MAY appear in either order (Section 23.6):

Additional columns (Signature, Chain ID, Agent, etc.) MAY be appended after column 4. Columns 1 (Procedure) and 2 (Verdict) are locked.

3. Evidence Bundle Header

SDK-generated evidence bundles include a watermark tier (Section 23.7). The watermark MUST be visible without scrolling:

4. Non-Conforming Displays

The following examples violate Section 23 requirements. Any of these patterns disqualifies a display from the "SWT3 Verified Display" conformity statement.

4.1 Truncated Fingerprint (violates Section 23.3)

4.2 Wrong Verdict Color (violates Section 23.2)

4.3 Raw Epoch Timestamp (violates Section 23.5)

4.4 No Verification Affordance (violates Section 23.4)

4.5 Reordered Columns (violates Section 23.6)

5. Reference CSS Snippet

Copy this CSS into any tool to achieve a conforming display. All classes are prefixed with swt3- to avoid collisions.

/* SWT3 Auditor Display Standard -- Reference CSS */
/* Conforms to SWT3-SPEC Section 23 (v1.0.1)     */

.swt3-anchor-full {
  font-family: 'SF Mono', 'Fira Code', 'Consolas', monospace;
  font-size: 11pt; font-weight: 700; color: #0f172a;
  word-break: break-all;
}
.swt3-fingerprint {
  font-family: 'SF Mono', 'Fira Code', 'Consolas', monospace;
  font-size: 10pt; color: #334155;
  letter-spacing: 0.5px; text-transform: lowercase;
  white-space: nowrap;
}
.swt3-verdict-pass {
  display: inline-block; background: #16a34a; color: #fff;
  font-size: 9pt; font-weight: 700; padding: 2px 10px;
  border-radius: 3px; text-transform: uppercase;
}
.swt3-verdict-fail {
  display: inline-block; background: #dc2626; color: #fff;
  font-size: 9pt; font-weight: 700; padding: 2px 10px;
  border-radius: 3px; text-transform: uppercase;
}
.swt3-verdict-inherited {
  display: inline-block; background: #2563eb; color: #fff;
  font-size: 9pt; font-weight: 700; padding: 2px 10px;
  border-radius: 3px; text-transform: uppercase;
}
.swt3-timestamp {
  font-size: 10pt; color: #64748b;
}
.swt3-provenance-local {
  display: inline-block; background: #f59e0b; color: #fff;
  font-size: 9pt; font-weight: 700; padding: 4px 14px;
  border-radius: 3px;
}
.swt3-provenance-cloud {
  display: inline-block; background: #16a34a; color: #fff;
  font-size: 9pt; font-weight: 700; padding: 4px 14px;
  border-radius: 3px;
}
.swt3-provenance-hardware {
  display: inline-block; background: #b45309; color: #fff;
  font-size: 9pt; font-weight: 700; padding: 4px 14px;
  border-radius: 3px;
}
.swt3-verify-link {
  font-size: 9pt; color: #2563eb; text-decoration: underline;
}

/* Print: ensure text labels accompany color badges */
@media print {
  .swt3-verdict-pass::after { content: ' PASS'; }
  .swt3-verdict-fail::after { content: ' FAIL'; }
  .swt3-verdict-inherited::after { content: ' INHERITED'; }
}

6. Self-Assessment Checklist

A tool that passes all 12 checks MAY display the SWT3 Verified Display conformity statement. Failing any single check disqualifies the tool.

1. 1Full anchor token displayed in monospace, untruncated. Section 23.1, field #1
2. 2All 9 required fields present in the specified order (anchor, protocol, tier, provider, domain, procedure, verdict, timestamp, fingerprint). Section 23.1
3. 3PASS verdict uses green color family (HSL hue 100-160). FAIL uses red (340-20). Colors are visually distinct. Cultural hue-range swap permitted if text labels are present and PASS/FAIL remain distinguishable. Section 23.2
4. 4Verdict badges include text labels (not color-only) for print and accessibility. Section 23.2
5. 5Fingerprints rendered in monospace, lowercase, all 12 characters visible, no truncation, no word-wrap. Section 23.3
6. 6At least one verification affordance present: public link, inline command, or client-side recomputation. No account required. Section 23.4
7. 7Timestamps in ISO 8601 with UTC indicator. No raw epoch integers without human-readable conversion. Section 23.5
8. 8Tabular displays: Procedure (column 1) and Verdict (column 2) are REQUIRED positions. Witnessed and Fingerprint MUST be present but MAY appear in either order. Section 23.6
9. 9Evidence provenance indicator (LOCAL ONLY / CLOUD VERIFIED / HARDWARE ATTESTED) displayed when present in metadata. Section 23.7
10. 10Conformity Evidence Packages display: metadata, summary, gate decision, Merkle root (if present), package hash, and individual anchor decomposition. Section 23.8
11. 11Extensions do not alter order, format, or semantics of required fields. Section 23.9
12. 12Non-conforming displays do not claim "SWT3 Verified Display" or any variation implying conformity. Section 23.10

7. Conformity Statement

Tools that pass all 12 checks MAY display this statement:

This is a text mark. A graphical badge is not defined in this version of the specification. The conformity statement MUST NOT be modified, abbreviated, or paraphrased.

8. Conformity Evidence Package Format

Section 24 of the SWT3-SPEC defines a portable JSON format for evidence packages. Any tool can produce one; any assessor tool can consume one. The minimum conforming package:

{
  "_meta": {
    "format": "swt3-conformity-evidence-package",
    "version": "1.0",
    "framework": "NIST-800-53",
    "generatedAt": "2026-08-11T14:30:00Z",
    "generator": "axiom-sovereign-engine/5.42.0",
    "tenantId": "tenant_uuid",
    "tenantName": "ACME Defense Corp"
  },
  "summary": {
    "totalProcedures": 113,
    "passing": 95,
    "failing": 3,
    "inherited": 9,
    "complianceRate": 84.1,
    "gateDecision": "PASS"
  },
  "anchors": [
    {
      "token": "SWT3-E-VULTR-AI-AIINF1-PASS-1774800000-2e16e2fe92dd",
      "procedureId": "AI-INF.1",
      "verdict": "PASS",
      "epoch": 1774800000,
      "fingerprint": "2e16e2fe92dd",
      "factorA": 1,
      "factorB": 0,
      "factorC": 2500
    }
  ],
  "merkle": {
    "root": "c22dcec3e8aa9a68...",
    "rollupDate": "2026-08-11",
    "anchorCount": 390,
    "algorithm": "SWT3-DOMAIN-SEPARATED-SHA256"
  },
  "packageHash": "a1b2c3d4e5f6..."
}

The packageHash is computed as SHA-256 of the canonical JSON with packageHash set to "". Assessors SHOULD verify this hash before trusting the package. See SWT3-SPEC Section 24 for the full schema.