Programmes · School of Mandate & Delegation

Mandate Engineering — Foundation

From instructions to bounded, verifiable, and revocable authority. An eight-week, online, cohort-based and assessed professional education programme — the first programme of ARENOMICS Institute, specified at version 1.0 and now in development.

Founding Cohort — In Development Programme specification v1.0 · 6 September 2026

Format: 8 weeks · online · cohort-based · assessed
Workload: 64 notional learning hours, about 8 per week
Award: Institute-issued, assessment-based, non-degree certificate
Programme enquiries: research@arenomics.institute

What the programme teaches

Mandate Engineering is a proposed professional discipline concerned with the design, issuance, operation, verification, modification, suspension, revocation and closure of authority granted to synthetic systems.

A mandate is a documented and revocable authorisation, issued by an identified principal to an identified human or synthetic actor, to pursue a specified outcome using defined capabilities and resources, within explicit boundaries, evidence obligations, escalation conditions and accountability arrangements.

A mandate is not necessarily a legal instrument. The programme teaches operational authority design. It does not validate a legal power the principal does not possess, replace legal advice, or create legal personhood for a synthetic actor.

A successful participant will be able to convert a real organisational objective into a documented, bounded, testable, observable and revocable mandate for an autonomous or semi-autonomous synthetic system; operate that mandate in a controlled setting; produce sufficient evidence of what occurred; and defend the resulting authority and accountability design before an independent reviewer.

The term "mandate engineering" is in independent use elsewhere; the Institute does not claim to have coined it. Its contribution is to define, operationalise, teach, test and evidence the discipline as an integrated professional capability.

Prompt engineering optimises an instruction. Mandate Engineering designs a governable authority relationship.

Each adjacent field answers one question well. Mandate Engineering integrates the relevant parts of each around one identifiable delegation of operational authority. It does not replace them.

Prompt engineering: How do we elicit a better response? — prompt, context, examples.
Workflow engineering: How should work move between steps? — workflow, automation, integration.
Access control: What can this identity technically access or execute? — roles, policies, credentials.
AI governance: What principles, responsibilities and controls apply organisation-wide? — policy, risk framework, oversight structure.
AI evaluation: How well and safely does the system perform under tests? — metrics, test results, evaluation report.
Mandate Engineering: Who may cause which consequence, for whose purpose, within which limits, under what evidence and revocation conditions? — Mandate Package, operational record, review and closure evidence.

The eight mandate questions

Every Mandate Package produced in the programme must answer eight questions in a form another person can inspect. They are a proposed ARENOMICS teaching framework, not an international standard.

Legitimacy

Who grants authority, and on what legitimate basis?

Delegate

Which identified actor or system receives it?

Outcome

What outcome is authorised, and what is explicitly not authorised?

Envelope

Which actions, tools, data, resources and communications fall inside the authority envelope?

Limits

Which limits, approval gates and reserved decisions constrain the work?

Evidence

What evidence must exist to show what happened and whether the mandate was followed?

Oversight

Who verifies, challenges, escalates and intervenes?

Lifecycle

How does authority pause, expire, revoke, recover, renew or close?

Proposed mandate lifecycle: Frame → Specify → Bound → Test → Issue → Activate → Observe → Escalate → Revoke or Close → Review.

Who it is for

AI and automation product managers
Operations and process designers
Founders and organisational leaders introducing agentic workflows
Risk, compliance, audit, assurance and model-risk professionals
Enterprise and solution architects
Technology consultants and transformation leaders
Researchers working on human–agent organisation
Professionals expected to approve, supervise, investigate or insure autonomous work

Foundation means the first professional level in the ARENOMICS pathway, not elementary AI literacy. No programming qualification is required; participants should understand the difference between a chatbot, an automated workflow and an agent that can use tools or take actions, and bring one bounded workflow suitable for controlled analysis.

What it is not

Not an AI-literacy introduction for complete beginners
Not a vendor-specific agent-builder course
Not a coding bootcamp
Not a legal, compliance, cybersecurity, audit, insurance or model-risk qualification
Not a licence to deploy or approve high-risk systems
Not an academic degree, accredited diploma or university qualification
Not the future ARENOMICS Mandate Standard
Does not require or permit uncontrolled real-money authority at Foundation level

Eight weeks

Build · Operate · Govern. The capstone begins in week one and is revised throughout; every material change produces a new version rather than erasing the earlier design. Teaching is case-first, artefact-based, tool-neutral and evidence-centred.

The Mandate Gap

Build

Distinguish an instruction, prompt, procedure, permission, policy, contract and authority-bearing mandate. Output: Case Diagnosis and Mandate Gap Audit.

Mandate Anatomy and the Authority Envelope

Build

Principal, delegate, objective, non-objectives, prohibitions, resources, thresholds, duration, termination. Output: Mandate Specification and Authority Envelope v0.1.

Identity, Delegation, and Enforceable Authority

Build

Delegation chain, identities, capabilities, sub-delegation rules, approval gates, separation of duties. Output: Delegation and Identity Map plus Permission Matrix.

Verification and Evidence by Design

Build

Objectives and constraints translated into observable tests, evidence and provenance requirements. Output: Claims-Evidence Matrix, Preflight Checklist, Mandate Package v0.2.

Issuance, Activation, and Runtime Operations

Operate

Controlled activation and run with a traceable operational record. Output: Activation Decision, Controlled Run Record, Operator Note.

Failure, Escalation, Revocation, and Recovery

Operate

Injected failure; pause, escalation, revocation, containment, recovery, reauthorisation. Output: Incident and Revocation Record, Recovery Decision, Mandate Package v0.3.

Accountability and Mandate Governance

Govern

Accountability, residual risk, control ownership, change process, continued validity. Output: Governance Review, Peer Audit, Author Response.

Closure, Integration, and Defence

Govern

Integrated package and live change challenge. Output: Final Mandate Package, Evidence Record, Oral Defence.

Workload: eight live concept seminars (12 h), eight applied studios (16 h), guided concepts and case preparation (8 h), individual laboratories and versioned portfolio work (18 h), capstone integration and peer audit (7 h), oral defence and live change challenge (3 h). The hours are notional learning hours, not academic credits.

Learning outcomes

A participant who earns the Foundation certificate will be able to:

1 · Diagnose mandate need

Distinguish an instruction, prompt, procedure, permission, policy, contract and authority-bearing mandate, and justify when a formal mandate is required.

2 · Specify a mandate

Produce a versioned Mandate Specification identifying the principal, delegate, objective, non-objectives, authority, prohibitions, resources, thresholds, duration, acceptance criteria and termination conditions.

3 · Design delegation and identity controls

Map the delegation chain, identities, capabilities, sub-delegation rules, approval gates and separation-of-duty requirements for a bounded agentic workflow.

4 · Make the mandate verifiable

Translate objectives and constraints into observable tests, evidence requirements, provenance requirements, and criteria by which an independent reviewer could determine compliance.

5 · Operate a mandate

Conduct a controlled activation and run, maintain a traceable operational record, and distinguish authorised action, exception, deviation and mandate breach.

6 · Escalate and revoke

Demonstrate pause, escalation, revocation, containment, recovery, expiry and reauthorisation procedures in response to an injected failure scenario.

7 · Govern and review

Evaluate accountability, residual risk, control ownership, change process and continued validity, and produce a defensible governance review.

8 · Defend demonstrated competence

Assemble an integrated Mandate Package and Evidence Record and defend its design, evidence, limitations and revisions during an oral challenge.

Assessment

Assessment determines whether a participant can design and govern one bounded mandate, not whether they can repeat terminology. The use of AI is expected; the learner remains responsible for every claim, authority decision, control and item of evidence.

BUILD portfolio, weeks 1–4 · 20%: Mandate Gap Audit through Claims-Evidence Matrix, preflight evidence, version history.
Controlled operational practicum, weeks 5–6 · 20%: Activation, run, incident, revocation, recovery and observation records.
Governance review and peer audit, week 7 · 10%: Independent findings, author response, residual-risk and continuation decision.
Final integrated Mandate Package and Evidence Record · 35%: Complete, traceable, internally consistent capstone dossier.
Oral defence and live change challenge · 15%: Authorship, reasoning, limitations, and competent revision under a material change.

Critical gates

No learner passes through an overall average that conceals failure in authority boundaries, evidence and verification, revocation, or accountability. Passing requires at least 70 overall, at least 70% across the final package, Evidence Record and defence combined, a minimum score in every critical-gate dimension, every mandatory artefact submitted, the controlled operation and revocation demonstration completed, and an oral defence sufficient to establish authorship.

Automatic non-pass

No average overrides these: a principal without authority knowingly represented as valid; required or prohibited actions left materially undefined; a high-impact or prohibited action performed without authorisation; no demonstrable pause or revocation path; fabricated, undisclosed-altered or misrepresented evidence; confidential, personal or protected data used without permission; inability to explain the submitted design; identity or authorship not established.

One bounded mandate — designed, issued, operated, challenged, revised and closed.

Minimum complexity

One identifiable principal with a defensible basis for granting authority; one accountable human owner; one identifiable synthetic actor or orchestrated system; a meaningful objective and beneficiary; explicit non-goals and prohibited actions; at least one downstream tool or delegated actor; at least one human approval or intervention gate; measurable boundaries; defined acceptance and rejection criteria; a controlled baseline run; an injected exception or failure; an escalation and revocation demonstration; a revision caused by observed evidence; a renewal, closure or non-approval decision; and a limitations and residual-risk statement.

The capstone is not a business pitch and not a software beauty contest. It is a demonstrable authority lifecycle for a real or realistic organisational workflow. At Foundation level, operation is sandboxed, simulated, or genuinely low-risk and reversible; real-money autonomous authority is reserved for later advanced programmes.

The Mandate Package

The central assessed object is a versioned Mandate Package, not an essay: Mandate Gap Audit · Mandate Specification · Authority Envelope · Delegation and Identity Map · Claims-Evidence Matrix · Activation and Run Record · Incident, Revocation and Recovery Record · Governance Review · Foundation Evidence Record. These are educational templates, not published professional standards.

Credential

The award is an assessment-based certificate: learning followed by assessment of published outcomes. It is not professional certification, because the assessment is linked to one programme and the Institute does not yet operate an independent, renewable certification scheme.

Title: ARENOMICS Institute Credential — Mandate Engineering: Foundation. Subtitle: Assessment-Based Certificate of Successful Completion.
Certificate statement: This certifies that the named participant successfully completed the assessed professional education programme Mandate Engineering — Foundation, programme version 1.0, and met its published competency requirements in mandate specification, authority and delegation design, verification and evidence, controlled operation, escalation and revocation, and governance review.
Qualification statement: This is an institute-issued, non-degree professional education credential. It does not confer academic credit, an accredited diploma, a degree, a professional licence, or authorisation to deploy or approve high-risk AI systems.
Titles not used: Certified Mandate Engineer · Professional Certification in Mandate Engineering · Diploma in Mandate Engineering · Accredited Mandate Engineering Qualification · any university-certificate or academic-credit language.
Participation without pass: A participant who engages with the programme but does not meet the competence threshold may receive a Statement of Participation, which does not use the credential title.

Status

Founding Cohort — In Development.

Programme Specification v1.0, dated 6 September 2026, defines the programme and its next production phase: the learner handbook, module packs, case library, templates, assessment materials and credential-verification process. It does not open enrolment, payment, accreditation claims, or a programme start date. The programme will be described here as open only after its academic, legal, delivery and technical readiness gates have been met.

Programme enquiries

research@arenomics.institute

There is no application, waiting list or fee process at this stage. Enquiries from prospective participants, employers, reviewers and prospective faculty are welcome and are answered as such.