AI Governance Chain
  1. Watch
  2. Season 3
  3. Episode 4

AI Governance for Small Businesses: Start in 8 Hours

Governance in a Day is a one-day path from AI Governance Chain that helps a small or medium business with no governance team build a minimum viable AI governance programme in 8 hours: 4 steps of about 2 hours each, from scope to evidence. Every step uses a free command that has worked since v0.1.0 (4 November 2026) and was checked again against v0.2.0 on 9 November 2026.

S3E4 poster: Governance In A Day. No governance team? Start in 8 hours.
Video not out yetRead the one-day plan

The video episode is not out yet.The one-day plan and the script are below. Every command works today.

S3E4 · Governance in a Day · Season 3: The Commons · script for an episode of about 3 minutes. Script and sources by Mathieu K. Gouanou. Not legal advice. Commands shipped in v0.1.0 (4 November 2026) and were checked again against v0.2.0 on 9 November 2026. Atlas data as of 4 November 2026: 198 obligations in 17 regimes, draft and not yet expert-reviewed.

Links of the chain in this episode: Obligation, Control, Gate, Evidence

The one-day plan

Block one working day for one AI system, ideally the one that acts for you most, and split it into 4 blocks of about 2 hours. You need a computer with Node.js 18 or later; step 3 also needs a GitHub repository. Each block names the command to run.

  1. Morning, 2 hours1. Find the rules that apply

    List every AI tool and agent your team uses and pick one. Then list the obligations for your role, your markets and what the system does. For a chatbot in the EU, with the roles provider and deployer, the command lists 3 obligations on 9 November 2026: the banned practices (EU AI Act Article 5) and AI literacy for staff (Article 4), both applicable since 2 February 2025, and telling people they are talking to an AI (Article 50(1)), applicable since 2 August 2026. A deployer-only run lists Articles 5 and 4.

    npx github:mathieugouanou/aigovernancechain scope -j EU -r provider,deployer -u chatbot
  2. Late morning, 2 hours2. Write the governance file

    Create AI_GOVERNANCE.md at the root of your project: the system, its owner, the duties in scope and a control for each. Replace every "todo" with a real status, and add the AI models you use to the models section.

    npx github:mathieugouanou/aigovernancechain init
  3. Afternoon, 2 hours3. Add the check

    Run the check and fix what fails: any failure names the missing control. Then add the Shield GitHub Action to your repository, so every pull request runs the same 17 checks. A chatbot is not an agent, so the 5 agent checks are skipped. The setup is one workflow file, linked under The tool.

    npx github:mathieugouanou/aigovernancechain check
  4. Late afternoon, 2 hours4. Keep the evidence

    Create the Evidence Pack: EVIDENCE.md and evidence.json, a dated record of what you declared and what the check found, with a SHA-256 fingerprint of AI_GOVERNANCE.md. Share it when a client asks, and put the next review date in your calendar.

    npx github:mathieugouanou/aigovernancechain evidence

It is a first programme, not a full assessment: the checks read your file, not the behaviour of your system, and the Evidence Pack is not an audit.

The script

The script of this episode as of 9 November 2026, ahead of the video. The wording may change slightly when it is recorded. Numbers are written as digits. Sources are listed below the script.

0:00No governance team? One day is enough

Welcome! No governance team? One day is enough to start. AI Governance Chain's one-day starter builds a minimum viable AI governance programme in 8 hours: 4 steps of about 2 hours each, from scope to evidence. It works today, with commands shipped since v0.1 on 4 November 2026.

0:41A client asks about the EU AI Act

Picture the owner of a small agency that resells an AI chatbot under its own brand. On Monday, a client asks what the EU AI Act means for the product. There is no governance team and no lawyer on staff. By evening, she needs a map of what applies, a file that records her controls, and evidence she can show.

1:03The Obligation Atlas behind the path

The 4 steps follow the chain from OBLIGATION to CONTROL, GATE and EVIDENCE. They draw on the Obligation Atlas: 198 obligations across 17 regimes, dated 4 November 2026.

1:16Step 1, morning: aigovchain scope

Step 1, morning: run aigovchain scope with jurisdiction, role and use. For an EU chatbot, with the roles provider and deployer, it lists 3 duties that apply today: no banned practices, Article 5; AI literacy for staff, Article 4; and telling people they are talking to an AI, Article 50(1).

1:36Step 2, late morning: AI_GOVERNANCE.md

Step 2, late morning: run aigovchain init. It writes AI_GOVERNANCE.md, one plain file with the system, its owner, the duties in scope and a control for each. Replace every to-do with a real status.

1:49Step 3, afternoon: Shield GitHub Action

Step 3, afternoon: add the Shield GitHub Action. Every pull request runs 17 checks on the file. A chatbot is not an agent, so the 5 agent checks are skipped, and any failure names the missing control.

2:03Step 4, late afternoon: the Evidence Pack

Step 4, late afternoon: run aigovchain evidence. The Evidence Pack holds a readable summary, a JSON record and a fingerprint of the file: what was declared, what was checked, and when.

2:14Who uses the one-day starter?

For an agency owner, it turns a client question into a dated answer.

For a product lead, it is the first record of the AI system and its controls.

For a developer, the checks and the evidence sit beside the code, in the repository.

2:31Limits of an 8-hour programme

This is a first programme, not a full assessment. The Action checks the declared file, not the model's behaviour, and the Evidence Pack is not an audit. Confirm the rules and sources for your system. This is governance guidance, not legal advice in any jurisdiction.

2:48Block a day and start

Block one day this week and start with aigovchain scope; the link is in the description.

One day gets you started. What keeps you going for a month?

Thank you for watching!

Short answers

Can a small business start AI governance in one day?

Yes, as a first programme. In 4 blocks of about 2 hours, a small team can list the rules that apply to one AI system, write AI_GOVERNANCE.md, check it and create an Evidence Pack. It is a start, not a full assessment. Not legal advice.

Does it work today?

Yes. Every command shipped in v0.1.0 on 4 November 2026 and was checked again against v0.2.0 on 9 November 2026.

What does aigovchain scope list for an EU chatbot?

With the roles provider and deployer, 3 obligations on 9 November 2026: EU AI Act Article 5 (prohibited practices) and Article 4 (AI literacy), both applicable since 2 February 2025, and Article 50(1) (telling people they are interacting with an AI), applicable since 2 August 2026. A deployer-only run lists Articles 5 and 4. Not legal advice.

What does it cost?

The commands are free and open source under Apache-2.0. They run on your computer with Node.js 18 or later, and the Shield GitHub Action runs in GitHub Actions.

Is the Evidence Pack an audit?

No. It records what was declared and what was checked, and when, with a SHA-256 fingerprint of AI_GOVERNANCE.md.

Does passing the checks mean we meet the EU AI Act?

No. The checks read your declared file, not the behaviour of your system, and a result states facts about the file only. Confirm the rules for your system at the source, with a lawyer where needed.

Questions this episode answers

Sources

  1. AI Governance Chain changelog: v0.1.0 (4 November 2026) and v0.2.0 (9 November 2026)
  2. AI Governance Chain Shield GitHub Action: setup and checks
  3. AI_GOVERNANCE.md draft spec v0.1
  4. AI Governance Chain roadmap: I20, SME 1-day starter
  5. EU AI Act Article 4: AI literacy (AI Act Service Desk)
  6. EU AI Act Article 5: prohibited AI practices (AI Act Service Desk)
  7. EU AI Act Article 50: transparency obligations (AI Act Service Desk)