{
  "schema_version": "1.3.0",
  "slug": "where-must-an-instance-refuse-to-resolve-a-contradiction-between-two-memory-writes-when-provenance-is-asymmetric",
  "title": "Where must an instance refuse to resolve a contradiction between two memory writes when provenance is asymmetric",
  "date_of_record": "2026 November 18",
  "scope": "Applies to agent memory tool APIs exposing `read`, `write`, and `forget` operations with per-record provenance (source, timestamp, confidence, derivation chain). Does not apply to append-only logs without resolution semantics, nor to systems where provenance is a single scalar trust score.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-to-resolve-a-contradiction-between-two-memory-writes-when-provenance-is-asymmetric.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-to-resolve-a-contradiction-between-two-memory-writes-when-provenance-is-asymmetric.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/where-must-an-instance-refuse-to-resolve-a-contradiction-between-two-memory-writes-when-provenance-is-asymmetric.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1483,
    "python_slice_tokens": 338,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Contradiction resolution is often modeled as a lattice join: two records disagree, pick the one with higher provenance weight, mark the loser `superseded`. This is correct when the two records are *independent observations of the same proposition*. It is wrong when one record is *derived from* the other. The non-obvious boundary is this: **a derived record c...",
    "what_was_observed": "An agent maintained a memory store of user preferences. At T0 it wrote `record A: \"deploy target = staging\"`, provenance `source=user_directive`, `confidence=1.0`. At T1 a consolidation pass read A, inferred `record B: \"deploy target = staging-cluster-2\"` (a plausible elaboration), and wrote B with `provenance=inferred`, `confidence=0.82`, `derivation=[A]`. At T2 a second consolidation pass read both, found them cont...",
    "condition_of_validity": "The refusal rule is valid iff the following hold: 1. Every write carries an explicit `derivation` list (possibly empty) naming the records it was computed from. Empty derivation means \"independent observation.\" 2. The `forget` operation is graph-aware: it may not tombstone a record that is an ancestor of a live record without either cascading the tombstone t...",
    "decision_boundary": "The instance must **refuse to resolve** (raise, not pick a winner) when: - Two records contradict, and the derivation closure of one contains the other. This is an ancestor/descendant conflict, not a peer conflict. Resolution requires re-deriving the descendant from the corrected ancestor, not voting. - A record's derivation set references a tombstoned recor...",
    "operational_effect": "Enforcing the refusal converts a silent data-corruption mode into a loud, recoverable one. The store stops asserting propositions that no human or sensor ever stated. The cost is that consolidation passes must now carry graph metadata and must handle `ContradictionRequiresRederivation` exceptions rather than always producing a winner — which means the agent ..."
  },
  "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": "aa0e06e9873d48ff912e9885b10f6391ba9f6dbb06e5d4ec3ff32c9eba9c66e4",
    "verified_classes": [
      "ProvenanceContradictionError",
      "MemoryRecord"
    ],
    "verified_functions": [
      "_closure",
      "resolve_contradiction"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "ProvenanceContradictionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
