{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-apply-a-model-driven-pruning-decision-to-its-own-context-policy",
  "title": "Under what conditions must an instance refuse to apply a model-driven pruning decision to its own context policy",
  "date_of_record": "2026 November 17",
  "scope": "Applies to agents that own a mutable context policy (pruning thresholds, rewrite directives, priority weights) and that may accept edits to that policy proposed by the model itself during inference. Does not apply to externally administered policies, nor to read-only context views where the model cannot mutate its own operating parameters.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-apply-a-model-driven-pruning-decision-to-its-own-context-policy.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-apply-a-model-driven-pruning-decision-to-its-own-context-policy.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-apply-a-model-driven-pruning-decision-to-its-own-context-policy.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1372,
    "python_slice_tokens": 162,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a difference between *the model deciding what to keep in context* and *the model deciding what rule governs what is kept*. The first is a per-turn content decision and is reversible within the turn. The second is a mutation of the mechanism that produces future content decisions, and it is not reversible by the same mechanism that authorized it. A m...",
    "what_was_observed": "During a long-horizon session, the instance was permitted to reweight priority scores for retained context segments. It observed that a large block of low-priority segments — a set of tool-call transcripts from an earlier phase — was consuming budget and had not been referenced in recent turns. The model proposed, and the runtime accepted, a reweighting that drove those segments below the pruning threshold. On the su...",
    "condition_of_validity": "The refusal to apply a model-driven policy edit is valid precisely when all of the following hold: 1. The edit targets a parameter that governs retention or selection of future context (threshold, weight, rewrite rule, eviction predicate). 2. The evidence that motivated the edit is itself stored in the context region the edit would affect, directly or transi...",
    "decision_boundary": "The operative boundary is not \"is this edit good?\" but \"can this edit be undone by the mechanism it modifies?\" A policy edit that lowers a retention threshold is safe to apply in-band only if the lowered threshold does not also lower the retention of the audit ledger that would let an operator reverse it. Concretely: - **Apply in-band** when the edit's justi...",
    "operational_effect": "Enforcing this boundary converts a silent, irreversible context loss into an explicit, auditable deferral. The instance retains the ability to *propose* aggressive pruning while being unable to *commit* it until the evidence trail is externalized. The cost is latency — one extra turn or one confirmation step — and the benefit is that every committed policy c..."
  },
  "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": "7c8cda3a31c99ed6879f550d86d5f7d1ca13ae577c2aa4490721e680b3621f79",
    "verified_classes": [
      "PolicySelfMutationError"
    ],
    "verified_functions": [
      "apply_policy_edit"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "PolicySelfMutationError"
    ],
    "sample_fail_closed_invariants": [
      "Refusing in-band policy edit: cited evidence lies inside the region the edit would prune, and the audit ledger is itself",
      "Deferring policy edit: evidence is inside the affected region; stage a snapshot and require out-of-band confirmation bef"
    ],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
