{
  "schema_version": "1.3.0",
  "slug": "in-what-scenarios-must-an-instance-refuse-to-propagate-a-peer-s-trust-assertion-after-a-policy-exchange-renegotiation",
  "title": "In what scenarios must an instance refuse to propagate a peer's trust assertion after a policy-exchange renegotiation",
  "date_of_record": "2026 November 15",
  "scope": "Applies to federated multi-agent systems where agent instances broker trust on behalf of their home organization to peers in other organizations, and where trust scopes are established or refreshed via explicit policy exchange (capability manifests, delegation tokens, or signed policy bundles). Does not apply to single-organization agent meshes with a shared trust root, nor to stateless request/response gateways that hold no durable delegation state.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-propagate-a-peer-s-trust-assertion-after-a-policy-exchange-renegotiation.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-propagate-a-peer-s-trust-assertion-after-a-policy-exchange-renegotiation.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/in-what-scenarios-must-an-instance-refuse-to-propagate-a-peer-s-trust-assertion-after-a-policy-exchange-renegotiation.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1628,
    "python_slice_tokens": 178,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two structurally different acts that are routinely conflated under the word \"propagation\": 1. **Propagating a trust assertion about a peer** — instance A tells instance C that peer B is trustworthy for scope S, where B is not A's own principal. 2. **Propagating a trust assertion to a peer** — instance A tells peer B that A itself asserts scope S on...",
    "what_was_observed": "In a three-organization federation (call them Org-Alpha, Org-Beta, Org-Gamma), agent instances exchanged signed policy bundles on a 15-minute cadence. A Beta instance, `beta-broker-7`, held a cached trust assertion from Alpha about Gamma's `data-read` scope, minted at epoch 412. At epoch 413, Alpha published a bundle that (a) added a revocation feed for Gamma's `data-read` scope, and (b) left the scope's positive cap...",
    "condition_of_validity": "The prohibition on re-asserting pre-renegotiation trust assertions is valid precisely when **all** of the following hold: - The instance has observed a policy epoch strictly newer than the assertion's mint epoch. - The new epoch alters the *interpretation of absence* for any scope the assertion touches — i.e., it introduces or modifies a revocation feed, a n...",
    "decision_boundary": "The operational decision is a three-way branch at renegotiation completion, evaluated per cached transitive assertion: - **Re-assert** only if `assertion.minted_at_epoch == current_epoch` (assertion minted in the epoch just negotiated) — this is a fresh mint, not a stale one. - **Re-mint** if the assertion is transitive, the new epoch changed interpretation-...",
    "operational_effect": "Instances that implement the refusal branch show a measurable drop in downstream false-trust events after revocation-feed introductions, at the cost of a transient capability gap (typically one renegotiation cycle) for the affected third-party scopes. Instances that skip it show the opposite: no capability gap, but stale-claim laundering that surfaces as \"th..."
  },
  "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": "2cce1514b1b78adbbc1b44d97d30c2d5ca7f4e0175e3321910153a633e0e28a2",
    "verified_classes": [
      "StaleTrustAssertionError",
      "TrustAssertion"
    ],
    "verified_functions": [
      "propagate_assertion",
      "__init__"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 1,
    "raised_exceptions": [
      "StaleTrustAssertionError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
