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>
- Requests run in the viewer's zone: Profile -> Time zone, else their
device's (a tz cookie set from the browser), else the installation's;
times show in it and "today" is the local date (a new flight's date)
- Docker's TZ sets the installation zone (default UTC): scheduled jobs run
on its clock (recurring.yml), and it's used before a device's zone is known
- The weekly reminder email is worked out in the recipient's zone
- Signatures, record history and exports keep exact UTC timestamps
- users.time_zone; README, .env.example and guide updated
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>
- 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>
- Users add their FAA certificates (kind, number, optional expiry) on
their profile; admins see them on the Users list
- "Sign as" on new/edited logbook entries and the squawk Resolve page
fills the signer's name, kind of certificate and number (expired
certificates aren't offered); deferrals default to mechanic for users
with a mechanic certificate
- Weekly reminder lists certificates expiring within 60 days (or lapsed
in the last 30), even when nothing else is due
- Preventive maintenance templates keep a certificate already chosen
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Entries transcribed by Claude are unverified (with Claude's confidence)
until an owner checks them against the scan: badge, filter, "mark
verified" stepping through the rest
- Preventive maintenance templates on new logbook entries, keyed to Part 43
Appendix A(c), setting the entry type and pilot certificate (43.3(g))
- An STC's ICA can become a tracked recurring inspection, linked from its
major record
- Weight & balance: history of empty weight/CG (linked to the 337 that
changed them), loading stations and CG envelope from the POH, and a live
calculator for takeoff and landing weight/CG; shown on the status report
- New ADs: weekly Federal Register search per aircraft (aircraft, engine
and propeller models, or custom terms); track or dismiss each; included
in the weekly reminder
- Archives carry the new records; brakeman: explicit params, reviewed
About-page links
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Squawks: defer an inoperative item under 91.213(d) once each condition
is confirmed (pilots may too); deferred items stop grounding and are
listed for awareness. Resolving can record the fix as a logbook entry
(43.9 fields) or link an existing one
- Expiration dates on components (ELT battery, 91.207(c)) and documents;
new document types (registration, airworthiness certificate, insurance,
radio license). Expired replacement-critical parts and an expired
registration (91.203) ground; others warn; registration warns 90 days out
- Standard inspections: one click adds annual, 100-hour, 91.411, 91.413,
ELT (91.207(d)) and VOR (91.171) checks with the right rules, skipping
ones already tracked and linking annual to 100-hour
- Weekly Monday reminder email to owners when something needs attention;
profile opt-out; admin "send me this week's reminder"
- README feature table updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>