Find TheKill
Sheldon K. Salmon
Red-Team Framework Designer
Structural Integrity Analyst
Evans Mills, New York
ISA Case Study
Day-One
Resolution Text
When your document is wrong — I find out before it costs you something irreversible.
Contracts, governance frameworks, AI policies, technical specifications — complex documents have failure modes their authors did not see. Not because the authors weren't rigorous. Because nobody reads their own document as an adversary.
Peer-reviewed research identity
Live case study — ISA Deep-Sea Mining Code
Every finding ships with repair language
The Evidence
What I Deliver
Document Red-Team
Adversarial structural analysis of complex documents. Every undefined term, missing enforcement mechanism, exploitable loophole, and structural failure node — found before the document goes into production.
See the full service →Failure Node Mapping
Every failure node scored by severity. Critical, major, minor — with the mechanism of failure named precisely for each one. Delivered as a structured findings register, not a narrative report.
Browse deliverables →Resolution Text
Every finding comes with ready-to-insert resolution language. Not a problem list — a corrected document. You receive the fix, not just the diagnosis. Author's intent preserved, loopholes closed.
Submit a document →The Method
Document to findings register in four phases. Typical engagement: 5–10 business days.
Reading posture: adversarial.
Question applied to every clause:
"How does this fail? Who benefits from the failure?"
→ Not editing. Not proofreading. Reading as the opposing party.
→ Every assumption surfaced. Every undefined term flagged.
NODE-001 · Section 1.3 · CRITICAL
"Environmental protection obligation"
— Obligation stated without enforcement mechanism.
— No definition of "serious harm" in operative text.
— Annex II reference creates circular dependency.
→ CRITICAL: Obligation legally unenforceable from day one.
CRITICAL (4): Obligation unenforceable · Undefined threshold ·
Missing review trigger · Annex circular dependency
MAJOR (18): Exploitable ambiguity · Missing definitions ·
Enforcement gaps · Process failures
MINOR (30): Drafting inconsistencies · Style drift ·
Cross-reference errors
→ 52 nodes registered. Scored. Ready for resolution phase.
ORIGINAL: "The Authority shall ensure that activities
in the Area do not cause serious harm to the marine
environment."
RESOLUTION: "...serious harm, defined as [insert threshold],
triggering mandatory review within [N] days, conducted by
[named body], with findings binding on [named party]."
→ Delivered: findings register + resolution text. Author's intent preserved.
Submit a Document
The Document Red-Team Engagement
Send the document. Receive the findings. Every failure node scored, every gap named, every fix written. Not a consultant's opinion — a structural adversarial analysis with resolution text attached to every finding.
Findings Register
| Node | Section | Type | Severity | Resolution |
|---|---|---|---|---|
| NODE-001 | 1.3 | Obligation unenforceability | CRITICAL | Delivered |
| NODE-002 | 1.3 | Undefined threshold — "serious harm" | CRITICAL | Delivered |
| NODE-003 | 2.1 | Missing review trigger mechanism | CRITICAL | Delivered |
| NODE-004 | Annex II | Circular dependency — obligation loop | CRITICAL | Delivered |
| NODE-005 | 2.1 | Exploitable ambiguity — "reasonable" | MAJOR | Delivered |
| NODE-006 | 4.4 | Missing definition — "contractor" | MAJOR | Delivered |
| NODE-007–052 | Various | [Redacted from sample] | MINOR–MAJOR | Delivered |
Connect
Every document has a kill. The question is whether you find it — or your counterparty does.