AIRS-J/1 · Instruments

The Standard is not an instrument.

An instrument is a delivery implementation that generates observations. The rubric contains no dependency on any instrument's interaction design, data model or vendor. Any instrument meeting sections 8, 9 and 10 of AIRS-J/1 and the published approval criteria may carry the Standard, including instruments AIR APAC does not own, does not operate and does not profit from.

Approval criteria: planned, not published

What an instrument is

Section 8, verbatim.

An eligible instrument type is not itself an approved instrument. Approval is against published criteria that do not exist yet; they are a blocking item (Annex A, item A12) before v1.0.

8.1 Instrument eligibility and approval. Observations may be generated for certification only through an instrument approved by AIR APAC against Sections 8, 9 and 10 and the published instrument-approval criteria required by Section 16.3. No instrument is approved under this draft. The following instrument types are eligible to seek approval for v1.0:

  • scenario simulation with retained decision trace;
  • assessed live exercise with an authorised assessor;
  • structured work-product review against a defined brief.

8.2 Self-report is not evidence. Self-assessment, survey response, declared experience, training attendance and manager endorsement generate no observations and contribute nothing to a score.

8.3 Minimum observations. Each dimension requires a minimum of three independent observations arising from distinct decision points. Two observations from the same decision point are one observation. A dimension below the minimum is scored Insufficient Evidence and cannot be certified.

8.4 Assessment volume. The minimum implies 27 observations. On the current scenario-simulation form, a single scenario yields approximately five to nine observations across the nine dimensions, implying three to five scenarios for a certifying assessment.

Assumption to be confirmed. The five-to-nine figure is drawn from existing scenario design, not from candidate data. Total assessment time per track must be measured in pilot and published before issue. If the real figure is materially lower, the practical answer is more decision points per scenario, not a lower minimum.

8.5 Contextual localisation. Scenario setting, sector, role titles, organisational norms, regulatory context and language may be localised. The decision points, the dimensions they elicit, the stakes profile and the anchors applied may not. Localised scenarios require AIR APAC approval before use in certification.

8.6 Decision-point integrity. Where an instrument reveals consequence, the candidate's position must be recorded before revelation. Post-revelation revision is an observation under P2, not a correction to P1. An instrument that permits silent overwriting of a committed position is not approvable.

8.7 Evidence minimisation. Transcripts retain only what the rubric requires: decisions, artifacts, sources consulted, stated rationale, revisions, and phase timings. Keystroke capture, affect inference, video analysis, biometric signals and private reflection are prohibited as scoring inputs.

8.8 Derivability. Every observation must be traceable to identified evidence in the transcript. An observation whose evidence cannot be pointed at does not exist.

8.9 Accessibility and accommodations. Every certifying instrument must meet published accessibility requirements and support a documented accommodations process. A candidate may request an access support before assessment and receives a written decision with reasons. Approved supports must preserve the construct, decision points, stakes profile and assessment integrity; they are recorded under Section 7.1.1 and Annex C. A denial or material misapplication is appealable under Section 18.6. Instrument requirements, request procedures, decision authority and assessor guidance must be published before v1.0 issue.


Candidate instruments

Named, with no presumption.

InstrumentOwnerEligible typeStatus
StepSimExeter Labs (separate organisation and repository from the Standard)Scenario simulation with retained decision traceCandidate · not approved
First candidate instrument named under draft v0.3. Not approved. No presumption of approval: the criteria do not exist yet, and when they do they are applied identically to this instrument and to any third party's. The instrument is deliberately built and held in a separate organisation and repository from this Standard. That separation is the structural expression of section 16.3, not an accident of the org chart. There are no screenshots, feature lists, or product pages for it on this site; the restraint is the argument.

When an instrument is approved, this table gains a row with the published approval decision and evidence summary, whatever the outcome. Where an AIR APAC-affiliated instrument fails a criterion, it is not approved and the failure is stated here.

Neutrality, as written

Section 16, verbatim.

16.1 AI Readiness Index. Rates organisations on public signals. Different unit of analysis, different signal model, different evidence base. An organisation's Index position is not a function of its employees' certifications, and a certification confers no Index effect. The two must not be co-marketed in a way that implies conversion between them.

16.2 Vendor Certification. Assesses products and providers against a separate standard. Cross-reference to be added at v1.0. A vendor certification says nothing about the judgment of any individual using the product.

16.3 Instrument approval and instrument neutrality. StepSim is the first candidate instrument named under this draft. It is not approved for certification, because no instrument may be approved until the criteria required by Annex A are published and retained approval evidence exists. StepSim is not the Standard. Any instrument satisfying Sections 8, 9 and 10 and the published approval criteria may generate observations under an issued version of AIRS-J/1, including instruments AIR APAC does not own, does not operate and does not profit from.

This is deliberate and is a term of the Standard, not an aspiration:

  • The rubric in Section 7 contains no dependency on any product's interaction design, data model or vendor.
  • Instrument approval is against published criteria, applied identically to AIR APAC's own instruments and to third-party instruments.
  • AIR APAC publishes the approval decision and evidence summary for each instrument.
  • Where an AIR APAC instrument fails an approval criterion, it is not approved.
  • AIR APAC publishes the list of approved instruments and their owners.

The consequence is accepted: any instrument, including a competitor's, can carry this Standard on merit. That is the condition under which the Standard is worth holding.


Third parties

How a third party will apply.

There is no application process today, because the approval criteria do not exist yet. Publishing them, and the retained approval evidence they require, is blocking item A12 before v1.0. When they are published, application will be open to any instrument, on identical criteria, with the decision and evidence summary published either way. If you are building toward sections 8, 9 and 10 and want to be told when the criteria open, say so through the delivery-partner enquiry.

Contact AIR APAC →
Assess readiness