- 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>
- more_menu helper (menu / menu-item styles): each section keeps its main
action as a button; imports, exports, printing and tools move under More
(flights, logbook, logbook entry, documents, inspections, fleet)
- Aircraft header: More with status report and, for owners, access &
sharing, edit, .sam.zip and records package; Access & Sharing and Oil
Analysis tabs removed (oil analysis is under Oil & Fuel with a switch)
- Logbook: Print selected appears once an entry is ticked; filters apply on
change; dates use fmt_date (also AirTrail, notes, audits, About)
- Header shows the role on the aircraft and hides the usual Available badge;
no second Grounded badge on the Overview; AD DRS import listed once
- Flights: stat cards 2x2 on phones; By year opens visibly, only with more
than one year; duplicate + Log Flight removed
- Remove unused hello_controller.js; guide and README updated
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AC 120-78B chapter 3:
- Every change to logbook entries, sub-components, signatures, inspection
records, AD compliance, major records, W&B, components, squawks and
documents is kept as a RecordVersion (who, IP, when, field changes),
hash-chained per aircraft; versions can't be edited or deleted. Shown on
each logbook entry and in Activity -> Record history
- Nightly job: SQLite online-backup copy to storage/backups, verified
(integrity_check + record counts), pruned to the configured number; then
an integrity check of the history chains and every signature's seal and
fingerprint. Results on Admin -> About ("Back up and check now"); admins
are emailed on failure
- Software versions recorded (first/last seen) on Admin -> About
- Records package (Access & Sharing): logbook entries PDF with signatures,
signatures.csv, record-history.csv, self-contained status report HTML,
the .sam.zip, and a README, for the FAA/NTSB or a buyer
- Legacy (paper) records: documents can be marked as legacy records;
aircraft have an "electronic records since" date (status report, package)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Sign an entry: review exactly what's certified, choose a current
certificate (eligibility checked: pilot only for preventive maintenance,
inspections need their result and time), re-enter the password or sign
in again with SSO (prompt=login, within 5 minutes), and confirm the
"Certified by" statement (43.9 return to service, 43.11(a)(5) for
inspections, preventive maintenance for pilots)
- The signature stores signer, certificate, statement, UTC time, how they
authenticated, IP/browser, a SHA-256 fingerprint of the entry's content
and a readable snapshot; an HMAC seal covers the signature record. Status
shows Valid / Superseded / Altered since signing. The signer is emailed
- Signed entries (and their sub-components) can't be edited or deleted;
a correction entry, once signed, supersedes the original (kept)
- Owners invite an outside mechanic by email to sign one entry: one-time,
14-day link; they create or use their own account and certificate and
see only that entry
- Admins can disable accounts (signed out, can't sign in or sign; past
signatures kept); users with signatures can't be deleted
- Printouts show the electronic signature and fingerprint; archives carry
signatures (marked imported, with their origin) and corrections
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Once a component is chosen, its sub-components are offered on the entry
form (and the squawk Resolve page); ticked ones are saved with their
total time and time since service, worked out from the airframe total
time like the component's (editable; blank before it was installed)
- Entry page and printed PDFs list each sub-component with its serial
number and times; parts without an overhaul type read "Since service"
- Archives carry them: the original format's list of components per entry
(first = the entry's component, the rest = sub-components)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An entry can link a component (engine, propeller…) and records its total
time and time since overhaul at the entry; picking the engine or prop log
selects that component and fills its current times (editable). Squawk
fixes carry the squawk's component
- Components have an overhaul type (major, factory overhaul, factory new),
shown as SMOH / SFOH / SNEW
- Printouts: engine and propeller entries add the serial number, total
time and SMOH/SFOH (blanks when no component is linked); airframe total
time is labelled as such; full-page layouts draw a box around each entry
- Archives carry the entry's component and times (the original format's
components / component_hours), no longer dropped on import
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Print one entry or several (tick them on the logbook list) as a PDF:
Avery 5164/8164 or 5163/8163 adhesive labels (start at any label on a
partly used sheet), or half-letter / letter pages
- Each entry has the aircraft and serial, log, date, total time in
service, the work, the signer's name and certificate, and a blank line
to sign by hand; inspection entries with a recorded result get the
43.11(a)(5) statement unless the text already certifies
- Labels: long entries shrink to fit, then continue on the next label.
Pages: entries follow one another with their signature lines, numbered
- Generated with Prawn (built-in fonts; unsupported characters become ?)
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>
- Logbook entries record the signer's kind of certificate and number and
an inspection's result; maintenance and inspection entries list what
43.9 / 43.11 needs that's missing (flagged, not enforced). Transcription
reads the certificate details too
- AD compliance records the method (inspection, terminating action, AMOC,
not applicable) and the AD revision complied with, filled in from the AD
when blank; the method sets the permanent / N/A flags
- Maintenance status report (91.417(a)(2)): total times, life-limited
parts, time since overhaul, inspection and AD status, major alterations,
open discrepancies; print or save as PDF; on maintenance share links too
- Archives carry the new fields
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Rails 8.1 + SQLite rewrite of marbindrakon/simple-aircraft-manager,
designed to self-host as a single container (Solid Queue/Cache/Cable,
Active Storage on disk, Hotwire + importmap, Tailwind).
- Airworthiness engine ported from health/services.py (ADs, grounding
squawks, inspection recurrency, component replacement)
- Hours updates and flight logs cascading to in-service components,
optional airworthiness enforcement
- Components, squawks, ADs, inspections, logbook, documents, major
records, oil/fuel consumption stats and charts, activity log
- Admin/owner/pilot RBAC and public share links (status/maintenance)
- Docker Compose and Kamal deployment, env-driven production config
- Service and integration tests
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>