# Squawk Sheet

> A hangar tech log for a paper plane. Write one line per test throw about what the plane did. A free
> in-browser engine reads each line as a squawk - dive, climb then stall, banks left, banks right,
> spiral, wobble, lands short, damage, a good flight or not clear - files it under an ATA 100
> maintenance chapter with its standard trim fix, draws the plane from above on a hangar floor with a
> numbered tag per squawk and the trim marked on its back edges, and sets a release status by a fixed
> rule: refold, trim then re-fly, test flight needed or cleared to fly. A metered run writes the
> engineer's entries. Derived from @personamanagmentlayer/aerospace-expert.

https://squawk-sheet.skillsafe.ai/

## What it does

- Throws: one a line (markers such as "1.", "Throw 2:" or "-" are dropped). One to eight throws; later lines are left out and counted.
- Reading: damage (torn, soggy, crushed), dive, climb then stall, spiral, banks left or right (as the pilot holds it, nose pointing away), wobble, lands short, or a good flight; the first one found is the line's primary.
- Chapters: 05 time limits and checks, 08 levelling and weighing, 27 flight controls, 53 fuselage, 55 stabilizers, 57 wings.
- Standard fixes: a dive gets both back edges bent up about 1 to 2 mm; a stall gets them flattened or one paper clip on the nose; a bank left gets the left back edge down or the right one up (and the mirror for a bank right); a spiral gets the wings matched; a wobble gets sharp creases and a slight upward V; landing short gets a level throw at the design's pace.
- The status, checked in this order: any damage is refold; else any flight fault is trim, then re-fly, starting with the first fix (dive, then stall, spiral, a bank either way, wobble, short; the earliest throw breaks a tie); else fewer than two good flights is test flight needed; else cleared to fly.
- Free downloads: the drawing (SVG, PNG), the squawks (CSV), and the tech log (plain text, Markdown, JSON).
- Saved logs (opt-in) keep the plane, the throws and the latest entries, and show how the status moved between runs.

## The paid task

One task, `squawk`, on gpt-terra, metered per run. The input is four string fields: `task`, `plane` (design, paper, place, tail mark and the pace the design likes), `reports` (one throw a line with what it reads as and its chapter) and `facts` (the page's decisions). The reply is one JSON object: verdict (refold | trim | test-fly | cleared, always the page's), entries (one per throw: n, chapter, defect, action, why), first_fix, next_test and sign_off. The page re-checks the reply: one entry per throw in order, the page's chapter, every trim bending the right edge the right way, the first fix naming the right squawk, numbers kept and none added, and a release line that matches the status.

A paper plane is a toy: throw it in a clear space, never towards people, animals or faces. Not professional advice.

- API tutorial: https://squawk-sheet.skillsafe.ai/api.html
- Source skill: https://skillsafe.ai/skill/@personamanagmentlayer/aerospace-expert (personamanagmentlayer/pcl)