docs: COMPLIANCE.md article-by-article evidence mapping

[vaaraio]

Summary

• New COMPLIANCE.md mapping Vaara's runtime artefacts to EU AI Act articles 9, 11, 12, 13, 14, 15, 26, 61 and DORA 10/12/13.
• Explicit carve-out for what the deployer still owns (Annex IV technical file, QMS, conformity decision, legal interpretation).
• Python + CLI examples using the real API (pipeline.intercept(), vaara trail export/verify).
• Two README links added: one near the top, one from the existing "Compliance evidence" section.

Test plan

• COMPLIANCE.md renders cleanly on GitHub
• Both README links resolve
• Article table matches vaara.compliance.engine.EU_AI_ACT_REQUIREMENTS

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added comprehensive compliance documentation mapping Vaara runtime to EU AI Act and DORA requirements
  • Documented evidence types and integrity properties
  • Included guidance for extracting and verifying compliance evidence via Python and CLI tools
  • Updated README with compliance documentation references

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

A new COMPLIANCE.md document is added detailing how Vaara runtime outputs map to EU AI Act and DORA article requirements, including article-to-event mappings, evidence artefact classes, integrity properties, and CLI/Python access patterns. README.md is updated with cross-references to this compliance documentation.

Changes

Cohort / File(s)	Summary
Compliance Documentation COMPLIANCE.md	New document mapping Vaara runtime outputs to EU AI Act and DORA requirements, including evidence artefact classes (audit trail, conformity report, regulator handoff), integrity properties, Python and CLI access methods, and deployer responsibilities.
README Updates README.md	Added references to the new compliance documentation, including links to article-by-article evidence mapping and pointer to COMPLIANCE.md for full mapping details and CLI handoff flow.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A compliance hop through audit trails,
Hash chains strong, where truth prevails,
DORA's dance, the AI Act's creed,
Mapped with care for all to read,
Responsibility—oh so clear! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: COMPLIANCE.md article-by-article evidence mapping' is concise, specific, and directly describes the main change: adding a new compliance documentation file with detailed article mappings.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/compliance-mapping

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}