About This Document This is a reference example showing how assessment bodies can incorporate SWT3 witness evidence into conformity assessment reports per EU AI Act Article 43. All organization names, personnel, and anchor fingerprints are fictional. Procedure IDs reference the public UCT Registry. Adapt this format to your organization's QMS and reporting requirements.
This Is Not a Real Assessment This document is illustrative. It does not certify, approve, or endorse any product or system. It demonstrates a citation format, not an assessment outcome. Do not present this document as evidence of any compliance status.

Report Cover Page

Conformity Assessment Report

EU Artificial Intelligence Act

High-Risk AI System -- Third-Party Conformity Assessment per Article 43(1)

Provider Under Assessment: Exemplar Financial AI Ltd.

AI System: AutoLend v3.2 (Credit Decision Engine)

Risk Classification: High-Risk (Annex III, Area 5(b) -- Creditworthiness)

Assessment Body: European AI Conformity Partners GmbH

Notified Body ID: NB-2847 (Fictional)

Assessment Standard: EN ISO/IEC 42001:2023 + EU AI Act Annex VI

Report ID: EACP-2026-0847

Report Date: 2026-10-10

Assessment Window: 2026-08-01 through 2026-10-08

1. Executive Summary

Scope of Assessment

This assessment evaluates the conformity of AutoLend v3.2 with EU Regulation 2024/1689 (the AI Act) requirements for high-risk AI systems. AutoLend is a credit decision engine used by three European financial institutions to evaluate consumer creditworthiness under Annex III, Area 5(b).

The assessment covers Articles 9 (Risk Management), 10 (Data Governance), 13 (Transparency), 14 (Human Oversight), and 15 (Accuracy, Robustness, and Cybersecurity). Technical documentation was evaluated against Annex IV requirements.

Evidence Sources

This assessment relied on three categories of evidence:

  1. Cryptographic witness evidence (SWT3): 23 SWT3 witness anchors covering 18 procedures, assessed via the audit portal (share link token, 70-day assessment window). Each anchor was independently verified using SHA-256 fingerprint recomputation.
  2. Document review: Risk management policy (v2.1, dated 2026-06-15), data governance procedures, model validation reports, incident response plan, and Annex IV technical documentation package.
  3. Interviews: 4 sessions with the Chief AI Officer, Head of Model Risk, Data Protection Officer, and the AutoLend development team lead. Interview notes on file (ref: EACP-INT-0847-01 through 04).

Overall Outcome

CONDITIONAL PASS. 4 of 5 assessed articles are conforming. One minor non-conformity identified on Article 13 (Transparency) requiring corrective action within 90 days. Reassessment of Art. 13 scheduled for January 2027.

MetricValue
Procedures Assessed18
Conforming15
Non-Conforming (Minor)1
Observations2
SWT3 Anchors Verified23 (5 independently recomputed)
Assessment Window2026-08-01 through 2026-10-08 (70 days)

2. Assessment Methodology

Assessment Framework

This assessment was conducted per the documented procedure EACP-QMS-P-012 "Conformity Assessment of AI Systems Using Cryptographic Evidence" (Rev 1.0, effective 2026-07-01), within the scope of NB-2847's ISO/IEC 17065 accreditation.

SWT3 Evidence Verification Method

SWT3 witness anchors were verified using a two-step process:

  1. Portal verification: All 23 anchors were checked via the public verifier at sovereign.tenova.io/verify. Each returned VALID (anchor exists, fingerprint matches, no revocation).
  2. Independent recomputation (5 anchors): Five anchors were selected for manual SHA-256 fingerprint recomputation using the formula published in the SWT3 Protocol Specification. All five matched. The recomputation was performed using the assessor's own tooling (OpenSSL 3.x), not the provider's software.

Interoperability Verification

The SWT3 fingerprint formula is implemented in 7 independent SDK implementations (Python, TypeScript, Rust, C#, Ruby, Swift, Go) and verified against a shared test vector suite. Independent recomputation (Step 2 above) used OpenSSL 3.x, which is not an SWT3 SDK implementation, confirming that the formula is reproducible using standard cryptographic tools without vendor dependency.

Temporal Scope

The assessment window was defined as 2026-08-01 through 2026-10-08 (70 days). Only anchors with epoch timestamps within this window were considered as primary evidence. Of the 18 procedures assessed, 16 had continuous anchor coverage (at least one anchor per 7-day period). Two procedures (AI-DATA.1 and AI-FAIR.1) had intermittent or absent coverage, which is documented in the Article 10 findings below.

Evidence Sufficiency Determination

SWT3 anchors were accepted as sufficient evidence for TEST-method assessment objectives per NIST 800-53A methodology. INTERVIEW and DOCUMENT_REVIEW objectives were assessed through traditional methods as documented in this report. Where SWT3 evidence and interview evidence covered the same objective, both sources were considered. Discrepancies between SWT3 verdicts and assessor findings are documented in the relevant article section.

3. Article-Level Findings

Article 9 -- Risk Management System

Finding: CONFORMING The provider maintains a continuous risk management system that identifies, evaluates, and mitigates risks from the AI system. The risk management policy (v2.1) was reviewed and found to address Art. 9(2)(a) through (d). Testing of known and foreseeable risks is documented through guardrail monitoring.

SWT3 Evidence Cited

ProcedureAnchorVerifiedWitness Date
AI-GRD.1 (Guardrail Enforcement) SWT3-E-VULTR-AI-AIGRD1-PASS-1791532800-a7c3e91f02b4 VALID (recomputed) 2026-10-05
AI-GRD.2 (Guardrail Coverage) SWT3-E-VULTR-AI-AIGRD2-PASS-1791446400-d12f8b6c4e91 VALID 2026-10-04
AI-SAFE.1 (Safety Classification) SWT3-E-VULTR-AI-AISAFE1-PASS-1791360000-e8f2a7b10c34 VALID 2026-10-03

Assessor notes: Art. 9(9) requires continuous iteration of the risk management system. The SWT3 evidence demonstrates continuous monitoring over the 70-day assessment window (23 anchors across 18 procedures). This continuous evidence pattern satisfies Art. 9(9) more robustly than periodic manual reviews.

Supplementary evidence: Interview with Head of Model Risk (EACP-INT-0847-02) confirmed quarterly risk review cadence and escalation procedures for model drift events.

Article 10 -- Data and Data Governance

Finding: OBSERVATION (OBS-001) Data governance practices are established and documented. Training data provenance is tracked. However, the provider has not yet implemented systematic bias detection across all protected characteristics. Bias monitoring for age and gender is active; disability status and ethnicity monitoring is planned for Q1 2027.

SWT3 Evidence Cited

ProcedureAnchorVerifiedWitness Date
AI-DATA.1 (Data Provenance) SWT3-E-VULTR-AI-AIDATA1-PASS-1790841600-b3d7f2e8a190 VALID (recomputed) 2026-09-28
AI-FAIR.1 (Bias Detection) Not witnessed during assessment window.

Assessor notes: AI-DATA.1 anchor confirms data provenance tracking is operational. The absence of an AI-FAIR.1 anchor is consistent with the provider's statement that comprehensive bias monitoring is not yet deployed. This is documented as an observation rather than a non-conformity because Art. 10(2)(f) requires "examination in view of possible biases" and the provider demonstrates partial coverage with a documented remediation plan.

Supplementary evidence: Data governance procedure document (DGP-2026-v2, section 4.3) reviewed. Interview with Data Protection Officer (EACP-INT-0847-03) confirmed bias detection roadmap.

Article 13 -- Transparency and Provision of Information to Deployers

Finding: MINOR NON-CONFORMITY (NC-001) The provider has implemented agent identification (AI-ID.1) and model identification is present in all inference responses. However, Art. 13(3)(d) requires that deployers be informed of "the level of accuracy, robustness, and cybersecurity" with metrics and validation results. The provider's deployer documentation does not include quantitative accuracy metrics or validation methodology. The technical documentation (Annex IV, Section 5) references internal benchmark results but does not make these available to deployers.

SWT3 Evidence Cited

ProcedureAnchorVerifiedWitness Date
AI-ID.1 (Agent Identification) SWT3-E-VULTR-AI-AIID1-PASS-1791100800-c4a8f7e2d301 VALID (recomputed) 2026-10-01
AI-EXPL.1 (Explainability) SWT3-E-VULTR-AI-AIEXPL1-PASS-1791187200-f9b2c6e1a478 VALID 2026-10-02

Assessor notes: The SWT3 evidence confirms that agent identification and explainability mechanisms are operational. However, operational evidence of system transparency does not satisfy the documentation obligation under Art. 13(3)(d). The provider must update deployer-facing documentation to include quantitative performance metrics.

Corrective action required: Update deployer documentation to include accuracy benchmarks, robustness test results, and cybersecurity assessment outcomes. Provide this documentation to all current deployers. Deadline: 90 days (2027-01-08).

Supplementary evidence: Deployer documentation package reviewed (AutoLend Integration Guide v3.2). Interview with development team lead (EACP-INT-0847-04) confirmed benchmarks exist internally but are not distributed.

Article 14 -- Human Oversight

Finding: CONFORMING Human oversight measures are implemented and operational. The credit decision engine operates with human-in-the-loop review for decisions exceeding a configurable risk threshold. Override capabilities are documented and tested.

SWT3 Evidence Cited

ProcedureAnchorVerifiedWitness Date
AI-HITL.1 (Human Override) SWT3-E-VULTR-AI-AIHITL1-PASS-1791014400-e7d3b8f2a156 VALID 2026-09-30
AI-HITL.2 (Override Effectiveness) SWT3-E-VULTR-AI-AIHITL2-PASS-1790928000-a2c9e4f7b831 VALID (recomputed) 2026-09-29

Supplementary evidence: Interview with Chief AI Officer (EACP-INT-0847-01) confirmed override authority structure. Override audit log reviewed (12 overrides in assessment window, all documented with justification).

Article 15 -- Accuracy, Robustness, and Cybersecurity

Finding: CONFORMING The system demonstrates accuracy within declared performance boundaries. Robustness testing is documented. Cybersecurity measures are in place.
OBSERVATION (OBS-002) While robustness procedures are in place, adversarial testing (AI-ROBUST.1) has been performed only against known attack vectors. The assessor recommends expanding adversarial testing to include emerging model extraction and data poisoning techniques relevant to financial AI models.

SWT3 Evidence Cited

ProcedureAnchorVerifiedWitness Date
AI-ROBUST.1 (Robustness Testing) SWT3-E-VULTR-AI-AIROBUST1-PASS-1790755200-f1a6c3d9e247 VALID 2026-09-27
AI-PERF.1 (Performance Monitoring) SWT3-E-VULTR-AI-AIPERF1-PASS-1790668800-b8e2f4a7c130 VALID (recomputed) 2026-09-26

4. Corrective Actions Register

IDArticleSeverityDescriptionDeadlineResponsible
NC-001 Art. 13 MINOR Update deployer documentation to include quantitative accuracy, robustness, and cybersecurity metrics per Art. 13(3)(d). 2027-01-08 Head of Product, Exemplar Financial AI

Observations (No Corrective Action Required)

IDArticleDescriptionRecommendation
OBS-001 Art. 10 Bias detection covers age and gender but not all protected characteristics. Expand bias monitoring to disability status and ethnicity before Q2 2027.
OBS-002 Art. 15 Adversarial testing limited to known attack vectors. Expand to emerging techniques (model extraction, data poisoning) relevant to financial AI.

5. Evidence Verification Log

Five SWT3 anchors were selected for independent SHA-256 fingerprint recomputation. Selection criteria: one anchor per assessed article, prioritizing the most recent anchor for each.

ProcedureAnchor (Truncated)Verification MethodResultVerified On
AI-GRD.1 ...a7c3e91f02b4 SHA-256 recomputation (OpenSSL 3.x) MATCH 2026-10-09
AI-DATA.1 ...b3d7f2e8a190 SHA-256 recomputation (OpenSSL 3.x) MATCH 2026-10-09
AI-ID.1 ...c4a8f7e2d301 SHA-256 recomputation (OpenSSL 3.x) MATCH 2026-10-09
AI-HITL.2 ...a2c9e4f7b831 SHA-256 recomputation (OpenSSL 3.x) MATCH 2026-10-09
AI-PERF.1 ...b8e2f4a7c130 SHA-256 recomputation (OpenSSL 3.x) MATCH 2026-10-09

Remaining 18 anchors were verified via the public verifier at sovereign.tenova.io/verify. All returned VALID.

6. Annex IV Technical Documentation Status

SectionTitleStatusNotes
1General DescriptionCOMPLETESystem purpose, intended use, interaction with hardware/software.
2Development ProcessCOMPLETEDesign specifications, model architecture, training methodology.
3Monitoring and FunctioningCOMPLETESWT3 continuous monitoring evidence (AI-INF.1, AI-GRD.1 anchors).
4Performance and AccuracyPARTIALInternal benchmarks exist but not formatted per Art. 13(3)(d). Linked to NC-001.
5Risk ManagementCOMPLETERisk policy v2.1 reviewed. SWT3 evidence for AI-SAFE.1.
6Changes LogCOMPLETEVersion history documented. Lifecycle chain evidence (AI-LCM.1).
7Harmonised StandardsCOMPLETEEN ISO/IEC 42001:2023 applied.
8EU Declaration of ConformityPENDINGTo be issued upon resolution of NC-001.

7. Conclusion and Recommendation

Assessment Outcome: CONDITIONAL PASS

AutoLend v3.2 demonstrates substantial conformity with EU AI Act requirements for high-risk AI systems under Annex III, Area 5(b). One minor non-conformity (NC-001) was identified regarding deployer documentation under Article 13(3)(d). Two observations were recorded for continuous improvement.

The assessment body recommends conditional certification pending:

  1. Resolution of NC-001 within 90 days (deadline: 2027-01-08)
  2. Submission of updated deployer documentation for verification
  3. Targeted reassessment of Art. 13 conformity (January 2027)

The use of SWT3 cryptographic witness evidence enabled continuous assessment over the 70-day window, providing stronger temporal coverage than periodic manual assessments. All 23 anchors were verified, with 5 independently recomputed using the assessor's own tools. The evidence integrity chain was confirmed intact.

8. Signature Blocks

Lead Assessor Dr. Katarina Novak
European AI Conformity Partners GmbH
Date: _______________
Technical Expert Marcus Lindgren
European AI Conformity Partners GmbH
Date: _______________
Quality Reviewer Sofia Martens
European AI Conformity Partners GmbH
Date: _______________

Annex A: How to Read SWT3 Anchor References

SWT3 witness anchors cited in this report follow the format:

SWT3-{TIER}-{PROVIDER}-{UCT}-{PROCEDURE}-{VERDICT}-{EPOCH}-{SHA256_12}
SegmentMeaningExample
TIERDeployment tier (E=Enclave, S=SaaS, H=Hybrid)E
PROVIDERInfrastructure providerVULTR
UCTControl categoryAI
PROCEDURESpecific procedure from the UCT RegistryAIGRD1
VERDICTAssessment resultPASS
EPOCHUnix timestamp of witness event1791532800
SHA256_12First 12 characters of the SHA-256 fingerprinta7c3e91f02b4

Any anchor can be independently verified at sovereign.tenova.io/verify with no account or authentication. The SHA-256 fingerprint formula is published in the SWT3 Protocol Specification and can be recomputed using any standard cryptographic library.