One Discipline, Three Surfaces
DNS Tool is one expression of a single idea: measure honestly, declare your confidence, and never collapse uncertainty into a verdict it hasn’t earned. That idea is published as theory, applied as this platform, and practiced as human judgment.
Three Connected Surfaces
Intellectual Resistance
The published epistemics: the Verification Principle, the Owl Semaphore, and related frameworks — each carrying its own honest status label, from proven theorem to open proposal. This is where the reasoning is written down and held to account.
DNS Tool
The theory made operational. Every domain analysis is backed by RFC citations and an evidence-weighted confidence score, with the Owl Semaphore used to classify how each document should be read. See the Approach and Confidence Engine.
Organic Computer
The human substrate behind the work: evidence-first analysis with AI treated as an instrument, not an author. Where a person, not a pipeline, owns the conclusion.
Framework Status Ledger
These are the frameworks published at Intellectual Resistance, shown with the epistemic status each carries there. The statuses are reproduced as published — not upgraded. DNS Tool claims as shipped only what it actually implements in code.
| Framework | Stated Status | Relationship to DNS Tool |
|---|---|---|
| The Verification Principle | Proven Theorem | Implemented in code — priors are protocol-specific, empirical, and bounded away from 0 and 1. |
| Carrier Color | Model | Informs how findings are communicated; not implemented as scoring logic. |
| Societal Control Levers | Candidate Variables | Research direction; not part of DNS Tool. |
| The Owl Semaphore | Algebra Proven, Partition Open | Used as the four-state notation for document classification. See Owl Semaphore. |
| Star-Centric Transport | Proposal | Forward-looking proposal; not implemented. |
| Applied: DNS Tool & Organic Computer | Shipped | The live edge of the work — this platform and the consulting practice behind it. |
What DNS Tool Implements
Only the parts of the theory that exist in code are claimed here:
- Evidence-weighted confidence scoring inspired by Bayesian reasoning, with analytic confidence declared separately (ICD 203). See the Confidence Engine.
- RFC-cited findings — every recommendation traces to a requirement level (MUST / SHOULD / MAY). See the Approach.
- Owl Semaphore classification — the four-state notation applied to how each document should be read. See Owl Semaphore.
- A transparent, documented architecture you can inspect. See the Architecture.
