Critical Assessor Notice SWT3 witness anchors prove that specific operational controls were active at a specific point in time. They do not replace the assessor's independent judgment, professional expertise, or regulatory authority. Assessment determination ratings remain the assessor's responsibility. The portal is an evidence workbench, not an assessment engine.

Who This Guide Is For

You are an assessor, auditor, or reviewer who has received a share link from a client. The link looks like:

https://sovereign.tenova.io/audit/axm_audit_abc123...

Your client generated this link from their dashboard. It gives you read access to their compliance evidence and, depending on scope, the ability to enter findings, request evidence, and generate assessment reports. No account is required on your end.

Token Lifecycle Your share link has an expiration date (14, 30, or 90 days depending on your client's subscription tier). If your link stops working during an assessment, your client needs to generate a new one from their Settings page. The client can also revoke links at any time. If you receive a 403 error, contact your client for a fresh link.

1. What You Are Looking At

When you open the portal, you see a single-page evidence dashboard organized into sections. A sticky table of contents on the left lets you jump to any section. The sections that appear depend on two factors:

If you need data that is not visible in your portal, your client may need to generate a new link with a broader scope or with specific articles included.

Scoped Portals Your client can scope your token to specific articles or requirements (for example, only Art. 9, Art. 10, and Art. 13 of the EU AI Act). If your portal shows a subset of the full control set, this is intentional. All KPIs, counts, and scores are recalculated to reflect only the scoped data. Ask your client if you need a broader view.

2. Reading the Score Cards

The top of the portal shows three headline metrics:

MetricWhat It MeansWhat You Should Do
Sovereign Score Aggregate posture percentage. Passing controls divided by total controls (excluding inherited). This is a coverage signal, not a compliance determination. Use as a triage indicator. A score below 80% suggests significant gaps. Do not cite this score as a compliance finding; it is an internal metric.
Gate Decision PASS, WARN, or BLOCK. The automated gate decision based on the client's configured policy. PASS means all configured thresholds are met. WARN means marginal. BLOCK means the client's own gate would prevent deployment. A BLOCK gate decision with no corresponding remediation activity is a signal worth investigating. A PASS gate does not mean your assessment should pass.
Control Counts Passing / Failing / Inherited / Total. Inherited controls are satisfied by the infrastructure provider (with evidence of that inheritance documented). Focus your assessment on the non-inherited controls. Verify inherited controls have valid provider attestation (SOC 2 report, shared responsibility matrix) by expanding the inheritance detail in the control matrix.

3. Control Matrix

The control matrix is the core evidence table. Each row represents a procedure with its current verdict and evidence chain.

Columns

ColumnDescription
Procedure IDThe UCT procedure identifier (e.g., AI-GRD.1, SC-7.6). Color-coded by verdict.
FamilyThe control family (e.g., SC, AC, AI).
TitleHuman-readable procedure name.
VerdictPASS FAIL INHERITED UNKNOWN
Last WitnessedWhen this procedure was last evaluated. Stale evidence (older than your assessment window) should be noted.
SeverityCAT I / CAT II / CAT III (from POA&M, if applicable).
Days OpenHow long a FAIL verdict has been unresolved.
SWT3 AnchorThe cryptographic witness anchor. Click to copy. Verify at sovereign.tenova.io/verify.

Filtering and Sorting

Evidence Summary

Each control row includes a human-readable evidence summary. For example:

SC-7.6 (Boundary Protection) The system enforces network segmentation with 3 firewall zones deployed.

These summaries are generated from the witness factors and describe what was measured. They are not assessor conclusions.

Assessment Objectives

Expand any control row to see linked NIST 800-53A assessment objectives. Each objective shows:

Coverage Does Not Mean Compliance FULL coverage means the SWT3 evidence addresses this assessment objective. It does not mean the objective is satisfied. You must evaluate whether the evidence is sufficient, appropriate, and relevant to the specific assessment context.

Inherited Controls

Controls with an INHERITED verdict include provider details when expanded:

4. Framework-Specific Sections

EU AI Act Conformity

If your client's primary framework is the EU AI Act, the portal shows an article-level conformity section. Each article (Art. 9, 10, 13, 14, 15, etc.) displays:

The Annex IV checklist section tracks technical documentation completeness across 15 sections. You can update section status, add reviewer notes, and score each section 0-10 with evidence quality ratings.

CMMC and NIST 800-53

If your client's primary framework is CMMC or NIST 800-53, the portal organizes evidence by control families (AC, AU, CM, SC, etc.). Each family card shows:

The control matrix includes STIG severity (CAT I / CAT II / CAT III), days open for FAIL controls, and POA&M milestone tracking. Expand any control to see linked NIST 800-53A assessment objectives with TEST/INTERVIEW/DOCUMENT_REVIEW method indicators.

ISO 42001 and Other Frameworks

For ISO 42001, NIST AI RMF, SR 11-7, and other frameworks, the portal shows a requirement-level assessment. Each requirement group displays conformity percentages, status indicators (COMPLIANT / MONITOR / ACTION_REQUIRED), and corrective actions prioritized by gap severity. The structure adapts to each framework's native organization (clauses for ISO, functions for NIST AI RMF, sections for SR 11-7).

5. Entering Findings

The Findings Register is where you document your assessment observations. This is your working record within the portal.

Creating a Finding

  1. Scroll to the Findings section (or click it in the table of contents).
  2. Enter your observation text. Be specific: reference the article, requirement, or procedure.
  3. Select a severity:
    • MAJOR: Non-conformity that affects the ability of the management system or product to achieve its intended outcomes. Requires corrective action before certification/authorization.
    • MINOR: Non-conformity that does not affect the ability to achieve intended outcomes but should be addressed. Corrective action within a defined timeline.
    • OBSERVATION: An area for improvement that is not a non-conformity. No corrective action required but recommended.
  4. Optionally link the finding to a specific procedure ID (e.g., AI-GRD.1).
  5. Optionally attach SWT3 anchor references as evidence citations.
  6. Save. The finding is created with status OPEN.

Updating Findings

As the assessment progresses, update finding status:

StatusMeaning
OPENFinding documented, not yet addressed.
REMEDIATIONClient is actively working on corrective action.
RESOLVEDCorrective action completed and verified by assessor.
ACCEPTEDFinding acknowledged and accepted (risk acceptance).

Every status change, severity change, and observation edit is logged in the portal's audit trail with your assessor identity and timestamp.

Bulk Import

If you have findings prepared in a spreadsheet, you can submit them as a batch via the bulk import endpoint. Prepare a CSV with columns: observation, severity, procedure_id, swt3_anchors. Up to 100 findings per batch. See your client's technical team or the Assessor Onboarding Kit for API details.

6. Evidence Requests and Interviews

Evidence Requests

When you need supplementary evidence beyond what the portal provides, create an evidence request:

Remember: SWT3 anchors cover TEST-method assessment objectives. INTERVIEW and DOCUMENT_REVIEW objectives require traditional evidence collection. The portal's assessment objectives display (Section 3) shows which objectives need manual evidence.

Interviews

Log interview sessions with date, interviewer identity, and linked procedures. Notes are stored in the portal's audit trail and appear in exported reports.

7. Peer Review

For multi-assessor teams, the Review Panel supports structured peer review:

8. Statistical Sampling

For large control sets, the Sampling section helps you select a statistically representative subset for deep review. The portal provides:

For detailed sampling methodology, see the Assessor Sampling Instructions.

9. Full-Scope Sections

If your token has full scope, additional sections appear. These provide deeper forensic and operational evidence for AI system assessments:

Agent Transparency (Art. 13/14)

Per-agent statistics: models used, tools called, procedures witnessed, clearing levels, total inferences, pass rates, violation counts, and first/last seen timestamps. Use this to verify that all AI agents in the system boundary are accounted for and governed.

Decision Chains

Multi-step inference sequences grouped by cycle_id. Each chain shows start time, end time, duration, and whether any violations occurred. Use this to verify that complex AI workflows (multi-agent, multi-step) are fully witnessed from initiation to completion.

Lifecycle Chains

Governance lifecycle sequences: deployment, escalation, resolution, abandonment. Each chain shows stage progression, parent-child anchor integrity, and terminal state. Use this to verify that governance events (emergency overrides, model updates, incident responses) follow documented procedures.

Hardware Attestation

Per-node compute details: silicon vendor, topology, accelerators, attestation count, and freshness. A stale attestation (older than 2 hours) is flagged. Use this to verify that the physical infrastructure matches the client's documented system boundary.

Merkle Integrity Proofs

Daily cryptographic roots proving that the ledger has not been tampered with. Each day shows the number of anchors and whether any FAIL verdicts were recorded. Use this to verify append-only integrity of the evidence chain.

10. Generating Reports

The portal offers several export formats. All exports include a report-level SWT3 anchor for tamper detection.

FormatUse CaseContents
Conformity Report (HTML) Primary assessment deliverable Executive summary, article/requirement-level conformity, findings summary, technical documentation status, corrective actions, recommended outcome (PASS/FAIL), report anchor
Conformity Report (JSON) Integration with assessment body systems Structured schema (swt3-assessment-report v1.0.0) with all report data
Certificate (HTML) Formal declaration document EU Declaration of Conformity or Compliance Assessment certificate with signature blocks, article table, findings summary
Work Papers (PDF) Traditional audit work papers KPI cards, open findings, POA&M summary, evidence sample with anchors. Print to PDF via browser.
Controls Matrix (CSV) Spreadsheet analysis Procedure ID, family, title, verdict, severity, days open, overdue status, last witnessed date, SWT3 anchor
Portal Data (JSON) Full data export for offline analysis Complete portal response including verdicts, controls, findings, anchors, conformity assessment, chains

Report Coherence Validation

Before rendering any report, the portal runs a coherence check. It detects contradictions such as:

Contradictions appear as warnings in the report banner. They do not block export but they flag areas where your findings and the automated evidence diverge. Investigate each warning before finalizing your report.

11. Verifying Anchors Independently

Every SWT3 anchor in the portal can be independently verified. This is the core integrity guarantee: you do not need to trust the portal display.

  1. Copy any anchor from the control matrix (click the copy icon).
  2. Open sovereign.tenova.io/verify in a new tab. No account required.
  3. Paste the anchor. The verifier checks the SHA-256 fingerprint against the witness ledger.
  4. Result: VALID (anchor exists and is untampered), REVOKED (anchor was later revoked with a reason code), or NOT FOUND.

For a detailed verification walkthrough including manual SHA-256 recomputation, see the Assessor Onboarding Kit.

Assessment Window When citing SWT3 anchors in your assessment report, always document the assessment window: the date range of anchors you reviewed. SWT3 evidence is continuous, not point-in-time. An anchor from three months ago may not reflect the current state. Filter the control matrix by "Last Witnessed" date to ensure your evidence falls within your assessment period. For formal temporal scope guidance (minimum coverage thresholds, gap handling, FAIL-to-PASS timelines), see the NB QMS Integration Guide, Section 12.

12. Common Issues

ProblemCauseResolution
403 Forbidden Token expired, revoked, or malformed Contact your client for a new share link.
Missing sections Token scope is basic, or token is scoped to specific articles Ask your client to generate a full-scope token if you need agent transparency, lifecycle chains, or hardware attestation.
429 Too Many Requests Rate limit exceeded (10 requests/minute for data, 20 for findings, 5 for reports) Wait 60 seconds and retry. Rate limits protect the evidence integrity pipeline.
"No data" on AI sections Client has not integrated AI witness SDK yet Not an error. AI witness sections only appear when the client has instrumented their AI systems. Infrastructure controls may still have full evidence.
Exports blocked Demo portal (DEMO_ tenant) Demo portals do not support exports. Create a free account or use a client-issued share link.