The flagship provider lifecycle tool: scores Annex IV technical-documentation completeness section-by-section, selects the conformity-assessment route (internal control vs notified body), gates CE-marking readiness, and emits an EU Declaration of Conformity skeleton. Answers the provider's question: is this high-risk financial AI system ready to CE-mark? Part of the ai-governance-conformity chain — distinct from art-05 (credit-scoring conformity check) and tool 333 (Art 9 risk-management builder): those are point-assessment stages; this tool assembles the full Annex IV conformity lifecycle.
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `build_ai_conformity_pack`. Task: Assemble an EU AI Act Annex IV technical documentation pack, validates the conformity-assessment route (internal control vs notified body), checks CE-marking and EU Declaration of Conformity readiness, and scores completeness per Arts 9/10/15/17.
Call it with arguments: {"policy_parameters":{}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Over MCP, the run happens on the AINumbers worker. No AINumbers server stores your inputs.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-65-ai-conformity-pack-builder.html#p=v1.H4sIAAAAAAAA_wECAP3_e31Dv6ajAgAAAA