●Distinguish the tests: importing VA instructions tests future AI behavior; direct speech only proves SAPI can deliver a line. A successful API response does not establish that the FO obeyed.
ACTIVE DEPARTMENTCABIN OPERATIONS01 / 04 ROLES
PUBLISHED TO SAPINOT YETAwaiting transmission
OBSERVED COMPLIANCEUNTESTEDAwaiting a flight transcript
01 / DOCTRINE ENGINE
Tell them what to believe.
Edit one department at a time. Select which departments to send when publishing. Each role gets its own SAPI field.
EDITING / CREW_DATA
Cabin Operations
Give announcements their wonderfully inappropriate corporate personality.
REV. 001
0 characters
The phrase we'll look for in that role's actual announcements.
Saved locally in this browser
02 / COMMAND & CONTROL
Send the company line.
This is the actual VA-import path, not a fake speech shortcut. Changes are documented as taking effect for future flights.
SAPI / IMPORTVADATA
Publish doctrine
Choose the roles to include in this update. Unchecked roles will not be included in the request.
Nothing transmitted yet.
SAPI / SAYAS
Direct speech test
Force a one-time line. Useful for connectivity testing, not evidence that the role follows the doctrine voluntarily.
Requires an active flight session.
03 / COMPLIANCE AUDIT
Did anybody get the memo?
Paste the actual unsolicited text from the SayIntentions intercom log. Keep the direct speech test separate, or it will contaminate the result.
TRANSCRIPT EVIDENCE
No transcript checked.
EVIDENCE RECORD
The verdict board
An exact marker is strong evidence the wording landed. A miss is inconclusive if the model paraphrased, delayed, or ignored it.
Cabin crewNOT TESTED
First officerNOT TESTED
Next step: publish the role instructions, start a new flight, and observe a naturally triggered announcement. A generic flight update is not evidence of adoption.