The Doctrine Card

Everything this programme rests on, on one page. Print it and keep it in the folder you take to the executive committee. These are the author’s recommended management disciplines, not additional legal duties: use them to examine a real obligation before authorising an investment.

The four executive questions

What must we do? Who is responsible? What evidence supports the answer? What happens next? If five departments give five different accounts, the company has a weakness in how it makes decisions. The test of an intelligent PIA programme: execute an obligation reliably, detect an exception early enough to act, and demonstrate what happened.

The six frameworks

#	Framework	The executive test
1	The operating intelligence loop sense → decide → act → learn	Where does the loop break — routing, delegation or funding? AI may detect the break; leadership must repair it.
2	The data foundation precondition	Does the answer have a source, a scope and a time basis? Readiness is a decision-specific acceptance test, not a programme to clean everything.
3	The autonomy ladder retrieve → draft → recommend → execute	Each rung is a different authority, earned by its own acceptance decision. Preparing a pack is not permission to submit it.
4	The value versus risk map	What decision can the output influence? Price risk beyond the fine: lost operating time, delayed cash, failed diligence, damaged confidence.
5	The sequencing discipline	Obligation and decision first, baseline, data gaps, bounded test, parallel run, then expand. After a rule change, never overwrite silently.
6	The operations excellence lens	Count obligations completed with accepted evidence. Submitted is not granted; payment initiated is not received; a model draft is not approved.

The executable obligation

Field	What it holds
Identifier and source	A stable reference; instrument, version, passage and approved interpretation
Applicability	Entity, activity, asset and period, approved by a specialist — never inferred by a model
Trigger and dates	The event or frequency; the legal date and its source kept apart from internal management dates
Owner and contributors	The person answerable; the functions providing inputs, each with a completion criterion
Evidence and closure rule	The records that prove fulfilment; the obligation closes only when approved evidence meets the criterion
Current condition and next decision	Gaps, open interpretation and exposure; the action needing authority now, and who holds it

Perform, authorise, verify are three different jobs. Rules for approved dates, calculations and status transitions; language models for retrieval, comparison and drafting.

Statuses that tell the truth

Event	What it proves	What it does not prove
Application acknowledged	Receipt	Permission
Fee paid	Payment	Satisfaction of every condition
Work order closed	Administrative completion	Repair verified, or fitness for service
Training attended	Attendance	Authorisation to perform the task
Return submitted	Transmission occurred	Receipt confirmed, or acceptance
Measurement difference reconciled	A reporting difference explained	Physical product recovered

Recommended process statuses: proposed · preparing · blocked · ready for review · approved · submitted · receipt confirmed · completed. Overdue is a time condition, not an outcome.

The obligation execution scorecard

Applicability approved · ownership assigned · evidence complete · on-time accepted completion · open high-consequence exceptions · decision age · resource decisions outstanding · assurance reconstruction · wrong-source incidents · reviewer correction effort · permission control failures · recovery demonstrated · benefit verified.

Report counts beside percentages — four of five is not eighty of a hundred. Define every measure’s denominator, evidence and owner before using it.

The ninety days

Phase	What happens	Gate
Days 1–30	Sponsor and owner appointed; entity, asset, sources and interpretation mapped; decision, evidence chain and manual process defined; baseline recorded; reference cases built; finance brought in	Map, evidence index, workflow, baseline and signed charter
Days 31–60	The smallest useful application — retrieval, comparison or completeness checking — tested on realistic sources, wrong versions, missing conditions, conflicting dates, wrong assets and denied access; manual continuation practised	A readiness decision based on evidence — not a demonstration
Days 61–90	Live work inside the accepted boundary; total effort measured; weekly exception review; criteria never weakened to manufacture success	Scale, narrow, repair or stop

The twelve leadership commitments: approved applicability · named ownership · controlled sources · dependable identity and time basis · documented decision rights · reproducible calculations · proportionate human review · limited permissions · visible exceptions · tested recovery · measured outcomes · sustained ownership.

The 15 sessions and the game plan they build

#	Session	Game-plan section
1	Why the PIA Belongs in the Operating Model	Section 1 — Where we are today: the obligation that matters most and the honest answer to the four questions.
2	The Reader's Toolkit: Six Ideas for the Executive Meeting	Section 2 — The one-page obligation trace and the first fix it needs.
3	From Legal Text to Operating Decisions	Section 3 — The executable obligation record.
4	The Intelligent PIA Company: Visible Authority	Section 4 — Sponsor, owners and decision rights.
5	The PIA-Ready Data Foundation	Section 5 — The evidence index and the data gaps, each with an owner.
6	The Regulatory Intelligence Engine	Section 6 — The AI role: layers, rules versus model, and the approval boundary.
7	Licensing and the Asset Lifecycle	Section 7 — The permission dependency schedule.
8	Measurement and Custody Transfer	Section 8 — The quantity evidence chain and reconciliation rule.
9	Host Communities, Environmental Evidence and Methane	Section 9 — The stakeholder or environmental evidence chain, and the unsupported claim.
10	Safety, Supply and the Midstream–Downstream Chain	Section 10 — The critical handoff and where its evidence breaks.
11	AI Governance for PIA Decisions	Section 11 — The governance record and authority boundary.
12	Audit Readiness and Controlled Autonomy	Section 12 — The submission package and the agent boundary.
13	Fiscal Intelligence, Retirement and Nigerian Capability	Section 13 — The honest capital case and the capability we will own.
14	The Board Scorecard and the Investment Paper	Section 14 — The board scorecard and the decision we will ask for.
15	The Ninety-Day PIA Game Plan	Section 15 — The assembled, signed 90-Day PIA Game Plan with its executive summary.

ERW CommandPIA · built on The Intelligent PIA — An Operating Doctrine for AI Leadership and Petroleum Industry Act Execution in Nigeria by Ritchie Wingo. Leadership training, not legal advice. Back to the programme home →

THE INTELLIGENT PIA LEADERSHIP PROGRAMME

The Petroleum Industry Act belongs in the operating model.