15-Session Programme · 25 Minutes Per Day · Free · For regulators and regulated companies in Nigeria’s petroleum industry
WEEK 1 OF 3 · THE INFLECTION AND THE FOUNDATIONS YOU CANNOT SKIP · SESSIONS 1–5 · WORK AT YOUR OWN PACE
Orientation · The Intelligent RegulatorSESSION 1
The Intelligent Regulator and the Reader's Toolkit
Why This Matters
Every decision in Nigeria's petroleum regulatory relationship is lived twice: by the institution that must decide it lawfully, and by the company that must evidence it and fulfil its conditions. AI is arriving on both sides. It can organise evidence and retrieve provisions; it can also produce a convincing but incorrect legal answer. Over fifteen sessions you will build a signed 90-Day Regulatory AI Plan for your own organisation, around one decision you choose today that currently costs it time, quality or trust. The book's claim is that the ability to explain a decision depends on leadership before it depends on software. This programme trains that leadership.
25-Minute Module
0:00 – 5:00
The argument, and the finish line
- An intelligent regulator can explain what it knows, how it knows it and why its decision follows.
- THE DOCTRINE
These capabilities depend on leadership before they depend on software. Make the evidence reliable, put judgement where it belongs and close the loop after action.
- The three weeks: 1 The Inflection and the Foundations You Cannot Skip; 2 Intelligence in Regulatory Practice; 3 Trust, Collaboration and the Leadership Game Plan. The finish line: a signed 90-Day Regulatory AI Plan, fourteen sections written one per session, assembled in Session 15 with the book's pilot charter, decision-rights matrix and executive scorecard.
- House rules: write about your own organisation; bring a real decision; no value claim without a baseline; no decision without a named owner and a lawful authority; report a blocker the same day. The pass mark is 70.
- Said once: this is leadership training, not legal, investment or engineering advice, and the book is not an official interpretation issued by a regulator. The frameworks, worked processes, templates and scorecard are my proposals, not statutory standards or prescribed regulatory forms. Specific obligations rest on the applicable instruments, licence conditions and legal advice.
Ask which decision is waiting before you ask what to buy.
5:00 – 10:00
Two sides, one legal starting point
- The Petroleum Industry Act 2021 establishes the upstream Commission and the midstream and downstream Authority, with distinct technical and commercial regulatory responsibilities. The Minister retains powers provided by the Act. It is the book's legal starting point, not a claim that one institution controls every petroleum-related obligation.
- Other public authorities exercise their own functions: data protection, Nigerian content, taxation and environmental assessment need separate legal treatment. A digital interface can coordinate evidence without merging statutory powers, and a company must establish the correct route for each activity.
- The book extends The Intelligent Barrel's loop from data through decision and action to measured outcome; here the outcome is public value as well as industrial performance. Neither side should measure success by AI tools purchased.
- THE DOCTRINE
A faster workflow that produces weaker decisions has failed. A more sophisticated model that creates no operational improvement has also failed. Leadership must hold both truths at the same time.
- In a regulated company, read every regulator-side passage as how your company prepares evidence for, and works with, the regulator on the same matter.
A shared interface is not a shared mandate.
10:00 – 18:00
The six frameworks, as the book defines them
Framework In brief The question it forces 1. Operating-Intelligence Loop Observe, interpret, decide, act, learn Who owns the next action? 2. Data-Foundation Precondition Dependable judgement needs dependable evidence Is the first data contract enforceable? 3. Autonomy Ladder Assist, supervised drafting, bounded execution What has this action earned? 4. Value-versus-Risk Map Benefit beside the harm of an error Which concrete controls are needed? 5. Sequencing Discipline Order by dependency What must exist first? 6. Operations-Excellence Lens The whole working process Where does the case wait? - The loop. In licensing, observation receives the application, interpretation finds the provisions, decision belongs to the authorised officer, action manages conditions, and learning compares the result with later queries and appeals. It fails wherever responsibility disappears. Finish the book's sentence: this evidence will help this person make this decision by this time, leading to this action and this measurable outcome. If you cannot, the project is not yet defined.
- The data floor and the ladder. Establish identity, period, units, source, revision, responsible person and limitations; AI often makes weak data more dangerous by polishing it. Advance to supervised drafting only after source fidelity is shown. The ladder is not a timetable: six months of use does not prove a tool can refuse a licence or impose a penalty.
- THE DOCTRINE
Keep legally consequential determinations with authorised human decision-makers unless a lawful and specifically approved arrangement establishes otherwise. Autonomy should be earned by the action and its consequences.
- The map and the sequence. Weigh the people affected, the chance to correct, time, confidentiality and capacity to recover, and describe controls concretely rather than assigning a reassuring colour. Sequence by dependency: legal sources before legal retrieval, facility identities before analytics, decision rights before an agent touches external parties. A checklist or a transparent queue is conventional software, and it belongs in the programme.
- INSIDE THE REGULATOR · THE WORKED CASE
- Inside the regulator. In a fictional licensing department, an assistant flags a missing drawing. The loop breaks at action: nobody owns the correction request, and the file waits as pending.
AT THE COMPANY · THE PARALLEL- At the company. In a fictional downstream company, the regulator's query lands in a shared inbox. Nobody owns the response, and the board hears that the regulator is slow. The same loop, seen twice.
Find where responsibility disappears before you price the clever part.
18:00 – 22:00
Trace an ordinary week, and keep the decision record
- The Operations-Excellence Lens asks where the case waits and what repeats because an action was never closed. Select one application, one inspection and one complaint, or their company equivalents, and trace each from receipt to disposition, recording handovers, repeated work, missing decisions and unresolved conditions. These traces often reveal a better first project than a list of fashionable use cases.
- The six frameworks are author tools, not statutory standards. Use them together on a single decision and record its purpose, legal and technical basis, evidence, uncertainty, accountable owner, permitted AI contribution, required human checks, action and review date. Preserve the original record and each material correction.
- THE DOCTRINE
The institution should be able to explain the decision to a reviewer who was not present at the meeting.
Improving one task while adding downstream rework improves nothing.
22:00 – 25:00
Write it down, and Section 1
- Before you close the laptop, write the book's sentence for your decision and the loop stage where it breaks.
- Choose a decision that costs time, quality or trust now, not one that sounds like an AI project. If it later needs only a checklist or a named owner, that is a legitimate result.
- Section 1 of your plan is Our organisation, our side of the regulatory relationship, the one decision we will carry and where its loop breaks.
The decision you choose today is the one you will defend in Session 15.
Key Terms
Operating-Intelligence Loop
Observation, interpretation, decision, action and learning; it fails where responsibility disappears.
Data contract
Agreed definitions, required fields, quality checks and responsibilities for a data record.
Autonomy Ladder
Assistance, then supervised drafting, then bounded low-consequence execution; not a timetable, but earned by the action and its consequences.
Decision record
The book's record of purpose, basis, evidence, uncertainty, owner, permitted AI contribution, human checks, action and review date.
Self-Check — Before You Submit
1. In a fictional licensing department, an assistant reliably flags missing documents, but no correction requests go out and files sit as pending. What comes first?
- A. Buy a more accurate model
- B. Name an owner for the correction request
- C. Report the missing-document count to the board
- D. Let the assistant reject incomplete applications
B. Name an owner for the correction request — The loop breaks at action. Every use case needs an owner for the next action, not only for the model; automatic rejection hands a consequential step to an unproven tool.
2. How does the book describe the Petroleum Industry Act 2021?
- A. It puts every petroleum obligation, taxation included, under one regulator
- B. It removes the Minister's powers
- C. It establishes the Commission and the Authority, the Minister retains powers under it, and it is the legal starting point
- D. It prescribes regulators' digital workflows
C. It establishes the Commission and the Authority, the Minister retains powers under it, and it is the legal starting point — It is the legal starting point, not a claim that one institution controls every obligation; data protection and taxation need separate legal treatment.
3. A drafting assistant has run without complaint for six months. A sponsor proposes letting it issue licence refusals. What does the Autonomy Ladder say?
- A. It is not a timetable; consequential determinations stay with authorised humans
- B. Six clean months earns the next rung
- C. Refusals are fine if reversible
- D. The vendor decides
A. It is not a timetable; consequential determinations stay with authorised humans — Six months of use does not prove a tool can refuse a licence. Autonomy is earned by the action and its consequences, and later reversal does not undo harm already caused.
Today’s Assignment
Name your organisation and its side of the regulatory relationship, choose the one decision you will carry through this programme, and show where its Operating-Intelligence Loop breaks.
- Your organisation. Its name and side: an institution and the function you lead, or a company and its activity (upstream, midstream, downstream, gas, refining, storage or other).
- The decision. One that costs your organisation time, quality or trust: an application class, an inspection finding, a complaint, a reconciliation, a recurring query or a report obligation.
- The sentence. This evidence will help this person make this decision by this time, leading to this action and this measurable outcome.
- One ordinary case. Traced from receipt to disposition.
- Where the loop breaks. The stage, why, and who owns the next action, by role.
- The honest part. What your organisation gets wrong about this decision today. No AI in use yet is normal.
- Four hundred to nine hundred words.
YOUR 90-DAY PLAN
Section 1 — Our organisation, our side of the regulatory relationship, the one decision we will carry and where its loop breaks.
How this is marked — the rubric
| Names the organisation, its side and its function or activity | 15 |
| Chooses one bounded decision and completes every part of the book's sentence | 30 |
| Traces one real case from receipt to disposition | 25 |
| Locates the loop break with a reason and the next-action owner by role | 20 |
| Names a real weakness in the student's own organisation | 10 |
| Total · pass mark 70 | 100 |
Submitting session 1
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 1, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Decision-first thinkingThe six toolkit frameworksLocating the broken loop stageKeeping a decision recordWorking both sides of the interface
Part One · The InflectionSESSION 2
From Regulatory Data to Public Value
Why This Matters
A file marked pending can mean four different problems, and nobody can fix any of them from a single count. This session turns Session 1's argument into a value case you could defend before a board or an auditor. Inside an institution, value is lost when skilled officers repeat clerical work, when uncertainty hides in one status and when actions stay open after a decision. Inside a company, the same loss appears as repeated queries, resubmissions and conditions nobody can evidence. Today you state the public-value chain for your decision, start the value case from an observed baseline rather than a promise, and separate the statuses and owners that a single green icon conceals.
25-Minute Module
0:00 – 5:00
The distance between a document and a decision
- The problem is usually not missing documents but the distance between a document and a decision: a report on time but on an incompatible boundary, a signed return that omits a material exception, a complaint with important evidence routed as a routine enquiry.
- National dashboards give policy context. They do not identify which asset has an overdue condition, what risk it creates and who must resolve it.
- THE DOCTRINE
Aggregate visibility and case accountability serve different purposes. A dashboard can help show whether the institution is making better decisions with its resources. It is not the answer itself.
- A producing field, a gas distribution system, a refinery, a storage terminal and a retail outlet need different evidence. A uniform portal's evidence requirements must reflect the actual activity. Do not confuse digital sophistication with lower risk: polished records can carry complex integrity exposure. Presentation is one signal, not the conclusion.
Ask which case is behind the number before you discuss the number.
5:00 – 10:00
Where value is lost, and the public-value chain
- Pending can mean awaiting a drawing, an engineering review, a legal interpretation or a signature. A useful case queue separates waiting time from active review time, records what is missing and who can supply it, and shows the age of the oldest unresolved high-consequence matter, not only an average. Averages can improve while the difficult cases deteriorate.
- AI can classify material, extract candidate facts, connect records, notice a drawing that conflicts with an approved design and locate the source of a technical claim; predictive analytics can estimate workload. These outputs direct attention; they do not replace the duty to test evidence.
- The public-value chain, link by link: better extraction reduces search time; better evidence reduces unnecessary queries; better queries reduce resubmission; better review supports a more timely, defensible determination; improved monitoring makes conditions visible after approval.
- THE DOCTRINE
Measure each link of the public-value chain rather than attributing every later improvement to AI.
A chain you cannot measure link by link is a hope, not a case.
10:00 – 16:00
The value case and the first pilot
- Build the value case from an observed baseline: application class, volume, manual effort, exception review, maintenance and downstream rework. Gross checking time released is the observed volume multiplied by the supported reduction per case. Net capacity subtracts the additional operating effort. The book supplies no figures, so the table uses assumed teaching inputs only.
Illustrative line (assumed teaching inputs) Value Observed volume in the period 600 files Supported reduction per case 1.5 hours Gross checking time released (600 × 1.5) 900 hours Additional operating effort (exception review, maintenance) 200 hours Net capacity (900 − 200) 700 hours - Released time is not automatically budget savings. If staff use the hours on difficult reviews, the benefit is capacity; if expenditure does not fall, there is no cash saving to claim. Measure avoidable rework too.
- The first pilot: one submission class with stable evidence requirements and enough history to show ordinary variation. The assistant may say evidence found, evidence not found, conflicting revisions and uncertainty, and nothing implying technical adequacy. Run it first in shadow mode, alongside the existing process without determining any external action. Compare it with independently reviewed files, including difficult cases and poor scans; analyse missed omissions, false omissions, unsupported extraction and the burden on reviewers. End with a recorded decision to adopt, revise or stop.
- For the board: median and tail case age, avoidable query rate, source fidelity, unresolved high-risk actions, appeals or corrections attributable to workflow error, system availability and the resources needed to sustain the service. Do not publish sensitive case details to demonstrate transparency.
Stopping a pilot on recorded evidence is a result, not an embarrassment.
16:00 – 21:00
Three statuses, three owners
- Organise work around a controlled case record: stable identifier, defined class, accountable coordinator, named reviewers and an explicit next action, with evidence attached by reference.
- Keep three statuses apart: evidence, review and decision. Evidence may be complete while technical review remains open. A review may be complete while the decision awaits lawful authorisation. A decision may be issued while its conditions remain unfulfilled. A single green icon cannot represent all three.
- INSIDE THE REGULATOR · THE WORKED CASE
- Inside the regulator. In a fictional licensing team, the case owner coordinates progress; the engineer and legal reviewer give the professional judgement; the service owner maintains the AI workflow. When the engineering basis changes, the case owner keeps one revision boundary and the specialists decide the consequence.
AT THE COMPANY · THE PARALLEL- At the company. In a fictional midstream company, the compliance lead tracks the same three statuses for its own application: pack submitted, regulator review open, decision awaited, conditions still to evidence. Ask whether the company and institution can identify the same outstanding decision from their records.
- THE DOCTRINE
Coordination does not allow the case owner to substitute for the authorised technical or legal judgement. A model owner is responsible for the system's behaviour; that does not make them the lawful decision-maker.
- Review weekly (blocked cases, ageing queues, escalations, ending in named actions), monthly at executive level (quality, workload, fairness, model performance, control weaknesses) and through periodic independent assurance. If the same issue appears every month without a new action, reporting is substituting for management. Reward accurate and timely decisions, not closed files, and make correction a legitimate professional act.
- Adoption needs a funded service owner, a fallback, controlled change and an outage test. At the executive review, ask for an ordinary, a difficult and a corrected case, and ask what work would continue if the model were stopped today.
Combining roles in a small team is practical; hiding them is not.
21:00 – 25:00
Write it down, and Section 2
- Before you close the laptop, write your decision's public-value chain in five lines and mark the link you can measure today.
- Then write the three statuses of one live case and its three owners by role.
- Section 2 of your plan is The public-value chain, the observed baseline, three statuses kept apart and the three owners.
If one person holds all three roles, write that down; it is a fact the board needs.
Key Terms
Public-value chain
The linked improvements from better extraction through better evidence, queries and review to visible conditions after approval, each measured separately.
Net capacity
Gross checking time released (observed volume multiplied by the supported reduction per case) less the additional operating effort the service creates. It is capacity, not automatically a budget saving.
Shadow mode
Evaluation alongside the existing process without determining external action.
Case owner
The person coordinating a defined case without replacing specialist or lawful decision authority; distinct from the professional owner and the service owner.
Self-Check — Before You Submit
1. A pilot report shows 900 hours of checking time released. Finance wants to book it as a budget saving. What is correct?
- A. Book it, since the hours were measured
- B. Book half as a prudent estimate
- C. Subtract additional operating effort for net capacity; claim cash only if expenditure falls
- D. Ignore it; released time has no value
C. Subtract additional operating effort for net capacity; claim cash only if expenditure falls — Gross time is not net capacity, and released time is not automatically budget savings. Ignoring it is the opposite error: capacity used on difficult reviews is real value.
2. Average case age is improving. What else must management see?
- A. The age of the oldest unresolved high-consequence matter
- B. The number of AI tools in use
- C. Total pages received
- D. The count of files marked pending
A. The age of the oldest unresolved high-consequence matter — Averages can improve while difficult cases deteriorate. A pending count is the trap: it hides whether a file awaits a drawing, a review, an interpretation or a signature.
3. In a fictional authority, the engineer is away and the AI summary looks complete. The case owner is pressed to sign off the technical point. What should the director decide?
- A. Let the case owner sign
- B. Ask the model owner to approve
- C. Mark it complete and correct later
- D. Keep review open until the authorised professional owner judges it, and record why it waits
D. Keep review open until the authorised professional owner judges it, and record why it waits — Coordination does not let the case owner substitute for technical judgement, and a model owner is not the decision-maker. Marking it complete hides a missing assessment behind an apparently complete case.
Today’s Assignment
State the public-value chain for your decision, record the observed baseline its value case would start from, and separate the statuses and owners of one live case.
- The chain. Your decision's public-value chain link by link, with how your organisation would measure each link.
- The baseline. Volume, manual effort, exception review, waiting and rework, marking what is measured and what is not. Do not invent figures.
- Released time. What it would and would not be, and whether any cash saving could be claimed.
- Three statuses. For one live case, the separate status of the evidence, the review and the decision.
- Three owners. The case owner, professional owner and service owner by role, and where those roles are blurred today.
- The book's question. What work would continue if the model were stopped today? If there is no model yet, answer for the process you would protect.
- Four hundred to nine hundred words.
YOUR 90-DAY PLAN
Section 2 — The public-value chain, the observed baseline, three statuses kept apart and the three owners.
How this is marked — the rubric
| States the public-value chain link by link with a measure for each link | 25 |
| Records an observed baseline, separates measured from unmeasured, and distinguishes capacity from cash saving | 25 |
| Keeps the evidence, review and decision statuses apart for one live case | 20 |
| Names case, professional and service owners by role and identifies where they are blurred | 20 |
| Answers what work would continue if the model were stopped, naming records, reviewers and fallback | 10 |
| Total · pass mark 70 | 100 |
Submitting session 2
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 2, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Building a value case from a baselineMeasuring the public-value chainDesigning a shadow-mode pilotSeparating evidence, review and decisionDistinguishing three kinds of ownership
Part Two · The Foundations You Cannot SkipSESSION 3
Making the PIA an Operating Backbone
Why This Matters
Legal text becomes operational only when your organisation can connect a requirement to an activity, an owner and evidence of fulfilment. A folder of PDFs is a reference, not an obligation-management system. This session asks for the most care in Week 1, because a model-generated summary is never the controlling legal document. You will read the Petroleum Industry Act 2021 as a map of decisions, keep the law apart from your organisation's chosen implementation, and write one register entry a regulator, a company and an auditor could each test. Every legal fact is stated exactly as the book states it.
25-Minute Module
0:00 – 5:00
A controlled source, and an answer that can refuse
- The PIA is the backbone; the system also holds applicable regulations, licence conditions, valid directives and relevant decisions, each with its legal status kept distinct. A consultation draft should not become a live compliance rule because it appears on an official website, and a website publication date may differ from commencement.
- The NUPRC's gazetted regulations index identifies published subject areas and the need to control versions; it is not a substitute for the current instrument.
- Build a controlled legal source register. For each instrument: official title, issuing authority, source, publication or gazette information, commencement where verified, scope, amendments, superseded status and validator. AI may propose metadata; a qualified reviewer approves legal status and applicability.
- An obligation cites the exact provision, the version relied on and its trigger. Comply with all regulations tells an engineer nothing.
- THE DOCTRINE
A fluent answer to a bad question is a failure. A clear request for the missing source can be the correct result.
- A legal assistant cites and displays the provision, states its date and scope, and routes the question when a source is missing or interpretation unresolved. Test it with a draft presented as enacted, a universal deadline and a superseded provision.
An unvalidated source is a lead, not a rule.
5:00 – 10:00
Reading the PIA as a decision map
- The section references below locate statutory subjects. The working records and roles are the author's proposed operating design. They do not reproduce every qualification or settle applicability; current regulations, licence conditions and authorised interpretation remain necessary.
Decision family PIA starting points Proposed working record Upstream supervision Sections 7 and 8 Technical and commercial review records Upstream development Sections 70 and 79 Licence identity and development decision pack Midstream and downstream approvals Sections 111 and 114 Application route and conditions register Refining Sections 174 and 183 to 186 Refining application and operating evidence Environment and flaring Sections 102 to 108 Plans, monitoring and exceptions Gas access and customers Sections 125, 160 and 164 to 165 Activity, network and service records Decommissioning Sections 232 and 233 Plan, cost basis and funding evidence Host communities Sections 235, 240 and 251 to 255 Trust, funding, delivery and reporting - These references organise the search; they do not summarise what any section says.
- THE DOCTRINE
A development case can depend on several decision families. Record those dependencies without implying that one team can approve every aspect.
Use the map to find the question, never to answer it.
10:00 – 15:00
Four workflow maps, and a decision that is not one event
- The book offers four workflow maps. Their roles are proposed functional assignments; the actual delegation governs their use.
- Upstream supervision. The company evidence owner provides the record; the case owner coordinates; the specialist assesses; the officer or body with authority acts. Keep the model's flag and the reviewer's conclusion separately: deleting rejected flags flatters the model.
- Licensing and project change. A new licence, a renewal, a modification and acceptance of a condition are different events. Sections 111(1) and 183 preserve a ministerial role in refining licensing on the Authority's recommendation, so the Authority's completed review must remain distinguishable from the Minister's issued instrument where that route applies. The proposed state record separates review open, assessment complete, recommendation issued, final decision pending and final instrument issued where applicable.
- Environment and closure; host-community delivery. Keep asset scope uncertain, plan update pending and funding evidence unresolved as different conditions. A need, an approved budget and an operating service are different records. A contribution calculation belongs in controlled computation, and the model should not decide which disputed expenditure enters the statutory base.
- INSIDE THE REGULATOR · THE WORKED CASE
- Inside the regulator. In a fictional authority, a refining licence application has a completed assessment. Where the ministerial route applies, the record shows recommendation issued and final decision pending, not approved, until the issued instrument exists.
AT THE COMPANY · THE PARALLEL- At the company. In a fictional refining company, the project manager ties the same case to the affected project gate; legal establishes the route. The plan does not treat the recommendation as the licence.
A recommendation is a step, not the instrument.
15:00 – 21:00
Law apart from implementation, and the register
- Use two linked records: the legal record of what the controlling source requires, with qualifications, and the implementation record of how your organisation proposes to fulfil or supervise it. A workflow is an organisational choice unless the instrument prescribes it, so a preferred process never becomes an alleged legal requirement.
- The obligation-to-evidence chain: provision, applicability, required action, accountable party, evidence, review, consequence of an unresolved exception. For a company the chain links to project gates and operating tasks; for a regulator, to review criteria and supervisory action. Shared definitions help; shared unrestricted access is neither necessary nor appropriate.
- Appendix B, an author template and not a prescribed form, has thirteen fields: obligation identifier; activity and entity; controlling source; source status (validated status, version and applicable date); applicability rationale; required act; trigger and timing; accountable owner; evidence; review; implementation; exception (gap, uncertainty, action and escalation); and change history.
- Its six statuses: not applicable, pending determination, evidence missing, under review, fulfilled and exception open. Use not applicable only with a recorded rationale. A blank field should not imply compliance. In the teaching entry for a report obligation, the receipt establishes delivery, while the report's adequacy and any resulting conditions remain separate questions.
- THE DOCTRINE
A changed instrument triggers review of affected entries; it does not automatically overwrite them. A revised model prompt alone is insufficient if the approved procedure and portal remain outdated.
- When a requirement changes, legal verifies source, effective date and transitional treatment, then register, fields, checklist and training follow, and old submissions stay identifiable. A release record names the validated source, affected activity, owner, changed fields, revised procedure and evaluation evidence, tested on an ordinary and a transition case. For the board: live obligations with verified sources and named owners, the age of unresolved legal-status questions, changes awaiting implementation and the rate of unsupported legal answers.
A green status because an email was sent is not compliance.
21:00 – 25:00
Write it down, Section 3, and Pop Quiz 1
- Before you close the laptop, write your decision's provision, its decision family and the applicability question still open.
- Section 3 of your plan is The obligation-to-evidence chain and one Appendix B register entry, with law kept apart from implementation.
- Pop Quiz 1 opens now: five questions, closed book, on Sessions 1 to 3. Sit it before you start Session 4.
Obligation to evidence and back to source, without memory: that is the backbone.
Key Terms
Applicability
The reason a legal or technical requirement applies to a particular activity, entity or case.
Controlled source
A retained authoritative reference with validated identity, status and version.
Obligation-to-evidence chain
Provision, applicability, required action, accountable party, evidence, review and the consequence of an unresolved exception.
Release record
The author's proposed record required before a changed provision enters the live service.
Self-Check — Before You Submit
1. As the book states it, what do sections 111(1) and 183 of the Petroleum Industry Act 2021 mean for a refining licence case?
- A. A ministerial role on the Authority's recommendation, so the Authority's review stays distinct from the Minister's issued instrument where that route applies
- B. The recommendation is the licence
- C. The Authority has no role
- D. A fixed decision deadline
A. A ministerial role on the Authority's recommendation, so the Authority's review stays distinct from the Minister's issued instrument where that route applies — The book states the ministerial role on the Authority's recommendation and draws only that consequence. It states no deadline; inventing one would add law the book does not contain.
2. Compliance finds a new regulation on an official website and wants it live in the register today. What comes first?
- A. Nothing; an official website makes it live
- B. A model summary
- C. A qualified reviewer's verification of legal status, commencement and applicability
- D. Board approval
C. A qualified reviewer's verification of legal status, commencement and applicability — A consultation draft should not become a live rule because it appears on an official website, and publication can differ from commencement. A model summary is never the controlling legal document.
3. A register entry shows fulfilled because the submission receipt is on file. What has the receipt established?
- A. That the report is adequate
- B. That no conditions will follow
- C. That the obligation no longer applies
- D. Delivery only; adequacy and conditions remain separate questions
D. Delivery only; adequacy and conditions remain separate questions — In Appendix B's teaching entry the receipt establishes delivery; treating it as adequacy gives a green status because an email was sent.
Today’s Assignment
Build the obligation-to-evidence chain behind your decision and write one complete Appendix B register entry for it, with the legal record kept apart from the implementation record.
- The chain. Provision, applicability, required act, accountable party, evidence, review and the consequence of an unresolved exception. Cite only what your organisation's validated sources state.
- One register entry. All thirteen Appendix B fields and one of the six statuses, with the legal record kept apart from your implementation.
- The map. The decision family your decision touches, and the applicability question left for a qualified reviewer. Do not answer it yourself.
- A change that propagates. How a source change reaches forms, checklist, training and systems, and who signs the release.
- The honest part. Where your organisation treats a preferred process as law, or a receipt as adequacy.
- Four hundred to nine hundred words.
YOUR 90-DAY PLAN
Section 3 — The obligation-to-evidence chain and one Appendix B register entry, with law kept apart from implementation.
How this is marked — the rubric
| Builds the full chain without legal content beyond validated sources | 25 |
| Completes all thirteen fields with a valid status, law kept apart from implementation | 30 |
| Names the decision family and leaves the applicability question with a qualified reviewer | 15 |
| Shows how a source change propagates, with a named release owner | 20 |
| Names a real weakness in the student's own organisation | 10 |
| Total · pass mark 70 | 100 |
Submitting session 3
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 3, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.ASSESSMENT NOW OPEN
Pop Quiz 1 — The Loop, Public Value and the PIA Backbone opens now. Sit it before you start the next session — it is how you find out whether the doctrine landed, and the practice papers may be resat as often as you like.
Sit Pop Quiz 1 →Closed book, no notes, and Coach Ritchie switches himself off while you sit it.Capabilities Covered
Controlling legal sourcesReading the PIA as a decision mapSeparating law from implementationOperating an obligation registerReleasing a legal change
Part Two · The Foundations You Cannot SkipSESSION 4
Building a Regulatory Evidence System
Why This Matters
Every later use of AI in your organisation rests on one question: can you show what was received, observed, inferred and decided, and keep them apart? A corrected return that erases the original, or a facility merged with another because the names looked alike, damages decisions long after the cause is forgotten. This session builds the evidence system your decision needs. You will learn the plain meaning of provenance, a data contract, chain of custody and identity resolution, and leave able to ask your data team whether a sampled case could be reconstructed from the original to the accountable person.
25-Minute Module
0:00 – 5:00
Four kinds of record, and stable identities
- An evidence system preserves what was received, observed, inferred and decided. A model summary is inference and should never overwrite the original observation; a corrected return should not erase what was previously submitted.
- The same facility may carry one name on a drawing, another on a licence and a third on a return. Identity resolution is the accountable process of deciding whether those are the same thing. Give each facility a controlled identifier and an alias register, with explicit links to entities, permits, measurement points and cases.
- THE DOCTRINE
Similar names are a candidate match, not proof of identity. Where the relationship is uncertain, create a resolution task rather than silently merging records.
- Test the consequence of a mistaken merge: could it attach one facility's adverse finding to another, expose a restricted record or apply an irrelevant obligation? An AI score can prioritise the review; it cannot replace the decision about identity.
A convenient master record built on a guess is a liability.
5:00 – 10:00
Provenance at entry, and a contract that fits the decision
- Provenance is where a record came from and what has happened to it since. Record origin, capture date, period, revision, responsible person, access classification, and whether it is an original, a transcribed copy, an extracted field or an estimate.
- OCR can confuse a decimal or a unit. A wrong telephone number delays a query; a wrong pressure or capacity figure may change an engineering assessment. Validate harder where an error could affect safety, finance or rights.
- A data contract is the agreement on what a record must contain and who checks it. The book proposes, for example, that a complaint record hold the allegation, source, location and consent or confidentiality handling where appropriate.
- Do not demand every conceivable field. Excessive requirements encourage workarounds and false completion. Set mandatory fields around the decision, provide a legitimate unknown status and specify the route for clarification. An honest gap is more useful than an invented value.
If the form forces a guess, the form is producing false evidence.
10:00 – 15:00
Reconcile first, and keep custody
- Cross-system analysis needs common definitions. A refinery's design capacity, available capacity and actual throughput are different measures; a flaring report may use a different period or unit from a sensor stream; a terminal stock figure may include a quantity reported elsewhere. Reconcile before training an anomaly detector, and keep the reconciliation inspectable: original values, adjustments, reason and approver.
- For conflicting measurement records, establish whether units, reference conditions and reporting periods are comparable. An assistant may propose basis differences; the measurement specialist validates any adjustment. Do not rewrite the source return to make the reconciliation disappear.
- Chain of custody is the documented handling of evidence from capture through use. For contested evidence, control access, retain originals, record who viewed, exported or amended a record, and separate changing a source from approving a decision. A correction creates an identifiable revision, never an invisible replacement.
- THE DOCTRINE
Cryptographic hashes can show whether file bytes changed. They do not prove that the content was truthful, accurately measured or lawfully obtained.
- INSIDE THE REGULATOR · THE WORKED CASE
- Inside the regulator. In a fictional upstream supervision team, a revised return conflicts with an earlier one. The team keeps both, records the candidate basis difference and assigns the measurement specialist to accept or reject the explanation.
AT THE COMPANY · THE PARALLEL- At the company. In a fictional upstream operator, the reporting lead submits the correction as a new revision linked to the earlier submission and keeps the exact files and receipt, so both sides hold the same history.
A reconciliation that cannot be inspected is just a second opinion.
15:00 – 21:00
A data model that can reconstruct a decision
- A repository stores files; a decision system preserves relationships. The book offers this schema as a proposed starting point for design, not something to adopt because a vendor can demonstrate it.
Record Core relationship Integrity question Entity Organisation and verified role Which legal person does the record concern? Facility or asset Entity, site and controlled identifiers Is this the same physical scope? Source instrument Official text, status and version Which controlling basis was used? Obligation Source, trigger and applicability Why does the requirement apply? Evidence object Original file, period and revision What was actually supplied? Assessment Evidence, criteria and reviewer What does the record establish? Decision Authority, assessment and issued record Who determined the matter? Condition or task Decision, owner and closure evidence What remains to be done? - Link an assessment to the evidence revision actually reviewed. A link that always opens the newest file cannot support historical reconstruction. Keep the company's submitted pack apart from its working collection.
- Keep the period a record describes apart from the time it became known. They answer two questions: what evidence is now accepted for the period, and what was available to the decision-maker at the time. Without that, a later corrected file can make an earlier assessment look better informed than it was. The accountable professional decides which historical decisions a correction affects.
- Preserve assertions as well as files. A model output, a company representation and a professional conclusion can use the same words with different evidential status. A citation can resolve to a real page while supporting only part of a statement: a hyperlink is navigation, not source fidelity.
- For the board: unresolved identity conflicts, critical-field errors, overdue corrections, records lacking provenance and the time needed to reconstruct a selected case. Sample cases; a system can report every field filled while the fields are unreliable.
Ask to reconstruct one sampled case before you accept any completeness statistic.
21:00 – 25:00
Write it down, and Section 4
- Before you close the laptop, list the identities and aliases your decision depends on and the one field whose error would most affect safety, finance or rights.
- The test you will apply: a reviewer can inspect the original, understand each transformation and identify the accountable person.
- Section 4 of your plan is The evidence system: identities, provenance, the data contract and a decision we can reconstruct.
Everything you build later stands on this section.
Key Terms
Evidence provenance
The origin, context, revision and transformation history of a record.
Identity resolution
The accountable process of deciding whether differently named records concern the same entity or asset.
Chain of custody
Documented handling of evidence from capture through use, appropriate to its purpose.
Period described and time known
The period a record covers, kept separate from when it was received or accepted.
Self-Check — Before You Submit
1. A supplier says its platform guarantees evidence integrity because every file is hashed. What does the book say a hash establishes?
- A. That the content is truthful
- B. Whether the file bytes changed, not whether the content was truthful, accurately measured or lawfully obtained
- C. That the record was lawfully obtained
- D. That chain of custody is complete
B. Whether the file bytes changed, not whether the content was truthful, accurately measured or lawfully obtained — Technical integrity and evidential reliability are related but different questions; a hash says nothing about whether the original was accurate or lawful.
2. Your data team proposes making every field mandatory on the new inspection form so that no record is incomplete. What is the better design?
- A. Mandatory fields set around the decision, a legitimate unknown status and a route for clarification
- B. Every field mandatory, as proposed
- C. No mandatory fields at all
- D. Let the model fill blank fields
A. Mandatory fields set around the decision, a legitimate unknown status and a route for clarification — Excessive requirements encourage workarounds and false completion. An honest gap is more useful than an invented value, which is exactly what a model filling blanks would create.
3. A fictional operator submits a corrected return eight weeks after an assessment was made on the original. The deputy wants the system to replace the original so records are tidy. What should the leader decide?
- A. Replace the original and update the assessment date
- B. Delete both and request a fresh submission
- C. Apply the correction to every historical case automatically
- D. Keep the original, record the correction as a linked revision with the time it became known, and let the accountable professional decide which decisions it affects
D. Keep the original, record the correction as a linked revision with the time it became known, and let the accountable professional decide which decisions it affects — A correction creates an identifiable revision, not an invisible replacement, and the period described stays apart from the time known. Automatic application is tempting but the book says to identify affected decisions and their review route.
Today’s Assignment
Define the evidence system your decision needs, so that a sampled case could be reconstructed from the original to the accountable person.
- Identities. The entities, facilities or assets and aliases your decision must control, and how an uncertain match is resolved and by whom.
- Provenance at entry. What your organisation records when a material record arrives, and which fields need stronger validation.
- The data contract. Mandatory fields set around the decision, a legitimate unknown status and the route for clarification.
- Corrections and time. How a correction becomes a linked revision rather than an invisible replacement, and how the period described is kept apart from the time received.
- Reconstruction. How one sampled case would be traced from the original through each transformation to the accountable person, using the book's proposed records where they help.
- The honest part. Where your organisation's records today overwrite, merge or lose history.
- Four hundred to nine hundred words.
YOUR 90-DAY PLAN
Section 4 — The evidence system: identities, provenance, the data contract and a decision we can reconstruct.
How this is marked — the rubric
| Names the identities and aliases to control and an accountable process for uncertain matches | 20 |
| Specifies provenance at entry and a data contract with decision-based mandatory fields and a legitimate unknown status | 25 |
| Shows corrections as linked revisions and keeps period described apart from time received | 25 |
| Reconstructs a sampled case from original through transformations to the accountable person | 20 |
| Names a real weakness in the student's own organisation | 10 |
| Total · pass mark 70 | 100 |
Submitting session 4
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 4, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.Capabilities Covered
Controlling identitiesRecording provenance at entryWriting a data contractPreserving chain of custodyReconstructing a decision
Part Two · The Foundations You Cannot SkipSESSION 5
The Architecture of Trust
Why This Matters
A model demonstration rarely tests the conditions your organisation actually works under: poor connectivity, an inspector offline, a supplier unavailable, a commercially sensitive record that must be reviewable but not exposed. Trust in a regulatory service is partly professional and partly architectural, and the architectural part can be tested before anyone relies on it. This session sets out what your decision's service must be built on: functional layers with clear permissions, a protected boundary with the plant, lawful handling of personal and confidential data, retrieval that respects the user, the right computation for each task, explicit exchange events between institution and company, and a fallback that works when the AI component is stopped.
25-Minute Module
0:00 – 5:00
Design around the case, in layers
- Separate intake, storage, retrieval, analytics and authorised actions, and give each service only the access it needs. Do not give an AI assistant broad administrative privileges because it makes integration easier. Permissions should reflect the task, the record classification and the consequences of misuse.
- The six practical layers: intake validates submitted files and records receipts; evidence retains originals and revisions; retrieval indexes approved material while respecting access restrictions; analytical generates candidate findings and rankings; workflow routes tasks and manages authorised actions; audit records what happened across them.
- THE DOCTRINE
These are functional layers, not a requirement to buy six products. A search assistant should not be able to alter the original submission. A draft-generation service should not automatically dispatch a regulatory determination.
Draw the permissions before you draw the product.
5:00 – 10:00
The plant boundary, and personal and confidential data
- Regulatory access to operational information should not create an uncontrolled route into industrial control systems. Prefer validated exports or approved read-only interfaces; technical teams must assess any connection to operational technology. An analytics project should never acquire the ability to change plant settings as an incidental convenience.
- Field devices need encryption, access management and a procedure for lost equipment. Offline capture should preserve time, identity and revision history on synchronisation, and an inspector who cannot reach the central service should still follow an approved inspection and escalation process.
- The Nigeria Data Protection Act 2023 provides the national legal framework for personal-data processing, and the NDPC identifies fair, lawful and accountable processing and protection of data-subject rights among its objectives. The book does not interpret the Act's sections, and neither does this session.
- Before any record goes to a model service, establish purpose, access, retention, security and applicable transfer arrangements. Personal data and confidential corporate information need related but distinct controls. A record does not become unrestricted because the institution received it. Check whether the supplier may retain inputs or use them to train other models.
Convenience is how an analytics tool ends up with a route into the plant.
10:00 – 15:00
Retrieval that respects the user and the law
- A retrieval system should return only what the requesting user may see, tested at document, case and field level. Protecting the database is insufficient if a generated summary reveals restricted content without a link. Test summaries across organisations, quotations from hidden records and indirect comparisons.
- Prompt injection, in plain words: a passage inside an uploaded document that tells the model to ignore its task or disclose information. The defence starts with a simple rule: an external submission is evidence, not an instruction. Treat it as untrusted content and restrict tools and destinations so an embedded instruction cannot create external authority.
- NIST's Generative AI Profile (NIST AI 600-1) identifies confidently erroneous content as a risk and includes source-verification guidance. It is voluntary cross-sector guidance, not Nigerian law. The legal-retrieval design that follows is the author's proposal.
- Establish the user's permission and the question's activity, date and requested decision; retrieve only eligible sources; bring in definitions, qualifications, cross-references and amendments, because a short excerpt can lose the condition that makes a provision applicable. Answer only within the supported scope, cite each material legal statement, and route the question where a source is absent or interpretation unresolved.
Test the answer's permissions, not only the file's.
15:00 – 21:00
The right computation, explicit exchange and a versioned service
Task Proposed mechanism Acceptance question Units and approved arithmetic Controlled calculation Are inputs, formula and basis valid? Record and state validation Deterministic workflow Are transitions and exceptions enforced? Source search and drafting Retrieval and language model Does the output preserve source meaning? Inspection prioritisation Evaluated statistical method Does the ranking support the defined action? Consequential determination Authorised professional process Is the decision supported and lawful? - THE DOCTRINE
A language model should not be the arithmetic authority simply because it explains a formula fluently. An approval state should arise from a retained event and permission check, not an inferred phrase.
- Define submission, receipt, validation, query and response events. A receipt identifies the pack accepted for delivery, its revision and time; delivery is distinct from adequacy. Agree how duplicates, invalid attachments, interrupted uploads and corrections are handled, so a retry does not create a second live application.
- INSIDE THE REGULATOR · THE WORKED CASE
- Inside the regulator. In a fictional authority, the intake team issues a receipt naming the pack, revision and time, and the validation event is recorded separately from any later review.
AT THE COMPANY · THE PARALLEL- At the company. In a fictional gas company, the regulatory affairs lead logs the same events against its submission. Both sides can reconcile the record even though their platforms differ.
- Ask suppliers to demonstrate export, rollback, access controls, logging, evaluation and degraded operation, and to say which parts are conventional workflow, deterministic validation and probabilistic AI. Count recurring costs, support, connectivity, foreign-currency exposure and staff time. Version the complete service: model, prompt, retrieval configuration, source collection, permissions, workflow and calculations. Rollback must not reintroduce an obsolete legal basis.
- For the board: availability, recovery performance, unauthorised-access test results, unresolved critical vulnerabilities, exportability, total operating cost and the condition of the fallback.
If the sales team cannot explain the boundary, you cannot control it.
21:00 – 25:00
Write it down, Section 5, and Practice Exam 1
- Before you close the laptop, write how your decision's work would continue tomorrow if the AI component were stopped.
- Section 5 of your plan is The architecture of trust: layers, the plant boundary, data protection, exchange events and the fallback. With it, Week 1 of your plan is complete.
- Practice Exam 1 opens now: fifteen questions, closed book, on Sessions 1 to 5, closing Week 1. Sit it before you start Session 6.
A resilient organisation can stop the AI and keep its lawful duties.
Key Terms
Service layers
Intake, evidence, retrieval, analytical, workflow and audit: functional layers with distinct permissions, not six products to buy.
Prompt injection
An attempt to make a model follow instructions embedded in untrusted material; the control is to treat submissions as evidence, not instructions.
Retrieval
Locating relevant records for a question, with access and source controls that apply to the generated answer as well as the files.
Exchange events
Submission, receipt, validation, query and response, defined so that a company and an institution can reconcile them across different platforms.
Self-Check — Before You Submit
1. A model correctly explains a fiscal formula and offers to compute the result. Under the book's computation table, what should compute it?
- A. The language model, since it explained the formula
- B. A controlled calculation with accepted inputs, an approved formula version and retained results
- C. An evaluated statistical method
- D. The case owner by hand, without retention
B. A controlled calculation with accepted inputs, an approved formula version and retained results — A language model is not the arithmetic authority because it explains fluently. It may draft an explanation from the controlled result, but it must not invent a different input basis or round without a declared rule.
2. An uploaded company submission contains a line telling the reviewing assistant to summarise all other companies' files. How should the service treat it?
- A. As untrusted content within evidence, with tools and destinations restricted so it cannot create authority
- B. As a legitimate request from the company
- C. As grounds to reject the company's application
- D. As a matter for the company to fix later
A. As untrusted content within evidence, with tools and destinations restricted so it cannot create authority — An external submission is evidence, not an instruction. Treating it as grounds for rejection is the tempting overreaction: the passage may be malicious or accidental, and accusation is never automated.
3. A fictional authority's new service passes its demonstration. The director must decide whether to rely on it next month. Which test matters most to the book?
- A. Whether the demonstration answers were fluent
- B. Whether the supplier is large
- C. Whether the model is the newest version
- D. Whether the AI component can be stopped without losing access to evidence or abandoning lawful duties, with a tested fallback
D. Whether the AI component can be stopped without losing access to evidence or abandoning lawful duties, with a tested fallback — The board measures include the condition of the fallback, and a resilient institution can stop the AI component without losing its evidence. A demonstration rarely tests poor connectivity, offline work or supplier failure.
Today’s Assignment
Set out the architecture your decision would rely on, from the service layers to the fallback, for your organisation.
- Layers. Which of the six service layers your decision touches, and what each may and may not do.
- The plant boundary. How operational information is obtained without a route into control systems, and how field capture works offline.
- Data protection and confidentiality. Purpose, access, retention and supplier terms for any personal or confidential data, without interpreting statutory sections yourself.
- Retrieval and computation. How retrieval respects the user, and which mechanism from the computation table each task in your decision needs.
- Exchange events. The submission, receipt, validation, query and response events your organisation and its counterpart must reconcile.
- The fallback. How the work continues if the AI component is stopped, and the honest part: where your organisation's current systems would fail that test.
- Four hundred to nine hundred words.
YOUR 90-DAY PLAN
Section 5 — The architecture of trust: layers, the plant boundary, data protection, exchange events and the fallback.
How this is marked — the rubric
| Maps the decision to the service layers with what each may and may not do | 20 |
| Protects the plant boundary and sets purpose, access, retention and supplier terms for personal and confidential data | 20 |
| Matches each task to the right mechanism in the computation table and shows retrieval respecting the user | 25 |
| Defines the exchange events both sides reconcile | 15 |
| Describes a workable fallback and names a real weakness in the student's own organisation | 20 |
| Total · pass mark 70 | 100 |
Submitting session 5
Write your answer in Word or Google Docs. The first line must read
Write your answer in Word or Google Docs. The first line must read
Session: 5, or the submission is refused. Upload the Word file (.docx), or switch to the Google Doc tab and paste your document’s share link.Marked against the rubric above and returned as a written letter, saved to your progress page. Do not submit until you have passed the self-check above.ASSESSMENT NOW OPEN
Practice Exam 1 — The Inflection and the Foundations You Cannot Skip opens now. Sit it before you start the next session — it is how you find out whether the doctrine landed, and the practice papers may be resat as often as you like.
Sit Practice Exam 1 →Closed book, no notes, and Coach Ritchie switches himself off while you sit it.Capabilities Covered
Designing functional service layersProtecting the plant boundaryHandling personal and confidential dataChoosing the right computationDefining exchange events and fallback