Observe.Stream

AOS-JSON/1 STREAMS (docs/standards/AOS-1.0-draft-1.md §24.1, §10): a stream's verdict -- complete, incomplete or invalid -- and the reason. invalid a line that is not a valid record; a first record that is not a header; a record after the footer; a footer whose count is not the number of lines before it; an event whose sequence does not increase within its producer epoch incomplete bytes after the last LF (a torn write: AOS-REC-001's valid prefix with an incomplete tail); no footer (AOS-JSON-002); a footer that says incomplete; sequences missing beyond the drops the producer's coverage record declares (AOS-COV-004 .. 005) complete none of these: complete for what the stream declares, not a claim that every physical event was observed (AOS-COV-001) An incomplete stream is not an invalid one: its records remain individually valid evidence (AOS-OBS-004). Status and problem numbers are a contract with the bootstrap reader (tool/Aos.hs `StreamStatus`, `StreamProblem`); never renumber one. status 0 complete, 1 incomplete, 2 invalid problem 0 none, 1 empty, 2 invalid-line, 3 header-missing, 4 after-footer, 5 footer-count, 6 sequence-order, 7 no-footer, 8 footer-incomplete, 9 truncated-tail, 10 unaccounted-gap, 11 coverage-cumulative --------------------------------------------------------------------------- Lines

49field unrestricted aosVerdictUnknownRecords : Nat