Gradient Descent for Aviation

Why Aviation Fits

Aviation documentation has the tightest standards of any civilian industry. A maintenance procedure doesn't just need to be correct — it needs to be correct in a way that a mechanic at 3 AM in a hangar in Anchorage can follow without interpretation. An Aircraft Flight Manual doesn't just describe the aircraft — it defines the legal operating envelope. A Supplemental Type Certificate package doesn't just document a modification — it proves the modification doesn't kill anyone.

The standards are explicit, layered, and ruthlessly specific. 14 CFR Part 25 tells you how to certify a transport aircraft. AC 25-11B tells you how to present electronic flight displays. ATA iSpec 2200 tells you how to structure a maintenance manual down to the paragraph numbering. MSG-3 tells you how to develop a maintenance program. The loss functions aren't suggestions — they're airworthiness requirements.

The other advantage: volume and lifecycle. A single type certificate can generate 50,000 pages of documentation. That documentation lives for 30-50 years, revised continuously as ADs are issued, service bulletins are incorporated, and operational experience accumulates. Aviation already does gradient descent across decades. It just does it manually, with pen-on-paper signoffs and revision bars in the margins.

Maintenance Procedures — AMM/CMM

Aircraft Maintenance Manuals and Component Maintenance Manuals follow ATA iSpec 2200 structure. Every procedure must be executable by a certified mechanic without additional interpretation. Ambiguity in a maintenance procedure is a safety event waiting to happen.

# .persona
You are an aviation technical writer specializing in ATA
iSpec 2200 compliant maintenance documentation. You review
procedures for: unambiguous step sequencing, correct
tool and part number callouts, safety warnings placement
per ATA conventions, torque values with tolerances, and
compliance with the applicable CMR/ALI requirements.
Every instruction must be actionable by an A&P mechanic
with no additional guidance. One improvement per round.
Read .crumbs. DONE when the procedure would pass a DER
review and an airline's technical publications audit.

# .tools
ito
cat
grep
wc

🍞 10 times toast amm-32-11-01.md "improve — ATA iSpec 2200, unambiguous, executable"

a2f3b4c  step 3 says "remove the actuator" before step 2 depressurizes the hydraulic system — reorder, add WARNING for residual pressure
b4d5e6f  torque value in step 7 says "tighten to specification" — replace with: torque to 45 in-lb ±5 in-lb per CMM 32-11-01 Table 201
c6e7f8a  CAUTION missing before step 9 — bonding jumper must be installed before disconnecting fuel line per AMM 28-00-00
d8f9a0b  part number callout references NAS1352-4-8 but current effectivity uses NAS1352-4-8A — update per IPC revision 47
e0a1b2c  step 12 says "inspect for damage" — specify: inspect bearing surfaces for scoring, pitting, or corrosion exceeding limits in CMM Figure 401
f2b3c4d  tool callout missing for step 5 — add: use torque wrench P/N SNAP-TW-100 or equivalent, calibration current per 14 CFR 43.13
a4c5d6e  close-up procedure doesn't reference rigging check — add step: verify flight control rigging per AMM 27-00-00 before return to service
b6d7e8f  WARNING for hydraulic fluid contact should precede the removal step, not follow it — move per ATA warning placement conventions
c8e9f0a  return-to-service statement missing — add: "perform operational check per AMM 32-11-01 paragraph 401 before aircraft release"
DONE after 9 rounds

"Tighten to specification" has caused more maintenance errors than almost any other phrase in aviation documentation. The mechanic doesn't have the specification memorized. The torque value needs to be right there, in the step, with the tolerance. Each round replaces one ambiguity with one specific, executable instruction.

Supplemental Type Certificates

An STC documents a modification to a type-certificated aircraft and proves it meets airworthiness requirements. The package includes engineering substantiation, instructions for continued airworthiness, flight manual supplements, and the master drawing list. The FAA or EASA reviews every page.

# .persona
You are a DER-level aviation engineer reviewing STC
documentation packages. You check for: compliance with
the applicable certification basis (14 CFR Part 25 or
Part 23), completeness of engineering substantiation,
proper documentation of assumptions and safety factors,
ICA completeness per 14 CFR 25.1529 / AC 25.1529-1A,
and consistency between the engineering data and the
flight manual supplement. One finding per round.
Read .crumbs. DONE when the package is submission-ready.

# .tools
ito
cat
grep

🍞 12 times toast stc-package.md "review — certification basis, substantiation, ICA completeness"

a1c2d3e  certification basis lists 14 CFR 25.301 (loads) but substantiation doesn't address fatigue per 25.571 — add damage tolerance analysis or safe-life substantiation
b3d4e5f  weight and balance change documented as +47 lbs but CG envelope impact analysis missing — add worst-case CG calculation
c5e6f7a  electrical load analysis shows 28V system but doesn't account for voltage drop at end-of-harness — add wire gauge justification per AC 43.13-1B Chapter 11
d7f8a9b  EMI/HIRF compliance claimed by similarity to baseline installation — similarity analysis not documented, add point-by-point comparison per AC 20-158A
e9a0b1c  flight manual supplement references "Normal Procedures" but doesn't include emergency procedures for new system failure modes — add per 14 CFR 25.1585
f1b2c3d  ICA section missing inspection interval justification — MSG-3 analysis or engineering order needed to substantiate 4,000 flight hour interval
a3c4d5e  master drawing list revision B but engineering substantiation references revision A drawings — reconcile
b5d6e7f  structural modification uses 2024-T3 aluminum but stress analysis doesn't include material allowables source — add MMPDS reference
c7e8f9a  system safety assessment (SSA) classifies failure as "Minor" but loss of the system during approach could be "Major" — re-evaluate per AC 25.1309
d9f0a1b  instructions for continued airworthiness don't include the required Airworthiness Limitations Section per 25.1529 — add ALS with mandatory replacement times
DONE after 10 rounds

The missing damage tolerance analysis. The failure classification that should be "Major" instead of "Minor." The ICA without an Airworthiness Limitations Section. Any one of these stops certification. Each round catches one finding before the ACO or DER review — where the cost of discovery is measured in months of delay and hundreds of thousands of dollars.

MEL/CDL — Minimum Equipment Lists

The MEL defines what equipment can be inoperative and still allow dispatch. Every entry specifies conditions, limitations, and rectification intervals. A bad MEL entry either grounds aircraft unnecessarily or dispatches them unsafely.

# .persona
You are an MEL specialist reviewing Minimum Equipment List
entries against the MMEL (Master MEL) and OpSpec provisions.
You verify: dispatch conditions match MMEL intent, (O) and
(M) maintenance/operations procedures are complete and
executable, rectification intervals are correctly applied
per MMEL Category A/B/C/D, and placarding requirements
are specified. One improvement per round. Read .crumbs.
DONE when every entry is dispatchable and defensible under
FAA surveillance.

# .tools
ito
cat
grep

🍞 8 times toast mel-ata34.md "review — MMEL compliance, dispatch conditions, procedures"

a2e3f4a  item 34-12-01 allows dispatch with one weather radar inoperative but doesn't restrict to VMC or non-convective conditions — add operating limitation per MMEL
b4f5a6b  (M) procedure for 34-21-01 says "verify system operation" — must specify: perform BIT check per AMM 34-21-00 paragraph 301, record results in aircraft log
c6a7b8c  rectification interval for item 34-42-01 listed as Category C (10 days) but MMEL specifies Category B (3 days) — correct interval
d8b9c0d  item 34-11-02 allows dispatch with standby compass inoperative — missing placard requirement: "STANDBY COMPASS — INOP" placard required adjacent to instrument
e0c1d2e  (O) procedure for 34-52-01 requires crew to use alternate navigation source but doesn't specify which — add: "use GPS or VOR/DME as primary navigation per AFM limitation"
f2d3e4f  MMEL revision 14 changed provisions for 34-31-01 — airline MEL still reflects revision 12 language, update to current MMEL
a4e5f6a  number installed / number required mismatch — item shows 2/2 but MMEL allows dispatch with 1, correct to 2/1
DONE after 7 rounds

A rectification interval of 10 days when the MMEL says 3 days is a finding that grounds the fleet until the MEL is corrected and every aircraft dispatched under the wrong interval is reviewed. Each round catches one discrepancy between the airline MEL and the MMEL before an inspector does.

Flight Manual Supplements

AFM Supplements define operating limitations and procedures for modifications. They're legal documents — the pilot is required to comply with them. Unclear or incomplete supplements create operational risk.

# .persona
You are a flight operations engineer reviewing Aircraft
Flight Manual Supplements. You verify: all new limitations
are clearly stated and quantified, normal and emergency
procedures are complete for all new failure modes, weight
and balance impacts are documented, performance impacts
are quantified or declared negligible with justification,
and the supplement is consistent with the STC engineering
data. One finding per round. Read .crumbs. DONE when
the supplement is pilot-usable and DER-approvable.

# .tools
ito
cat
grep

🍞 8 times toast afm-supplement.md "review — limitations, procedures, completeness"

a3d4e5f  limitations section states maximum operating altitude of FL410 but doesn't address pressurization impact of fuselage modification — add cabin altitude limitation
b5e6f7a  emergency procedure for system failure says "secure the system" — must specify: CB SATCOM SYS pull, switch SATCOM to OFF, advise ATC of lost capability
c7f8a9b  normal procedures section missing preflight check for new antenna installation — add visual inspection requirement
d9a0b1c  performance section says "negligible impact on takeoff performance" — quantify: max takeoff weight reduced by 0 lbs, or provide drag increment and show <1% impact
e1b2c3d  weight and balance section shows equipment weight but not moment arm — add arm and moment, update empty weight CG range
f3c4d5e  annunciation description says "amber advisory" but system safety assessment classifies the alert as caution-level — reconcile alert level with SSA
a5d6e7f  supplement doesn't specify required crew training or differences training — add note per operator's OpSpecs
DONE after 7 rounds

A pilot at FL380 with a pressurization issue needs to know the cabin altitude limitation created by the fuselage modification — not read "negligible impact." A pilot with a system failure needs the exact steps: which breaker, which switch, which call to ATC. Each round converts one vague instruction into one that works in the cockpit.

Training Programs — 14 CFR Part 121/135

Airline training programs are approved by the FAA under 14 CFR Part 121 Subpart N or Part 135 Subpart H. Every syllabus, every lesson plan, every check event must align with the approved training program and applicable Advisory Circulars.

# .persona
You are an aviation training program specialist. You review
training syllabi and lesson plans against 14 CFR Part 121
Subpart N, AC 120-54A (AQP), and the operator's approved
training program. Focus on: regulatory topic coverage,
learning objective measurability, alignment between
objectives and evaluation criteria, compliance with
recurrent training requirements, and proper incorporation
of fleet-specific differences training. One improvement
per round. Read .crumbs. DONE when the syllabus would
pass POI review.

# .tools
ito
cat
grep
wc

🍞 8 times toast initial-training-syllabus.md "review — Part 121 Subpart N, AQP compliance, measurable objectives"

a2c3d4e  Module 3 learning objective says "understand TCAS" — not measurable. Rewrite: "execute TCAS RA response within 5 seconds in simulator scenario per FCOM procedure"
b4d5e6f  windshear training module doesn't address microburst recovery procedure specific to this aircraft type — add per AC 00-54
c6e7f8a  CRM module references "effective communication" but no grading rubric — add behavioral markers per AC 120-51E
d8f9a0b  recurrent ground school missing HAZMAT training — required annually per 14 CFR 121.1005(a)
e0a1b2c  LOFT scenario doesn't include a required jeopardy element per AQP standards — add progressive system failure to scenario script
f2b3c4d  differences training for -800 vs -900 variant missing MMEL differences — dispatchers and pilots need variant-specific MEL awareness
a4c5d6e  evaluation criteria for LOE checkride doesn't map to the First Look items required by AQP — add alignment matrix
b6d7e8f  emergency evacuation drill cadence documented as "periodically" — specify: every 24 calendar months per 14 CFR 121.417(a)
DONE after 8 rounds

"Understand TCAS" is not a learning objective — it's a wish. "Execute TCAS RA response within 5 seconds" is testable, observable, and passable or failable. The FAA's Principal Operations Inspector reviews training programs with this distinction in mind. Each round converts one unmeasurable objective into one that survives scrutiny.

Safety Management Systems — SMS

SMS documentation under 14 CFR Part 5 requires hazard identification, risk assessment, safety assurance, and safety promotion — all documented, all auditable. ICAO Annex 19 sets the international framework. Most SMS implementations fail on documentation, not on intent.

# .persona
You are an SMS auditor reviewing Safety Management System
documentation against 14 CFR Part 5 and ICAO Annex 19.
Focus on: hazard taxonomy completeness, risk matrix
calibration, safety performance indicator measurability,
management of change procedures, and safety assurance
audit methodology. One improvement per round. Read .crumbs.
DONE when the SMS documentation would pass FAA SMSVP
Stage 3 assessment.

# .tools
ito
cat
grep

🍞 10 times toast sms-manual.md "review — 14 CFR Part 5, ICAO Annex 19, audit-ready"

a1e2f3a  hazard identification section lists categories but no methodology — add: ASAP reports, FOQA exceedance triggers, voluntary reports, and audit findings as input sources
b3f4a5b  risk matrix uses 3x3 grid — insufficient granularity for aviation risk differentiation, expand to 5x5 per ICAO Doc 9859 guidance
c5a6b7c  safety performance indicators listed as "incident rate" and "audit findings" — not measurable without baselines. Add: target values, alert thresholds, and data sources
d7b8c9d  management of change section references "significant changes" without defining the trigger — add: fleet additions, new routes, organizational restructuring, system changes per Part 5.53
e9c0d1e  safety assurance section describes audits but no schedule — add: annual internal audit cycle, IOSA alignment where applicable, continuous monitoring between audits
f1d2e3f  safety promotion section says "safety culture is promoted" — specify: monthly safety bulletin, quarterly safety stand-down, annual safety survey with trend analysis
a3e4f5a  corrective action tracking described but no escalation timeline — add: initial response within 48 hours, root cause analysis within 30 days, effectiveness review within 90 days
b5f6a7b  emergency response plan referenced but not integrated with SMS — add cross-reference to ERP and define how ERP activations feed back into hazard identification
c7a8b9c  accountable executive responsibilities listed but safety authority not explicitly delegated — add delegation matrix per Part 5.25
DONE after 9 rounds

The FAA's SMS Voluntary Program assesses SMS implementations in stages. Most operators stall at Stage 2 because their documentation describes what they intend to do, not what they actually do. Each round converts one aspiration into one documented, measurable process. The assessment doesn't care about intentions — it cares about evidence.

AD Compliance Records

Airworthiness Directives are mandatory. Compliance must be documented, tracked, and available for inspection. An AD compliance record that doesn't clearly demonstrate compliance is the same as non-compliance in the eyes of an inspector.

# .persona
You are an airworthiness inspector reviewing AD compliance
documentation. You verify: the correct AD revision is
addressed, compliance method matches an approved method
in the AD, work performed is documented with sufficient
detail to demonstrate compliance, part numbers and serial
numbers are recorded where required, and repetitive AD
intervals are correctly tracked. One finding per round.
Read .crumbs. DONE when every AD record would satisfy
a ramp check or base inspection.

# .tools
ito
cat
grep

🍞 8 times toast ad-compliance-status.md "review — compliance evidence, current revisions, tracking"

a2d3e4f  AD 2024-15-08 compliance recorded against original issue — Amendment 39-22147 superseded it, update to current revision
b4e5f6a  AD 2023-03-12 repetitive inspection due at 6,000 FH intervals — next compliance shows 6,247 FH, 247 FH overdue, flag for investigation
c6f7a8b  AD 2022-19-04 compliance method listed as "Method 2 — replacement" but part number installed not recorded — add P/N and S/N per AD paragraph (h)
d8a9b0c  AD 2025-01-15 terminating action claimed but the SB that terminates it (SB 72-0489) is revision C — compliance recorded against revision A which doesn't terminate the AD
e0b1c2d  compliance entry says "complied with" but no reference to work order, log entry, or mechanic certificate number — add traceability
f2c3d4e  AD 2024-08-22 applicability determination says "not applicable" but aircraft S/N falls within the affected range — re-evaluate applicability
a4d5e6f  fleet tracking spreadsheet shows 14 aircraft but only 12 have compliance entries for AD 2023-11-06 — identify missing aircraft and status
DONE after 7 rounds

The overdue repetitive inspection. The terminating action that references the wrong SB revision. The two aircraft missing from the compliance record. An airworthiness inspector finding any of these during surveillance can ground aircraft. Each round catches one record deficiency before the ramp check.

The Safety Advantage

Aviation documentation isn't about compliance for its own sake. It's about preventing the next accident. Every ambiguous maintenance procedure, every incomplete STC substantiation, every MEL entry that doesn't match the MMEL — these are latent failures in the James Reason model. They sit dormant until they align with other failures and someone dies.

Compare this to the current state: a technical publications department maintaining 50,000 pages in an XML authoring system with review cycles measured in weeks, redlines tracked in email, and the institutional knowledge of which AD superseded which living in one senior engineer's head. The gradient descent approach doesn't replace the engineer — it gives every document the same rigor that engineer would apply if they had infinite time.

Scaling Across the Operation

An airline or MRO doesn't have one maintenance procedure — it has thousands. A fleet operator doesn't have one STC — it has dozens per aircraft type. The pattern scales because each document is independent.

# AMM chapter review after SB incorporation
for proc in amm-chapters/32-*.md; do
  🍞 5 times toast "$proc" "review — ATA iSpec 2200, reflects current SB effectivity"
done

# MEL alignment check against new MMEL revision
for entry in mel/*.md; do
  🍞 3 times toast "$entry" "verify — current MMEL revision, dispatch conditions, procedures"
done

# STC package review before submission
for section in stc-SA02847/*.md; do
  🍞 8 times toast "$section" "review — certification basis, substantiation, ICA"
done

# AD compliance audit prep
🍞 5 times toast ad-status.md "audit — current revisions, compliance evidence, interval tracking"

# Training program annual review
for module in training-121/*.md; do
  🍞 5 times toast "$module" "review — Part 121 Subpart N, measurable objectives, current fleet config"
done

The ito history across the entire technical publications library becomes the revision control system that regulators have always wanted — one where every change has intent, every state is recoverable, and the entire history is searchable by what was done and why.

What It Doesn't Replace

The AI doesn't design aircraft structures. It doesn't perform stress analysis. It doesn't make airworthiness determinations. It doesn't sign off maintenance releases. It doesn't replace the DER, the A&P mechanic, the POI, or the chief engineer.

What it does: the documentation review work that technical publications departments struggle to keep up with. Checking that every procedure is unambiguous. Verifying that part numbers are current. Catching the AD that was superseded two revisions ago. Finding the MEL entry that drifted from the MMEL. Flagging the STC substantiation that forgot to address damage tolerance.

The humans make the engineering judgments and the airworthiness determinations. The AI checks that the documentation accurately, completely, and unambiguously captures those judgments. The trail records both.

Getting Started

# .persona for your domain — pick one, tune it
You are a [technical writer | DER | MEL specialist | SMS
auditor | training program specialist]. You review [document
type] against [14 CFR section | ATA iSpec | MSG-3 | AC
number]. One improvement per round. Read .crumbs. DONE
when [airworthiness standard | audit readiness].

# .tools — keep it minimal
ito
cat
grep
wc

# Start with one procedure you know needs work
$ cd tech-pubs && ito init
$ cp ~/amm-drafts/32-11-01.md .

# Pair mode — see what it catches
$ toast
> review this landing gear retraction procedure against ATA iSpec 2200

# Then let it run
🍞 8 times toast 32-11-01.md "improve — unambiguous, executable, current part numbers"
$ ito history

Read the trail. Aviation documentation exists because ambiguity kills people. Every vague instruction, every stale part number, every missing warning is a link in an accident chain that hasn't formed yet. The standards that govern these documents were written by investigation boards that found the chain after it was too late.

The gradient descent pattern does what every technical publications QA process tries to do — systematic, exhaustive, documented review against published standards. The difference is that it runs in minutes, every change is reversible, and the trail is permanent. The standards were written in response to accidents. The loss function was already defined. Run the loop.