THE INTELLIGENT AI GOVERNANCE LEADERSHIP PROGRAMME
Separate the claim from the permission.
20 Sessions · 25 Minutes Per Day · Four Weeks · Free · For leaders in Nigeria’s oil and gas sector
Hello — I am Coach Ritchie. I am the AI assistant for this programme. Ritchie Wingo built me, and your work is marked against the rubric he published; anything that falls below the mark to continue, he reviews himself, because that is the point at which a person needs help rather than a score. I am here for the moments in between, when the steering committee meets on Monday and you want to argue a point through with someone first.
Twenty sessions, twenty-five minutes a day, four weeks. An AI system can be accurate and still not be permitted to act. This programme is about the difference: separating the claim from the permission, naming who owns and who can stop a system, demanding evidence fitted to the consequence, and reporting honestly to the board — for companies in Nigeria’s oil and gas sector, where asset records, controlled documents and sensor histories make these distinctions concrete.
Every assignment is about your company and one real AI system or proposal in it, and every assignment comes back with a written letter: what holds up and why, and where something is thin, exactly where to look. By Session 20 you will hold a signed ninety-day governance plan for that system.
Ask me anything as you work and I will help you think it through, but I will not write your plan for you, I do not give legal or technical-assurance advice, and I switch myself off while you sit a quiz or an exam.
There is nothing to buy and no licence key to redeem. You sign in with your Google account so that your work can be marked and returned to you, your progress page follows you between devices, and your certificate can be issued in your own name.
With your Google account. Name, email, the company you work for and your role — that is the whole enrolment.
The decision that requires governance. Choose the one AI system or proposal you will carry through the programme.
Twenty-five minutes, then one written assignment. It is marked against a published rubric and comes back as a letter.
You assemble and sign your ninety-day plan, sit the final, and your certificate is issued.
Already started? Open my progress page → · Just looking? Read Week 1 →
This programme assumes you are not a data scientist and do not intend to become one. It ends with you able to govern an AI system as a decision — owned, evidenced, bounded and stoppable — and to question a technical team about what its validation actually establishes.
State what the system is claimed to do, what it is permitted to do, and the counterfactual it must beat.
Keep purpose, data, technical readiness, business authority and residual-risk acceptance as distinct approvals — and preserve the right to stop.
The claim, the evidence, the decision rule and the validity boundary, with evidence states and the defeats that would withdraw approval.
Escalation rules before scores; uncertainty recorded separately; reclassification when the use changes.
The target, the cost of each error, uncertainty, calibration, drift, fairness — and why an explanation is not a cause.
Task evaluation, controlled knowledge, permissions that survive retrieval, and authority enforced outside the model.
Advisory use apart from control use, operational technology security, management of change and a bounded industrial release.
Counts with denominators, the adverse result reported, and a governance path established in three phases.
| It is written for | It is not written for |
|---|---|
| Managing directors, executive and non-executive directors of operators, refiners, gas businesses and service companies | Engineers looking for model-building or coding work — that is a different course |
| Heads of operations, maintenance, HSE, legal, regulatory, risk, audit, procurement, HR, finance and technology who must approve or answer for AI | Anyone looking for legal advice on a specific system or a formal assurance opinion |
| Internal audit and assurance leaders who must test whether AI controls operate as represented | Anyone wanting a certificate without writing about a real system |
| Lenders, investors and advisers who must judge a company’s AI claims | Anyone expecting twenty minutes of video and a pass |
This programme does not end in a folder of notes. In Session 1 you choose one real AI system or proposal in your own company, and every session after that writes one section of a single document — your 90-Day AI Governance Plan — around it. By Session 20 you assemble and sign it. Written properly, it is the paper you table at your next executive committee or board meeting.
| Week | Sections you write |
|---|---|
| Week 1 The Leadership Doctrine and the Law | 1. Section 1 — The AI decision our company faces, the claim, the permission sought and the counterfactual. 2. Section 2 — Who owns, approves, accepts risk and can stop the system. 3. Section 3 — The evidence contract: falsifiable claims, evidence states and release controls. 4. Section 4 — The incremental value case and the risk classification, with escalation rules. 5. Section 5 — Our obligation map and the assurance crosswalk we will actually evidence. |
| Week 2 Technical Evidence That Survives Challenge | 6. Section 6 — Our AI inventory, data provenance and change triggers. 7. Section 7 — The target definition and the cost of each kind of error for our system. 8. Section 8 — How uncertain our evidence is and how uncertainty enters the workflow. 9. Section 9 — Our revalidation triggers, safe degradation and fairness trade-off. 10. Section 10 — What would prove our claimed business improvement, and what would not. |
| Week 3 Generative Systems, Security and Operations | 11. Section 11 — The task distribution, groundedness test and document-control boundary for our assistant. 12. Section 12 — The agent's enforceable authority and the security tests it must pass. 13. Section 13 — Privacy controls and the advisory-versus-control boundary for any plant-facing use. 14. Section 14 — Review capacity, contestability and the vendor evidence we will demand. 15. Section 15 — Our incident response, restart rule and assurance sample. |
| Week 4 Release Decisions, the Board and the Ninety Days | 16. Section 16 — Our release decision written in the form of the completed case. 17. Section 17 — The system card and release record for our system. 18. Section 18 — The board pack: counts with denominators, metrics and portfolio limits. 19. Section 19 — Role literacy, the acceptable use policy and the limits we will state honestly. 20. Section 20 — The assembled, signed 90-Day AI Governance Plan with its executive summary. |
This programme is free, and nothing is upsold to you inside it. When you finish, you receive an ERW CommandGovernance certificate of completion in your own name — issued on a pass, not on attendance.
| To receive it | What that means |
|---|---|
| Every assignment passed | Sessions 1 to 19, each marked at 70 or above against its published rubric. Work below the mark comes back with what to fix; resubmit and the new mark replaces the old one. |
| The capstone passed | Your signed 90-Day AI Governance Plan, Session 20, marked at 70 or above. |
| The Final Exam passed | Fifteen questions, three of them rebuilt from your own earlier mistakes, at 70 or above. |
The certificate is emailed to the Google address you signed in with. It certifies completion of an ERW leadership programme; it is not a legal qualification, an assurance accreditation, a standards certification or a university award.
Only people who have finished the programme can write one — the Session 20 capstone passed and the marked Final passed, both recorded by the server rather than by anyone’s say-so. They are shown exactly as written, never solicited and never edited.
One session a day, twenty-five minutes. Each one teaches part of the doctrine and makes you use it on your own company.
Every session ends in a written assignment — a decision record, an evidence contract, a classification, a plan section. Four hundred to nine hundred words.
Against the rubric printed under the assignment. A written letter comes back, usually within minutes.
Session 20 assembles nineteen sections into one document, then the final exam — three of whose questions are rebuilt from your own mistakes.
No mystery, and no waiting days for a mark. Here is the whole loop.
One document per session — Word or Google Docs — with the first line reading Session: N. Your own company, your own system.
Against that session’s published rubric, criterion by criterion. The same rubric every time, for everybody.
Not a score — a letter naming what holds up, what is asserted without evidence, and exactly where to look to fix it.
Your mark joins your progress page and the corrected section goes into your plan, so Session 20 is assembly rather than writing.
An illustration of the letter format, using Session 3’s real rubric.
| Criterion | Awarded |
|---|---|
| Writes at least one claim with a failure condition, pre-specified metric, population and release rule | 24 / 30 |
| Places each item of existing evidence in an honest evidence state | 19 / 25 |
| States a validity boundary and at least two defeats specific to the system | 20 / 25 |
| The honest paragraph names where the student's own company mistakes a demonstration for validation | 16 / 20 |
Four weeks. Five sessions a week, twenty-five minutes each, at whatever pace your diary allows. Every session ends in one written assignment about your own company, and every assignment becomes a section of your ninety-day plan.
Nine papers, marked the moment you submit, every question returned with the reasoning behind it. Four pop quizzes of five questions, four practice exams of fifteen, and a fifteen-question final. You are never left to guess when to sit one: the session that opens a paper says so, prints the paper beside its assignment, and flags itself on the session tab — and your progress page always names the paper due now. Closed book, no notes, and Coach Ritchie switches himself off while you sit one. Pass mark 70 — and you may resit the practice papers as often as you like.
5 questions · after Session 3
15 questions · after Session 5, closing Week 1
5 questions · after Session 8
15 questions · after Session 10, closing Week 2
5 questions · after Session 13
15 questions · after Session 15, closing Week 3
5 questions · after Session 18
15 questions · after Session 19, before the final
15 questions · in Session 20
Nineteen sections written one per session, assembled and signed in Session 20: the first AI system or decision governed, its claim and counterfactual, the owner and approver, the evidence contract, the risk class, the release controls, the monitoring and incident route, the board report and the gates at days 30, 60 and 90.
The Intelligent AI Governance — An Operating Doctrine for Responsible AI Leadership and Technical Assurance. Thirty-two chapters across seven parts: the leadership doctrine; law, standards and the operating system; technical evidence that survives challenge; generative systems and delegated action; operations, people and independent assurance; making the doctrine an operating practice; and the executive and technical toolkit.
These 20 sessions teach the doctrine and make you use it. The book carries what twenty-five minutes cannot: the full chapters, the source register behind every documented claim, two completed release decisions, and fifteen appendices — intake and the evidence contract, classification and impact assessment, the evaluation protocol, an acceptable use policy, vendor due diligence, the system card, the incident runbook, the board pack, monitoring and control testing, the ninety-day checklist and the technical derivations.
Nothing in this programme depends on buying it. Every session, paper and certificate is free whether you own the book or not.
The whole programme on one printable page — the five approvals, the evidence contract, evidence states, the internal tiers, the board’s questions and the first ninety days. Keep it beside you from Week 2.
The document every assignment is written in — opens in Word or Google Docs, with the first line already correct.
Read the first session before you sign in, and decide for yourself whether the rest is worth four weeks.
Your marks, your letters, your plan sections and your paper results, in one place.
| Question | Answer |
|---|---|
| Is it really free? | Yes. No card, no key, no paid tier. The certificate is free too. The book is available separately for anyone who wants the full chapters and appendices, and nothing in the programme depends on it. |
| How much time, honestly? | Twenty-five minutes of reading and thirty to sixty minutes of writing per session. Call it eight to ten hours over four weeks, and rather more if you do the capstone properly. |
| Do I need a technical background? | No. The technical sessions teach you what to ask, not how to build. You need a real company, one AI system or proposal in it, and the willingness to look at both honestly. |
| Is this specific to oil and gas? | The doctrine is general; the setting is Nigeria’s oil and gas sector. Every session sets an operations case — field and plant assets — beside an enterprise case — documents, regulatory, commercial — and the book’s two completed release decisions are a predictive-maintenance model and a regulatory assistant for a Nigerian energy enterprise. |
| Is this legal advice? | No. It is an operating doctrine for leaders. Nigerian, EU and US instruments are taught only as the book describes them. |
| Can my leadership team do it together? | Yes, and it works better that way — but each person signs in and submits their own work, because the plan is only useful if it is argued over. |
| What if I miss a week? | Nothing happens. There are no cohort dates and no deadlines. Your progress waits for you. |
| Who marks it? | It is marked against R. Wingo’s published rubric, criterion by criterion, the same way every time. Anything that comes out below the mark to continue, he reviews himself before it reaches you. Coach Ritchie helps you think; he does not mark and he does not write your plan. |