What the verification states mean
A checklist is a safety document. The most dangerous thing this project could do is let an unchecked machine transcription look like a checked one, so every file carries its state on two independent axes and neither implies the other.
Does it match its source?
unreviewed | Machine or first-pass output. Nobody has compared it to the source document. |
single_reviewed | One person, not the transcriber, compared it line by line against the source. |
dual_reviewed | Two people did so independently. |
not_applicable | There is no source document. The content is authored — common for Part 103, where no approved flight manual is required. |
Has it been used in an aircraft?
none | Never exercised against a real aircraft. |
ground_checked | Walked through in the actual cockpit, every control located. |
flown | Flown behind in this type. |
Why flying behind it is not the top state
Flying behind a checklist cannot detect a missing item. Nothing prompts you to do the check that was left out, so the flight feels entirely normal. That makes "flown" weaker evidence of correctness than "two people compared it against the source" — which is why operational review never lifts a file out of quarantine on its own.
Completeness
A file can be faithful to its source and still be missing whole sections. A
missing emergency procedure is invisible to the person holding the file, so
completeness is stated separately: full, normal_only,
partial, excerpt.
Quarantine
Files that are unreviewed, or that carry an unresolved safety defect, are quarantined. They are still downloadable — review requires people to be able to read them — but they are excluded from the default bundle, their filenames carry the state, and they are never offered in a panel-loadable avionics format, because a panel file has nowhere to put a warning label.
Rights
Rights are recorded per file, not repo-wide, because this project cannot grant a
licence in text it does not own. public_domain files state the basis
(most are US Government works under 17 U.S.C. 105). original_expression
means the wording is the contributor's own, expressing procedure taken as fact.
Files whose rights are unresolved are not published at all.
Found a problem?
File a report against the exact version you were looking at — every file has a content hash. A confirmed transcription error or stale item costs the file its verification badge automatically, which is how the corpus stays current instead of merely claiming to.