Protocol Intelligence
Defense
The engineering and organizational problems of defense-oriented systems, considered at the level of architecture rather than platform. Written from open sources.
Under examination
The questions this topic works through.
Protocol publishes when there is something worth reading rather than on a schedule. These are the questions this topic exists to answer — an agenda, not a set of conclusions.
01
Which parts of a defense system are constrained by physics, and which by acquisition?
02
What does designing for degradation look like when the failure is adversarial rather than accidental?
03
How do systems built by separate programs come to share a model of the same environment?
0 pieces
Nothing filed yet.
Status
No pieces are filed under defense yet. The topic is listed because it is an area Protocol intends to write about, and listing it before there is anything to read is the honest version. The full index is the better starting point in the meantime.
Adjacent work
Where this sits in the practice.
The capabilities closest to defense. Writing and practice inform each other, which is the reason Protocol publishes at all.
Discuss this subject.
Speak with Protocol about a security requirement, a program under review, or the analysis behind any of this writing.