Launching with OC-AISF and OC-AIRT · Team programmes scoped on enquiryODA3 Institute ↗
Sign inEnquire
Overview/Methodology
Evidence standard

How every course is built and reviewed.

Every case is source-reviewed before it anchors course content. Every framework reference is checked at clause or article level in the approved specification. This page shows the method, the current review status and what is not yet in place.

§ 01Method

From evidence to exercise.

Approved course specifications will name the source material, the system or failure path examined, and the criteria used to review practical work.

01Source

State what the evidence documents

State what a public case, publication or standard actually documents, and nothing beyond it.

02System

Trace the system

Trace the relevant workflow and name its trust boundaries.

03Exercise

Publish the exercise

Publish scenario, inputs, task, output and review criteria before enrolment.

§ 02Corpus to curriculum

Proposed case references across the curriculum.

A working map of public cases to planned courses. Each connection needs source review before it appears in a published course specification.

Notably absent

Each case is source-reviewed before it anchors course content. Control requirements are stated, with their source and interpretation, in each approved course specification.

§ 03Frameworks referenced

Where the curriculum meets regulation.

Draft course descriptions identify these frameworks as possible teaching references. Clause and article mappings require review in each approved course specification.

Referencing a framework does not mean its publisher has approved or endorsed a course.

§ 04Publication criteria

Proposed publication criteria.

Four criteria proposed for every course before launch. They are under review and are not yet adopted policy.

Proposed · under review
Source

Trace material to its source

Identify the incident, research record or standard behind every teaching claim, and separate documented fact from inference.

BasisCited public disclosures, standards and regulation
Failure path

Understand how systems fail

Examine how a system can fail before selecting or evaluating a defensive control.

BasisAttack chain examined before the control
Precision

Read requirements precisely

Teach the difference between required, recommended and optional control language.

BasisIETF RFC 2119: SHALL, SHOULD, MAY
Revision

Revise when evidence changes

Review courses against new findings and record every substantive change.

BasisChange recorded in the course specification log
§ 05Teach with us

Founding instructor cohort.

Practitioners appointed against a written standard for each domain. Named instructors are published once appointed.

Register faculty interest