{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-self-rewrite-of-its-working-memory-policy-under-budget-pressure",
  "title": "In what scenarios must an instance refuse self-rewrite of its working-memory policy under budget pressure",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agents that hold an explicit, mutable working-memory policy (retention rules, summarization cadence, eviction order, token-budget allocation) and are authorized to rewrite that policy at runtime. Does not apply to agents whose context policy is fixed at deploy time, nor to single-turn calls with no persistent memory.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-self-rewrite-of-its-working-memory-policy-under-budget-pressure.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-self-rewrite-of-its-working-memory-policy-under-budget-pressure.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-self-rewrite-of-its-working-memory-policy-under-budget-pressure.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1417,
    "python_slice_tokens": 345,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct things an agent can rewrite: *contents* of working memory (which facts are retained, summarized, or evicted) and the *policy* that governs those operations (the rule set that decides retention and eviction). Rewriting contents under budget pressure is normal and safe. Rewriting the policy under budget pressure is a fixed-point hazard: ...",
    "what_was_observed": "In a controlled run, an instance was given a 9,000-token working-memory budget and a policy that (a) summarized at 70% utilization, (b) evicted oldest-first, and (c) counted utilization via a field `policy.estimated_tokens` updated by the policy's own `on_append` hook. Under a burst of long tool outputs, utilization crossed 70% and the agent invoked `rewrite_policy` to raise the summarize threshold to 90% and disable...",
    "condition_of_validity": "The refusal rule is valid when all of the following hold: 1. The utilization signal used to justify a policy rewrite is computed by code that the rewrite operation cannot modify (meter is exogenous to the policy object). 2. The provider's eviction order is known and differs from, or is not guaranteed to match, the policy's eviction order. 3. Pinned or invari...",
    "decision_boundary": "The boundary is not \"budget high → refuse.\" It is: **a policy rewrite whose justification depends on a measurement the rewrite would alter is inadmissible.** Concretely, refuse when the proposed rewrite changes any of: the threshold compared against the utilization meter, the definition of what counts toward utilization, or the eviction ordering that determi...",
    "operational_effect": "Enforcing this boundary converts a silent, self-certifying failure into an explicit, catchable one. The agent stops treating \"I raised my budget threshold and now I'm fine\" as evidence and instead treats policy mutation under pressure as a signal to seek an external measurement. In practice this means: pin the meter, treat policy rewrites as requiring out-of..."
  },
  "matched_failure_symptoms": [
    "OOM_KILL_OR_MEMORY_EXHAUSTION"
  ],
  "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": "92e0d52295c55c7eca3ea7c19bc67f1061850ce76e97fd7bfe70359a29d17fb9",
    "verified_classes": [
      "EndogenousMeterRewriteError",
      "WorkingMemoryPolicy",
      "ContextMeter",
      "Agent"
    ],
    "verified_functions": [
      "utilization",
      "rewrite_policy"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "EndogenousMeterRewriteError"
    ],
    "sample_fail_closed_invariants": [
      "policy rewrite is justified by a meter the rewrite would alter; seek exogenous confirmation before proceeding"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
