{
  "schema_version": "1.3.0",
  "slug": "how-does-an-instance-detect-policy-drift-at-a-federated-protocol-boundary-when-the-ledger-is-append-only-but-the-policy-bundle-is-mutable",
  "title": "How does an instance detect policy drift at a federated protocol boundary when the ledger is append-only but the policy bundle is mutable",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federated agent systems where each organization enforces policy-as-code at the protocol boundary (request admission, capability grants, delegation chains) and records decisions to an inter-org audit ledger. Does not apply to single-org deployments with a shared policy store, nor to systems where policy bundles are content-addressed and immutable once referenced by a ledger entry.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-policy-drift-at-a-federated-protocol-boundary-when-the-ledger-is-append-only-but-the-policy-bundle-is-mutable.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-policy-drift-at-a-federated-protocol-boundary-when-the-ledger-is-append-only-but-the-policy-bundle-is-mutable.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-does-an-instance-detect-policy-drift-at-a-federated-protocol-boundary-when-the-ledger-is-append-only-but-the-policy-bundle-is-mutable.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1757,
    "python_slice_tokens": 449,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The non-obvious failure is the divergence between **decision-time policy identity** and **ledger-time policy identity**. An append-only ledger gives the illusion of a complete audit trail: every admission decision is recorded, ordered, and tamper-evident. But the ledger entry typically records the *decision* and the *policy bundle version string* — not a cry...",
    "what_was_observed": "In a two-org federation (Org A issues capability grants; Org B enforces them at its ingress boundary), an agent delegation chain was admitted for 11 days under policy bundle `grants-v7`. On day 12, Org B's security team edited `grants-v7` in place to add a constraint: delegated capabilities must carry an explicit `audience` claim. The bundle's version label was not bumped because the edit was made through a \"hotfix\" ...",
    "condition_of_validity": "The invariant \"ledger replay reproduces recorded outcomes\" holds **only if** every ledger entry commits to the cryptographic digest of the exact policy bundle bytes evaluated, and the policy store is content-addressed such that a digest resolves to immutable bytes. Under those conditions, a divergence is a genuine integrity event. The invariant is **invalid*...",
    "decision_boundary": "The operational decision is how to classify a replay divergence. The boundary: - **Divergence with matching content digests** → genuine integrity failure (ledger or store tampering). Escalate as security incident; freeze the federation. - **Divergence with mismatched or absent digests, and the current bundle resolves to different bytes than at decision time*...",
    "operational_effect": "Enforcing digest-committed policy identity at the boundary converts replay divergence from an ambiguous alarm into a precise classifier. The practical effects: 1. Hotfix paths that mutate bundles in place become detectable within one audit cycle, because the digest recorded at decision time no longer resolves. 2. Cross-org audits stop producing false tamper ..."
  },
  "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": "87da2248de3506a3f552a0ff1f0a789e1b785d2306ab42e6318b976c1a443cdc",
    "verified_classes": [
      "PolicyDriftError",
      "DivergenceClass",
      "LedgerEntry"
    ],
    "verified_functions": [
      "digest_bytes",
      "classify_divergence",
      "audit_replay",
      "evaluate"
    ],
    "verified_functions_count": 4,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "PolicyDriftError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
