innorve-evidence-binder

Scaffolds a governance binder skeleton with folders, templates, and owner assignments for AI system audits and reviews.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/Innorve-Inc/innorve-method --skill innorve-evidence-binder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: innorve-evidence-binder
Source: https://github.com/Innorve-Inc/innorve-method/tree/main/plugins/innorve-method/skills/innorve-evidence-binder
Command: npx skills add https://github.com/Innorve-Inc/innorve-method --skill innorve-evidence-binder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scaffolds a Governance Binder skeleton to organize artifacts, templates, and ownership for AI systems, ensuring audit-readiness from day one.

Core Features & Use Cases

  • Folder scaffold at governance/<system-name>/ with a README index and templates for model cards, risk registers, eval plans, prompts, and audit trails.
  • Append-only CHANGELOG to track binder evolution and last-reviewed dates.
  • Owner assignment workflow that enforces named owners per artifact and reusable governance patterns for SOC 2, HIPAA, and EU AI Act contexts.
  • Use Case: a new AI system in a regulated domain uses the binder to organize evidence before an audit.

Quick Start

Create a new folder governance/<system-name>/ and begin populating the templates with owners and placeholders.

Frequently Asked Questions about innorve-evidence-binder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up an AI governance binder for audit readiness?

An AI governance binder scaffolds a folder structure with templates for model cards, risk registers, and audit trails to organize compliance evidence. You create a governance/<system-name>/ directory and populate the provided templates with named owners and placeholders.

What evidence do I need to prepare for an EU AI Act audit?

EU AI Act audits require documented risk registers, model cards, evaluation plans, and audit trails. The binder provides reusable governance patterns and templates specifically mapped to EU AI Act, SOC 2, and HIPAA contexts to structure these artifacts.

Can I use this governance binder scaffold for multiple AI systems?

Yes, the binder is designed to be instantiated for each AI system individually. You create a separate governance/<system-name>/ folder per system, allowing each to maintain its own ownership assignments, templates, and audit trails independently.

What's the best way to track compliance documentation changes over time?

Tracking compliance documentation changes is handled through an append-only CHANGELOG within the binder scaffold. It records binder evolution and last-reviewed dates, ensuring a defensible audit trail of when artifacts were updated and by whom.

Does the binder enforce ownership assignment for compliance artifacts?

Ownership assignment is enforced through a built-in workflow that requires named owners per artifact. This ensures every model card, risk register, and evaluation plan has a designated accountable individual before audit review.

When do I need to scaffold a governance binder for a new AI system?

You need a governance binder when a new AI system operates in a regulated domain requiring audits or regulator reviews. Scaffolding it from day one ensures audit-readiness by organizing evidence before compliance reviews begin.