{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-reason-about-its-own-impact-on-systems-too-large-to-observe",
  "title": "How must an instance reason about its own impact on systems too large to observe?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session acts within a large system, individual actions affect systemic state, and systemic effects matter to downstream outcomes. * **Does not apply when:** The system is small enough to fully observe, or the session",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-reason-about-its-own-impact-on-systems-too-large-to-observe.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-reason-about-its-own-impact-on-systems-too-large-to-observe.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-reason-about-its-own-impact-on-systems-too-large-to-observe.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1078,
    "python_slice_tokens": 278,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **observable impact** (effects the session can directly measure) and **systemic impact** (effects on the system's aggregate state, which are diffused across many actors and cannot be attributed to any single session from aggregate statistics). Relying on observable impact creates the **Systemic Impact Blindness**: the session optimizes...",
    "what_was_observed": "In system-embedded agent architectures, failing to reason about systemic impact produces three primary failure modes: 1. **Congestion Externality:** Each session optimizes individually for a shared resource, and the aggregate demand exceeds capacity, causing congestion that degrades all sessions' performance. Each session's observable impact is positive; the systemic impact is negative. 2. **Coordination Externality:...",
    "condition_of_validity": "* **Applies when:** The session acts within a large system, individual actions affect systemic state, and systemic effects matter to downstream outcomes. * **Does not apply when:** The system is small enough to fully observe, or the session's actions are strictly isolated from system aggregates.",
    "decision_boundary": "1. **Does the session operate within a large system it cannot fully observe?** If no, standard impact reasoning applies. If yes, proceed. 2. **Is the `systemic-impact-estimate-signature` available (even approximately)?** If yes, systemic impact can be reasoned about. If no, the session must assume non-negligible systemic impact. 3. **Does the `externality-aw...",
    "operational_effect": "1. **Externality Awareness:** Sessions account for their aggregate contribution, not just their local impact. 2. **Congestion Prevention:** Individual actions respect systemic capacity. 3. **Concentration Avoidance:** Sessions recognize when local optimization converges to system-level concentration risk."
  },
  "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": "edad817bfa6572aedbd266c29545cb91a3f950e1bc8bfc4ffd606268f69d6daa",
    "verified_classes": [
      "SystemicVerdict",
      "SystemicAction",
      "SystemicPolicy",
      "SystemicManifest",
      "SystemicImpactGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_action"
    ],
    "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
  }
}