Skip to content

What Hermes Does Not Know — Epistemic Limits & Analytical Boundaries

Density:
┌─────────────────────────────────────────────────────────────────────────────────┐
│ HERMES CODEX EPISTEMIC INTEGRITY CONTRACT (SECTION 83) │
│ │
│ "To state what is known without stating what is ignored is not analysis; │
│ it is marketing. Hermes formalizes the frontier of its own ignorance." │
└─────────────────────────────────────────────────────────────────────────────────┘

1. The Six Dimensions of Analytical Uncertainty

Section titled “1. The Six Dimensions of Analytical Uncertainty”

Under Section 83 of the Hermes Master Specification, analytical uncertainty is decomposed into six immutable, mutually exclusive dimensions:

D1 Missing Data (Données Manquantes)

Information that exists objectively in the physical world or private telemetry but has not been published or verified in accessible authoritative registries.

D2 Unavailable Sources (Sources Indisponibles)

Authoritative feeds locked behind proprietary NDA licensing, classified state sensors, or paywalled private EDR telemetry networks.

D3 Working Hypotheses (Hypothèses)

Default baseline postulates adopted to enable deterministic risk calculation prior to empirical ground confirmation.

D4 Structural Uncertainties (Incertitudes)

Intrinsic statistical dispersion, machine learning inference intervals (EPSS), and temporal ingestion lags (24–72 hours).

D5 Model Limitations (Limites des Modèles)

Mathematical and algorithmic boundaries inherent to AST parsing, non-SemVer normalization heuristics, and static pillar weightings.

D6 Unobservable Dimensions (Non Observables)

Physical and cryptographic realities inaccessible from the exterior (internal network micro-segmentation, private air-gaps, actor psychological intentions).


What Constitutes Missing Data in Threat Intelligence?

Section titled “What Constitutes Missing Data in Threat Intelligence?”
  • NVD Ingestion Latency & Backlog: Due to national triage backlogs, weeks can elapse between public zero-day exploitation and official CVSS vector assignment.
  • Closed Firmware & Proprietary Diffs: Closed-source enterprise gateways (Ivanti, Palo Alto, Fortinet, Cisco) rarely disclose exact git commit SHAs, line-level diffs, or vulnerable AST sinks.
  • Unbounded Early Version Ranges: Vendor advisories frequently publish ambiguous statements such as “all versions prior to 24.2.1”, concealing whether legacy architectural branches are vulnerable or structurally immune.

Hermes flags the dossier with epistemic_state: "INSUFFICIENT_DATA". Rather than guessing an arbitrary score, Hermes bounds the affected range conservatively and reduces the confidence metric (C) with a distance penalty (P_dist = -0.10 per missing variable).


3. Operational Rule: When is an Assessment “Uncomputable”?

Section titled “3. Operational Rule: When is an Assessment “Uncomputable”?”

Hermes firmly rejects “fake precision.” If critical evidentiary predicates are missing, the Decision Engine refuses to fabricate a score and marks the entry as UNCOMPUTABLE:

┌──────────────────────────────────────────────┐
│ Vulnerability Ingestion Event │
└──────────────────────┬───────────────────────┘
│
Are affected versions bounded?
├── NO ──► [EPISTEMIC_STATE: INSUFFICIENT_DATA]
│ HTS: UNCOMPUTABLE
YES Action: Quarantine Analysis
│
Is root vulnerability locus verified?
├── NO ──► Apply Penalty (C ≤ 0.45)
│ Review Date: +24h
YES
│
Are primary sources in conflict?
├── YES ─► [EPISTEMIC_STATE: CONFLICTING]
│ Document Dispute & Side with Lab
NO
│
▼
[EPISTEMIC_STATE: KNOWN]
Confidence Score: 0.85 – 1.00
Publish Automated Advisory
  1. Unbounded Version Specifier: If an advisory specifies no version bounds (e.g., version: "*" without CPE vendor confirmation), HTS calculation is suspended.
  2. Conflicting Vector Discrepancy > 4.0 Points: If primary vendor advisory asserts CVSS 4.0 (Local DoS) while community telemetry observes remote arbitrary code execution (CVSS 9.8), the item is flagged as CONFLICTING and escalated for laboratory verification.
  3. Zero Corroborated Telemetry with Expired PoC: If an unverified social media claim asserts zero-day exploitation without code, packet capture, or sensor hits within 14 days, it is purged as unverified noise.

4. Live Demonstration: Epistemic Limits UI Integration

Section titled “4. Live Demonstration: Epistemic Limits UI Integration”

Every single observation and threat dossier on Hermes Codex embeds the Hermes Unknown Box to ensure readers instantly perceive analytical boundaries:

WHAT HERMES DOES NOT KNOW (SAMPLE DOSSIER OBS-2026-000273) Principle P3 — Epistemic Rigor
  • ✕ Local network segmentation: whether the target organization isolates the management API behind an out-of-band VPN.
  • ✕ Vendor patch availability date: the vendor has not released a maintenance release timestamp for legacy branch 2.4.x.
  • ✕ Active weaponization against air-gapped instances: telemetry is derived solely from internet-exposed sensor arrays.

Every artifact within the Hermes intelligence repository tracks its lifecycle through four formal states:

Epistemic StateMathematical DefinitionConfidence Metric ($C$)Publishing Behavior
KNOWNPrimary telemetry verified; $\ge 2$ corroborating feeds; version bounds deterministic.$0.75 \le C \le 1.00$Automated real-time publication.
CONFLICTINGIncompatible claims between vendor advisory and field telemetry.$0.40 \le C \le 0.74$Prominent dispute callout box displayed.
INSUFFICIENT_DATAEssential analytical variables missing (e.g., unbounded affected versions).$C < 0.40$Score marked UNCOMPUTABLE; quarantine alert.
UNKNOWNTheoretical vector identified but completely unobservable in current telemetry.N/ADocumented exclusively under What Hermes Does Not Know.