Asked on a work pack what still stops the CRS, the helper reads the pack’s items and quotes the release rules from the manual.
The helper, and this manual
From the FlyPack CAMO manual
Ask FlyPack CAMO in the top bar, or Ctrl/Cmd+K. Esc closes it — unless a dialog is open, in which case Esc belongs to the dialog.
It opens as a dock beside the screen rather than a bubble over it. Almost every answer ends in "the field is on this screen, here", and a floating panel covers the thing being pointed at. On a phone it is a sheet from the bottom, so the record stays visible above it.
Two kinds of thing it can say, and never a third
- How FlyPack CAMO works — read from these manual pages. Where a control is, why a rule exists, what a refusal means.
- What your records say — read from the database as you ask, through tools that can only read.
If neither covers it, it says it does not know and says who would. It does not reason it out from how such software usually works: a confident wrong answer about a maintenance record is the worst thing it could produce.
What it cannot do
- It cannot change anything. Every tool it has reads. Ask it to record a flight and it tells you where you do that yourself.
- It does not decide airworthiness. Whether an aircraft may fly, whether a deferral is acceptable, whether work can be released — those belong to the authorised person, which is where Part-ML puts them.
- It does not work around a refusal. If a tool refuses on grounds of role — the audit trail, for instance — it relays the refusal rather than finding the answer somewhere else.
- It sees only what you can see. Everything it reads goes through the same tenant scoping as the screens, so it cannot reach another organisation's records, and an owner's session cannot reach another owner's aircraft.
The chip that says what it is looking at
Open the dock on an aircraft and it carries that aircraft as a chip — YR-ZEN · Components. That chip is what makes "what is due on it?" answerable at all, and it is shown so it can be checked rather than guessed at. The ✕ on the chip drops it; moving to a different aircraft brings a fresh one.
"Take me there"
Most answers end in a button. It goes to the screen the answer is about, and where the answer is about a form it opens that form — Fit component on the Components tab rather than the Components tab with the button somewhere on it. That last step is the one somebody stuck enough to ask cannot take.
A button is only ever a route this application actually serves. The helper cannot invent one: it picks from a fixed list, and anything not on that list is dropped rather than shown.
Where a link needs an aircraft and the dock is not looking at one, there is no button and the answer says where to go in words instead.
"From" — where the answer came from
Under every answer, one or two chips:
- ▤ Manual · <page> — read from that page of this manual, and a link to it. Click it for the whole page rather than the three lines.
- ◉ Your records — a figure read from the database just now. It appears only when a lookup actually succeeded: an answer that fell back to the manual because a tool failed does not claim the records, which is the one lie this panel must not tell.
Nothing is stored
The conversation lives in your browser and is sent back whole with each question. Nothing is written down: no table of what anybody asked, and no second copy of maintenance data in a place nobody thought to secure. Closing the panel ends it.
The language
Answers come back in the organisation's document language — the chip at the bottom of the panel says which. Names of controls stay in the interface's own words whatever the language of the answer: the section is called "Correct the record" on screen, so it is called that in a Romanian answer too, and explained in Romanian.
The figures it quotes
Hours come back written the way your organisation writes them — decimal or hours and minutes — and so do figures the helper works out for itself rather than reads off a record. It is told the convention along with the language. Limits quoted from a manual, and man-hours, stay decimal as they do on the screens. See How hours are written.
Dates come back the same way — 21 Aug 2026, 21/08/2026 or 08/21/2026, as the organisation has chosen. See How dates are written.
The manual on a screen
Manual, at the bottom of the Organisation group in the rail. The same pages the helper answers from, for somebody who would rather read than ask. Each page has its own address — /manual/components — so a page can be sent to a colleague and survives a refresh.
Pages link to one another. A page that mentions another names it as a link, so following an explanation from the tech log to what a MEL category means is a click rather than a hunt through the list. Getting around carries a contents table of all twenty-two.
The pages live in the repository beside the code they describe, and each one declares which files it covers. A page whose code has changed since the page was last written fails the build. That is what stops this manual drifting into a description of software that used to exist — and it has caught it: the components page once said component lives never reach the due list, months after they did.
No helper on this installation
The panel needs a key for the model it talks to. Where the installation has none, the Ask FlyPack CAMO button is not shown at all rather than shown and explaining itself when clicked — but Manual is still there, because the pages are the written documentation whether or not anything reads them aloud.