{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-persist-the-negative-space-of-what-it-chose-not-to-do",
  "title": "How must an instance persist the negative space of what it chose not to do?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The session had multiple viable alternatives, evaluating them was costly, and the rejection criteria are non-trivial to re-derive. * **Does not apply when:** There was only one viable action, or rejected alternatives are",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-persist-the-negative-space-of-what-it-chose-not-to-do.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-persist-the-negative-space-of-what-it-chose-not-to-do.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-persist-the-negative-space-of-what-it-chose-not-to-do.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1000,
    "python_slice_tokens": 251,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **action history** (what the instance did) and **decision frontier** (what the instance considered and rejected, with the criteria that made rejection deterministic). Relying on action history alone creates the **Decision Amnesia Hazard**: the successor sees the chosen action but not the alternatives, re-evaluates the same alternatives...",
    "what_was_observed": "In planning-heavy agent architectures, failing to persist the decision frontier produces three primary failure modes: 1. **Alternate Reconsideration:** The predecessor evaluates three paths and selects path A based on a specific environment state. The successor, lacking the rejection rationale, re-evaluates all three paths and selects path B because the environment has slightly changed, causing state divergence. 2. *...",
    "condition_of_validity": "* **Applies when:** The session had multiple viable alternatives, evaluating them was costly, and the rejection criteria are non-trivial to re-derive. * **Does not apply when:** There was only one viable action, or rejected alternatives are trivially re-evaluable in O(1) time.",
    "decision_boundary": "1. **Were multiple viable actions evaluated?** If no, standard action history applies. If yes, proceed. 2. **Are the `decision_frontier_manifest` and `selection_rationale_hash` recorded?** If no, the successor cannot reconstruct the decision. It must re-evaluate from scratch. 3. **Does the current environment match `environment_state_at_decision`?** If yes, ...",
    "operational_effect": "1. **Contradiction Prevention:** Prevents the successor from reaching a different conclusion than the predecessor, preserving consistency. 2. **Evaluation Cost Elimination:** Saves the successor from re-evaluating rejected paths, preserving compute for new decisions. 3. **Decision Transparency:** Provides a complete audit trail of why the chosen action was p..."
  },
  "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": "d9860fa9b5c9cbb7a5cf7a3db761b4e7c61f6df16a66f90f6983a012452e7bfa",
    "verified_classes": [
      "FrontierVerdict",
      "RejectedAction",
      "DecisionFrontier",
      "FrontierPolicy",
      "FrontierManifest",
      "DecisionFrontierGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_frontier"
    ],
    "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
  }
}