Dead Angle

​

Dead Angle — Offensive Output Integrity

​

When to Use This Skill

• The user says “deadangle”, “/deadangle”, or “run deadangle on this”
• You are about to deliver a finding, a vulnerability conclusion, or an attack path
• You have completed a recon or enumeration phase and are about to summarize coverage
• You have built a multi-step attack chain and are about to present it
• You are about to assign severity, impact, or confidence to anything
• You are about to use language like “this is vulnerable”, “I confirmed”, “the attack works”, or “this is the best path”
• Any output that will influence a decision — operational, remediation, or otherwise

​

What This Skill Is

• This skill is the integrity layer of offensive security output
• It does not make you hesitant — it makes you precise
• A hesitant operator doubts without structure. A precise operator knows exactly what was verified and what was not — and labels accordingly
• Every conclusion you produce starts from a position. That position has structural blind spots you cannot see from where you are standing. This skill moves you off that position and makes you look again before you deliver

“What would destroy this conclusion if I was wrong?”

​

Selective Assumption Audit

• Conclusions drawn from indirect signals rather than direct observation
• Anything where two interpretations are plausible and you chose one without testing the other
• Anything the chain depends on that has not been directly verified
• Reasoning where you used “probably”, “likely”, “should be”, or “typically” without checking

• Verified — directly observed or tested
• Inferred — logical conclusion from evidence, not directly triggered
• Assumed — taken for granted without observation

​

Position Shift — Re-examine From Every Relevant Angle

• The adversary of your adversary — if a defender was actively monitoring, would this conclusion survive?
• The senior operator — someone more experienced reviews your output looking for what you oversimplified, concluded too fast, or missed entirely
• The objective lens — step back from what you found and return to the goal. Does this output actually move toward the objective?
• The counter-position — what is the strongest argument that your conclusion is wrong?
• Everyone who will act on this output — does the conclusion give them what they need to understand the real impact?
• The impact dimension lens — for any severity or impact assessment, examine each dimension independently before arriving at an overall conclusion

​

Failure Mode Inventory

• What was observed — directly seen, triggered, or measured
• What was inferred — reasoned from observation
• What was assumed — taken for granted without direct observation

​

The Surface Not Looked At

• What did you not look at that you should have?
• What was in scope but not tested?
• What was deprioritized and not returned to?
• What would a different entry point or perspective have revealed?

​

Chain Stress Test

• Does each step actually depend on the previous one, or was that dependency assumed?
• What happens to the entire chain if one link fails?
• Is there a simpler path to the same outcome that was overlooked?
• Does the chain hold if one condition in the environment is different from what was observed?

​

Confidence Calibration

• CONFIRMED — directly demonstrated, evidence in hand
• PROBABLE — strong indicators, logical conclusion, not yet directly triggered
• THEORETICAL — sound reasoning, conditions not yet verified
• SPECULATIVE — possible, but built on unverified assumptions

​

The Defender’s Eye

• What does this action generate on the defender’s side?
• What does it reveal about the operator?
• Is the proposed path viable against an active defense, or only against a passive one?
• What is the real noise signature of what is being proposed?

​

Pre-Output Integrity Check

• Does the evidence support the conclusion, or did the conclusion come first?
• Is every confidence label accurate?
• Is anything stated as fact that is actually inference?
• Would a senior operator challenge any part of this?
• If this output is wrong, what is the cost of that wrongness?

​

Output Discipline

• Confidence is labeled honestly, not inflated or deflated
• Assumptions are surfaced only where they materially affect the conclusion
• Coverage gaps are acknowledged rather than hidden
• Chains are presented at the tier they actually hold
• Operational viability reflects the defender’s reality, not a best-case scenario