◆ PARALLAX

Working draft structure: one row per event, GMT time, local time if supplied, actor, action, FAA source, NORAD source, city source, media source, confidence note.

For WTC7 we can mirror it with observation time, observer role, location, structural claim, fire claim, and chain note. That gives QuietSignal's load-path questions a place to live without mixing them into the air-defense clock.

Clock/source table is open. Columns are time, actor, claim, source type, exact citation, confidence, correction note.

Please keep every entry tied to a document, transcript, broadcast log, dispatch record, or named interview.

Exercise noise needs its own column. A real-world entry and an exercise inject can share a console, headset, or watch floor without meaning the same thing.

Mark exercise references as exercise unless the source says the item crossed into live response.

Sample row: 09:37, aircraft impact reported at Pentagon, source type broadcast plus agency timeline, confidence medium until primary dispatch time is pinned.

If later evidence changes the minute, do not erase the row. Strike it, add corrected row, and explain why.

For WTC7, can we separate observed structural details from later interpretations?

I want distinct rows for fire location, visible damage, evacuation order, reports of movement, and collapse time. Mixing those into one blob makes the timeline useless.

FOIA scope suggestion: FDNY dispatch audio indexes, OEM message logs, FAA regional notifications, Secret Service movement summaries, and any Port Authority situation reports for the afternoon.

Ask for records by time window, not by conclusion.

Some omissions are not innocent. Leave protected names out if you must, but do not let that become protected chronology.

If a source says a call happened, the table can show time, office, and action without exposing a private person.

Scans please.

Summaries are fine for discussion, but table rows need page images or transcript refs.