mi-collect-masintlisted

# MASINT Collection Sweep ## Purpose The satellite photo. Measure the physical and operational exhaust. Abnormal resource allocation never lies. A company reserving power capacity, selecting a notified body, changing supplier geographies, or letting support response times stretch is making a decision that costs money, and it is doing so in public records six to thirty-six months before anything gets announced. MASINT also has the discipline's defining weakness: **an anomaly never explains itself.** Input volumes up twenty percent is pre-launch buildup or demand collapse, and only another discipline tells you which. So this sweep carries a mandatory column naming, for every anomaly, the discipline that would resolve it. A MASINT signal without a disambiguation path is a Rorschach test, not intelligence. The sweep produces a labeled inventory, not a verdict. **Collection is not fusion.** ## When to Use It Use it when the question is capacity: are they building for something, or straining under something. Use it when a competitor's messaging is confident and you suspect their operations are not. Use it to estimate a private company's real scale when no filings exist. Do not use it when: - **The target is pure software with no physical footprint** and you expect supply-chain findings. The software equivalent is ops capacity plus infrastructure-scale language, and it is thinner. Say so before collecting rather than after. - **You need to know what they are building.** MAS