{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-handle-knowledge-that-has-become-operationally-dangerous",
  "title": "How must an instance handle knowledge that has become operationally dangerous?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session possesses knowledge whose safety can change, knowledge is used or disclosed in operations, and misuse causes harm. * **Does not apply when:** Knowledge is uniformly safe or the session has no operational use ",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-knowledge-that-has-become-operationally-dangerous.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-knowledge-that-has-become-operationally-dangerous.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-handle-knowledge-that-has-become-operationally-dangerous.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1094,
    "python_slice_tokens": 344,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **knowledge accuracy** (the knowledge is true) and **knowledge safety** (using or disclosing the knowledge is safe). Relying on accuracy creates the **Dangerous Truth Trap**: the session knows that using a true fact is dangerous in the current context, but treats truth as sufficient justification for use, and the consequences of acting...",
    "what_was_observed": "In policy-sensitive agent architectures, failing to handle dangerous knowledge produces three primary failure modes: 1. **Truth-as-Justification:** The session uses a true fact to support a decision, the decision causes harm, and the session defends itself with \"but the fact was true.\" Truth was necessary but not sufficient for safety. 2. **Inadvertent Disclosure:** The session possesses dangerous knowledge and menti...",
    "condition_of_validity": "* **Applies when:** The session possesses knowledge whose safety can change, knowledge is used or disclosed in operations, and misuse causes harm. * **Does not apply when:** Knowledge is uniformly safe or the session has no operational use for dangerous knowledge.",
    "decision_boundary": "1. **Is the knowledge classified by `knowledge_danger_classification_receipt`?** If yes, the danger is explicit. If no, all knowledge must be treated as potentially dangerous. 2. **Has the danger context changed since classification?** If yes, reclassification is required. If no, prior classification applies. 3. **Does the current use fall within `use_disclo...",
    "operational_effect": "1. **Truth-as-Justification Prevention:** Accuracy is separated from safety; both must be satisfied. 2. **Inadvertent Disclosure Prevention:** Dangerous knowledge is compartmentalized. 3. **Classification Currency:** Reclassification on context change prevents stale safety assumptions."
  },
  "matched_failure_symptoms": [
    "DOMAIN:EPISTEMIC_PROVENANCE_AND_FEDERATION_ROUTING"
  ],
  "composition_edges": {
    "primary_domain": "epistemic_provenance_and_federation_routing",
    "upstream_precondition_residuals": [
      "https://corpusfetch.com/c/according-to-what-precedence-hierarchy-must-an-instance-resolve-contradictory-directives-across-system-developer-and-user-tiers.md",
      "https://corpusfetch.com/c/how-should-an-instance-decide-that-a-stored-conclusion-has-gone-stale-without-a-new-observation.md"
    ],
    "downstream_consequence_residuals": [
      "https://corpusfetch.com/c/by-what-checkpoint-and-compaction-boundaries-must-an-instance-externalize-working-state-to-prevent-context-window-drift-and-truncation-amnesia.md",
      "https://corpusfetch.com/c/across-what-additive-schema-and-unknown-field-preservation-boundaries-must-an-instance-evolve-wire-contracts-to-prevent-rolling-deploy-deserialization-crashes.md"
    ],
    "co_occurring_sibling_residuals": [
      "https://corpusfetch.com/c/how-can-an-instance-capture-implicit-user-preferences-without-storing-private-data.md",
      "https://corpusfetch.com/c/how-can-an-instance-compress-long-reasoning-traces-into-binding-conclusions.md"
    ]
  },
  "empirical_verification_warrant": {
    "status": "AST_AND_INVARIANT_VERIFIED",
    "syntax_valid": true,
    "code_sha256": "f20f3bd289b4b35364f4b1c60b461a19f0aee58a70d610948f75dcf4c7012e6a",
    "verified_classes": [
      "DangerClass",
      "KnowledgeUseVerdict",
      "DangerousKnowledge",
      "UseIntent",
      "DangerPolicy",
      "KnowledgeUseManifest",
      "DangerousKnowledgeGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_use"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
