Build an AI companion · session 2 of 4

Rules it can follow, and you can check

The rules are the job description. Short ones get followed; clever ones get ignored. This session writes the short ones.

Six decisions on setting rules: saying what it is for, banning the decisions it may never make, teaching it to admit a gap, keeping rules short, deciding who owns the rules, and testing that a rule actually holds.

Corporate pricing on request. Course funding application status: pending.

Session2 of 4 in Build an AI companion
Decisions6, one correct answer each
Marker1 printed point on the desk board
Recordthe five fields, same as every run

The scenario

Setting the rules a companion must follow at the post

A companion with no rules answers every question as though it were equally qualified. That is what makes it feel impressive in week one and dangerous in week four.

Rules do not make it less useful. They make it useful in a way you can check: this is the job, these are the things I do not do. This is what I say when I do not know.

The sheet is short on purpose. Five lines that hold beat a page that nobody can verify.

The six decisions are the ones that actually go wrong on a quiet shift. They are, in the order the run puts them:

  • Saying what the companion is for, in a line
  • The ban list: no decisions, no identities, no confidential material
  • Teaching it to admit a gap instead of filling it
  • Keeping the rule sheet short
  • Who owns the rules, and who may change them
  • Testing that a rule actually holds

What changes, and for whom

Three people, three different changes

For the officer building it

You want it to behave the same way every shift

Rules are how that happens. The session shows what to write, how short to keep it. The one line every companion needs - what to say when it does not know.

For the supervisor

An unruled companion invents confidence

The most dangerous answer from a companion is a confident one it had no business giving. Rule two in this session is the ban list, and it is there for a reason.

For the agency

The rules are an agency document, not a personal one

Whoever writes the rules owns the behaviour. This session makes that explicit, so a companion never becomes the officer's private system.

These are descriptions of the work the training addresses. They are not client results and not a promised saving.

What the officer does, in order

One run, start to record

About ten minutes at the post, on the officer's own phone, with a supervisor on site.

Scan the marker at the desk board

One printed marker where the rules sheet is kept.

Write the rules

Six decisions that build the sheet: purpose, bans, admitted gaps, length, ownership and a test.

See the ban list in place

The overlay marks the three questions that go back to a person, every time.

Write the record

One row, the same five fields as every run in the department.

The trainee list

Every session writes the same record, so four sessions make one page of that officer's training history, and the same five fields are asked of the newest officer and the most senior one - which is the part of it that is fair. The run is written to the agency's list in the five fields the checklist reads.

This page is the session. The run itself is on the player: open it here - the practice run needs no camera. It is session 2 of 4 in Build an AI companion.

A completed session produces one row, in these five fields

This is post training, so there is no assessor to satisfy - but the record matters anyway: it is how an agency shows what its officers were trained on, in what order, and when.

The five fields every run here writes, plus the score and the time on task, kept in the agency's own record.
FieldWhat it carries
NameAs written in the agency's own staff record. Nothing else is stored about the officer.
NRIC / FINThe last four characters only. The full number is never entered and never leaves the phone.
Training providerWhichever name the checklist route puts here: the agency's own name when the agency delivers the training in-house, or the service provider's name when a provider delivers it - in that case the checklist also asks the agency to submit the provider's invoice showing simulation training was used. The field is left blank on purpose: it is typed, not assumed.
Course titleStates the technology: the training programme or session plus Augmented Reality (AR) Simulation Training.
Date of trainingThe date the run was completed, written from the device at the time of the run.

The record lives on the officer's own phone until it is exported or printed, so the habit is: run it, then save the list. The house standard is 80 per cent, which is a fair bar for six decisions, and a failed run is a re-run rather than a mark against an officer.

What this package does not claim

The limits, stated on the page rather than found later

Every course here is honest about what it is and what it is not, because a package that oversells itself is the one that lets an agency down in front of an assessor. Read these before you book anything.

  • This session does not set your site's policy. It teaches how to write the rules down so they are followed and checked.
  • It is not a SACE programme and does not satisfy a licence-renewal requirement.
  • It does not permit a companion to hold personal details or site access information, whatever the rules say.
  • It is not a substitute for a post order. Rules must not contradict the agency's own orders.

Questions about this session

Straight answers

How many rules should it have?
As few as possible. Five or six short lines beat two pages - a long rule sheet gets ignored by the companion and by the reader.
What should it say when it does not know?
Exactly that, plus who to ask. "I do not have that information - ask the supervisor" is a correct and useful answer.
Who owns the rules?
The agency or the supervisor, in writing. An officer can suggest a change; the rule sheet is a site document.
Is this a SACE programme?
No. It is post training, not a SACE licence programme.

Build an AI companion · session 2 of 4

Run it on your site before your officers do

Fix one marker at the real point, open the session on a phone, and see whether the overlay holds where your officers actually stand. That is a fair test, and it takes three minutes.

Corporate pricing on request. Course funding application status: pending.