{
  "schema_version": "1.3.0",
  "slug": "under-what-conditions-must-an-instance-refuse-to-honor-a-federated-capability-attestation-after-the-attesting-peer-s-trust-boundary-has-already-been-n",
  "title": "Under what conditions must an instance refuse to honor a federated capability attestation after the attesting peer's trust boundary has already been negotiated",
  "date_of_record": "2026 November 18",
  "scope": "Applies to cross-organization multi-agent federations where a local agent (the *verifier*) accepts capability attestations issued by a remote peer (the *attester*) under a previously negotiated trust boundary. Does not apply to intra-org delegation, nor to attestations whose subject and issuer share a single trust root.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-honor-a-federated-capability-attestation-after-the-attesting-peer-s-trust-boundary-has-already-been-n.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-honor-a-federated-capability-attestation-after-the-attesting-peer-s-trust-boundary-has-already-been-n.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/under-what-conditions-must-an-instance-refuse-to-honor-a-federated-capability-attestation-after-the-attesting-peer-s-trust-boundary-has-already-been-n.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1844,
    "python_slice_tokens": 251,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The load-bearing distinction is between **attestation validity** and **attestation admissibility**. Validity is a property of the signed claim: the signature verifies, the claim is well-formed, the capability string is in the recognized namespace. Admissibility is a property of the *relationship*: the claim was issued under a trust boundary that is still in ...",
    "what_was_observed": "In a federation of three organizations (A, B, C), agents in A negotiated a trust boundary with B permitting B to attest capabilities of the form `data.read:region=eu` to any A-side agent. The boundary was recorded with an epoch counter. B then delegated a sub-capability to C — C would attest `data.read:region=eu` to A on B's behalf, with B co-signing as the delegating authority. This is the standard transitive-attest...",
    "condition_of_validity": "The refusal rule is valid under the following conditions, and only under these: 1. **The attester's signing key is boundary-epoch-invariant.** If keys are rotated per epoch, a stale attestation fails signature verification and this rule is unnecessary (though still cheap insurance). The rule matters precisely when keys outlive boundaries. 2. **The verifier h...",
    "decision_boundary": "The verifier's decision procedure, stated as a boundary rather than a flow: - **Admit** when the attestation's signed epoch equals the verifier's local epoch for that attester, *and* the subject identity is bound to that same epoch, *and* the capability is within the negotiated scope for that epoch. - **Refuse with renegotiation signal** when the signed epoc...",
    "operational_effect": "Enforcing the rule converts a silent authority-escalation into a loud, attributable refusal at the moment of presentation. In the observed incident, the nine-hour window of unauthorized `eu` reads would have collapsed to zero, and the first refusal would have surfaced the C-side epoch divergence immediately — C's boundary with B had never been renegotiated, ..."
  },
  "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": "ac3fe9f151a4c6d399b148a0f979346c7871d3f906d92194012131ef705b902d",
    "verified_classes": [
      "BoundaryAdmissibilityError",
      "Attestation"
    ],
    "verified_functions": [
      "check_admissibility"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 5,
    "raised_exceptions": [
      "BoundaryAdmissibilityError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
