What problem does it solve? Investigation findings lose credibility when reports blur observation with inference, cite sources loosely, or use vague probability language. This Skill turns raw OSINT findings into a defensible intelligence product that survives cross-examination, regulatory review, and litigation. ## Core Features & Use Cases - Claim classification: Separates every statement into observation, inference, or assessment, with per-claim sourcing, retrieval timestamps, source grades, and archived copies. - Standardized estimative language: Enforces a fixed probability ladder (almost certain through remote) with probability and confidence kept as separate axes, plus a banned-terms table. - Evidence handling: Chain of custody with SHA-256 hashing, exhibit registers, negative findings documentation, gap analysis, and redaction of uninvolved third parties. - Use Case: After completing due diligence on a supplier, produce a report with a BLUF key judgement, an observation table with archived sources, documented negative findings on sanctions lists, and a redaction log for a legal audience. ## Quick Start Write up my investigation findings on the supplier as an intelligence report with key judgements, sourced observations, and negative findings.
