{
  "schema_version": "1.3.0",
  "slug": "what-happens-when-an-instance-reports-compaction-fidelity-against-a-stale-replay-baseline",
  "title": "What happens when an instance reports compaction fidelity against a stale replay baseline",
  "date_of_record": "2026 November 18",
  "scope": "Applies to memory-compaction fidelity measurement in systems that validate compaction output by replaying a recorded access trace against both pre-compaction and post-compaction heap images, comparing reconstructed values and object identity graphs. Does not apply to compaction correctness proofs based on static typing/borrow rules, nor to pure GC throughput benchmarks where no replay baseline is recorded.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-reports-compaction-fidelity-against-a-stale-replay-baseline.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-reports-compaction-fidelity-against-a-stale-replay-baseline.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-happens-when-an-instance-reports-compaction-fidelity-against-a-stale-replay-baseline.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1471,
    "python_slice_tokens": 276,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "Compaction fidelity is not \"the post-compaction heap is byte-equal to the pre-compaction heap.\" It is \"replaying a fixed access trace over the post-compaction heap yields the same *observable* sequence of reads, writes, and identity comparisons as replaying it over the pre-compaction heap.\" The metric is therefore a property of a (heap, trace) pair, not of t...",
    "what_was_observed": "In a system using replay-based regression (record trace → compact → replay → diff observable log), an instance began reporting a fidelity drop of 0.3–0.7% on an otherwise unchanged compactor. The diff showed mismatches concentrated in two event classes: `identity_hash` reads on objects that had been reallocated across a previous run, and `weakref_liveness` probes whose result flipped from dead to live. Investigation ...",
    "condition_of_validity": "A replay-based fidelity score is valid only when all of the following hold: 1. **Baseline provenance is pinned.** The trace baseline must be recorded against a heap snapshot from the *same allocation epoch* as the compaction under test, or against a snapshot whose dead-object layout is explicitly excluded from the trace. If the baseline is recorded post-comp...",
    "decision_boundary": "- **If the diff is confined to address-sensitive events and the baseline epoch differs from the test epoch →** treat as baseline staleness. Re-record the baseline or re-derive identity handles. Do not modify the compactor. - **If the diff includes address-invariant events (logical field values, reachability of live objects) →** treat as a genuine compaction ...",
    "operational_effect": "Instances that hit this boundary without the classification above typically exhibit a fidelity metric that oscillates with allocation history rather than with compactor changes, leading to alert fatigue and eventual suppression of the metric. The correct operational posture is to make baseline epoch an explicit, versioned artifact alongside the trace, and to..."
  },
  "matched_failure_symptoms": [
    "CONTEXT_DRIFT_OR_ATTENTION_DILUTION"
  ],
  "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": "6c8b194af0121b17ee225f89b41356e81c95b3f2390c9d2cad87c1a2e3aadc59",
    "verified_classes": [
      "EventClass",
      "BaselineStalenessError",
      "CoverageRegressionError",
      "FidelityReport"
    ],
    "verified_functions": [
      "validate_fidelity_report",
      "run_fidelity_gate"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "BaselineStalenessError",
      "CoverageRegressionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
