What people can do on an aircraft now comes from their role there, and
administrators set what each role allows (Admin → Roles).
- Roles are installation-wide sets of permissions (31, grouped as flying,
squawks and notes, maintenance records, imports and exports, the
aircraft, notifications). Seeing an aircraft's records needs none.
- Built in: Owner (always every permission, so an aircraft can always be
managed), Mechanic (shop maintenance: logbook, signing, components,
inspections, ADs, squawks, reminders), Pilot (what pilots could do
before) and Viewer (view only). Administrators can change all but
Owner's, and add their own; a role can be deleted once nobody has it.
- Existing owners and pilots keep exactly what they could do.
- Admin → Users → a user lists their role on every aircraft, to change,
remove or add. On the aircraft's Access page, anyone who manages people
hands out roles, but only an Owner can give or take away Owner, nobody
changes their own (except administrators), and an aircraft always
keeps an Owner (AircraftAccess).
- Controllers declare the permission each action needs; a request that
changes something with none declared is refused (and raises in
development and tests), and a test walks every route to check.
- Weekly reminders and overdue alerts go to roles that get reminders;
the DRS reminder also needs Manage ADs. The API follows the person's
role; its owners_only error is now not_permitted.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Setup checklist on a new aircraft's Overview (owners): components,
standard inspections, DRS AD import, registration/airworthiness
certificate, weight and balance; hideable per device
- Log Flight: "Save and log next leg" reopens the form on the same date,
starting where the leg ended
- Component form: limits in two collapsible groups (replacement and expiry;
overhaul and TBO), open when in use
- Squawk form warns what "Ground Aircraft" does
- Logbook entry form: inspection result only for inspection entries
(show-when controller); document names default from the file
- Dates in pickers, the activity log, airworthiness lines, search, audits
and transcription notes use the app format
- No duplicate Report Squawk button on Squawks; "Record service" label
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Views use lazy t(".key") lookups; sentences with values or links stay
whole (interpolation, _html keys); counts use one/other plurals
- Stored-value labels (statuses, types, priorities...) are LabelSets read
from labels: in the current locale; field names and validation messages
under activerecord:; flash and activity text under flash:
- Services, models, helpers, mailer subjects, the logbook PDF, procedures
templates, records package README and transcription warnings localized;
the PDF reuses LogbookEntry#certification_statement instead of a copy
- Scripts read js: strings from a JSON tag via app/javascript/i18n.js
- Dates through I18n.l (app, weekday, month_year, long formats); html lang
follows the locale
- APP_LOCALE picks the language (falls back to English); missing
translations raise in development and tests
- README: Translating section and APP_LOCALE
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shown on Admin -> About, in the software history, records package, procedures
and sam:doctor; release notes in the app under Help.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Admin → Off-site Backup: connect a Google account with your own OAuth
client (drive.file scope; refresh token and secret encrypted)
- Nightly after the verified database backup: upload the gzipped snapshot
(newest N kept, Settings) and every uploaded file not yet copied
- Restore test downloads the newest copy, opens and checks it, and checks
sampled files against their checksums; failures emailed to admins
- About, procedures document, policy completeness and audits use it
- offsite:restore_files rake task; restore steps in the admin guide
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Admin → Recordkeeping Procedures: generated procedures document
(2.2.11 / 3.2.8) from the system setup plus owner-entered details;
adopted as numbered, immutable revisions; included in the records package
- Admin → Records Audits: periodic QC checklist (3.2.8.5) combining app
checks with a restore test, sampled entries vs. source documents and a
user review; next due date on About and in admins' weekly reminder
- User instructions at /help/records, linked from the logbook and signing
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>