- POST /aircraft/:id/draft_batches turns a visit's work items into one
unsigned entry per logbook, signed in the app (by a user with a
certificate, or a mechanic through a returned or emailed invitation link).
- The squawks they resolve and inspections they complete (with their result)
are held until every entry is signed, then applied, attributed to the last
signer; draft_batch.completed webhook. A draft never clears a squawk alone.
- Drafts are for owners (integrations act for one, drafts:write scope);
unsigned drafts can be withdrawn; lookup by external_ref.
- The signing and entry pages show where a draft came from and what signing
will do.
- The suggested recordkeeping procedures describe the API once it's in use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Personal tokens (Profile → API tokens) act as their owner; integration
tokens (Admin → Integrations) reach chosen aircraft and scopes, and their
writes name the person they're for (SAM-On-Behalf-Of). Tokens are stored
hashed, shown once, revocable, with last use recorded.
- GET aircraft, components, due list, inspections, ADs, logbook entries and
squawks; POST/PATCH squawks with external_ref links to the other system.
- Idempotency-Key for safe retries, paging, JSON errors, rate limits.
- Record history keeps the token with each change (in the hashed payload).
- Webhooks (squawk created/updated/resolved, entry signed), HMAC-signed,
retried, never sent to the server itself; deliveries listed for admins.
- The outbound address check is shared by AirTrail and webhooks; reporting a
squawk is announced the same way from the form and the API.
- docs/guide/api.md: the API reference.
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>
- Delete methods nothing calls: BackupRun.last_good, EntrySignature#short_id,
Sso#issuer_origin, InspectionType#effect_label and #latest_record_for,
ApplicationHelper#airworthiness_dot, Airworthiness::Status#can_fly? and
FlightStats#shortest_flight (tests now check red? / longest_flight)
- Routes: sessions and passwords limited to the actions that exist
- Theme toggle: drop the unused button target
- Action Cable was never used (no broadcasts or streams): async adapter in
production, solid_cable gem, cable database and app/channels removed
- Empty system test setup removed with capybara and selenium-webdriver
- Compliance: one due_result helper for overdue / due soon; inspections use
next_due for the date, as ADs do
- applicable_to moved into SharedRecordHistory (was identical in ADs and
inspection types)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- 10 failed sign-ins in a row (password, authenticator code, or password
at signing) lock an account for 15 minutes from any address; the user
is emailed; admins can unlock. Same message as a wrong password.
- Passwords: at least 12 characters (max 72), refused if found in Have I
Been Pwned (k-anonymity range API; fails open; PWNED_PASSWORDS_CHECK=false)
- Optional TOTP (authenticator app) with 10 recovery codes for password
and emailed-link sign-in, and at signing (auth method password_totp);
codes accepted once; admins can reset; SSO sign-in unaffected
- Demo/test passwords updated; guide, README and procedures document
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>