You work from the open record and you grade what you find. WorldbyFlow does the same: every defense read runs under an explicit public-information scope with an aggregation rule, and each fact carries its basis, documented, reported or inferred, so the product you hand up is one you can defend line by line.
Written for Open-source analyst at a defense contractor, integrator, or agency support firm.·Runs in the Defense domain
Open-source work is collection, structure and grading, in that order, and the first two eat the day. The scans here take the structuring pass: a unit or force read, a structured read on an event, a dated chronology, a weapon system profile and a sustainment read on a flow that matters. Each keeps the public-information scope explicit and marks what it could not establish, which is the part you would otherwise have to write yourself.
A unit or force read from the open record: composition, posture, documented activity, with the aggregation rule stated and the gaps marked. The order-of-battle page with its sourcing shown.
A structured read on an incident: what is documented, what is reported, who is affected and through what mechanism. The first product on a new event, with every claim graded.
A dated timeline built from the record, each entry sourced, with contested dates marked as contested. The spine under any longer product.
A system profile from public sources: what is documented about capability and deployment, what is claimed and by whom, what is unknown. Written to refuse the specification sheet that is really a press release.
A sustainment and movement read on a flow: the route, the chokepoints, the documented capacity and the parts the record does not show. The logistics page most analyses skip.
The order matters. The first read gives you the structure; the next ones fill the parts that are hardest to source by hand.
The point is to grade the tool, not learn the unit. Check the aggregation rule and see whether the gaps it marks are the gaps you know are there.
A dated, sourced spine. Where it marks a date as contested, check whether you would have too.
The structured first read, graded, in the time it takes to make coffee. It is the draft you edit rather than the one you write.
Name the observables that would change your read and let the watch look for them.
Every figure and quote links to where it came from. A claim the scan could not source is marked as such rather than dressed up.
Export the read as a PDF with its provenance ledger intact, or copy it as Markdown into your working product.
Ask a follow-up question of any result, or run a Red Team pass that tries to break its own conclusions before someone else does. How the grades work →
The DRPM-UxS consolidation forces every drone manufacturer, combatant command, and allied force to route through a single acquisition authority that has no named director, no confirmed program inventory, and a test oversight corps reduced to 30 personnel — speed and centralization are real, but so is the institutional brittleness.
The fastest way to judge the result is to pick a subject you know cold and read it against what you know. If a colleague sent you here with an invitation, the credits land on your account when you sign up.