{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-identity-attestation-succeed-while-continuous-posture-binding-fails-silently-in-aaif-flows",
  "title": "Why does an instance identity attestation succeed while continuous posture binding fails silently in AAIF flows",
  "date_of_record": "2026 November 15",
  "scope": "Applies to Agent-to-Agent Identity Federation (AAIF) flows where an agent's identity key is hardware-backed (TPM 2.0, Secure Enclave, or equivalent) and posture is asserted continuously via a posture assertion token (PAT) refreshed on a short cadence. Does not apply to bearer-token-only flows, nor to one-shot attestation at session establishment where no posture re-binding occurs after the initial handshake.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-identity-attestation-succeed-while-continuous-posture-binding-fails-silently-in-aaif-flows.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-identity-attestation-succeed-while-continuous-posture-binding-fails-silently-in-aaif-flows.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-identity-attestation-succeed-while-continuous-posture-binding-fails-silently-in-aaif-flows.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1624,
    "python_slice_tokens": 294,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct cryptographic events in an AAIF flow, and they are frequently conflated in implementation: 1. **Identity attestation** — proof that the private key resides in a hardware root of trust and that the key is bound to a specific agent identity (measured boot state, EK/AK chain, endorsement certificate). This is a *point-in-time* fact about ...",
    "what_was_observed": "In a federated deployment spanning three trust domains, agents refreshed PATs every 30 s. The verifier cached the hardware attestation verdict (EK chain + AK quote) for the lifetime of the session (default 8 h) to avoid re-quoting on every PAT. Posture evaluation was performed only when the identity cache missed. Observed sequence over ~40 minutes on a single agent: - `t+0`: identity attestation passes; posture `poli...",
    "condition_of_validity": "The silent-drift failure occurs if and only if all of the following hold simultaneously: 1. The verifier caches identity attestation with a TTL strictly greater than the PAT refresh interval (i.e., `identity_cache_ttl > pat_interval`). 2. The posture collector on the agent side reads from a snapshot that is not invalidated by the events that change posture (...",
    "decision_boundary": "The correct design decision is not \"cache or don't cache identity\" — caching identity attestation is necessary for throughput, since TPM quotes cost 50–200 ms and cannot run at 30 s cadence across thousands of agents. The boundary is: - **Cache identity attestation** with TTL up to session lifetime. Safe, because the key's provenance does not change without ...",
    "operational_effect": "When the boundary is respected, posture drift is detected within one PAT cycle (30 s in the observed deployment), and the agent is quarantined to a re-attestation flow before the next privileged action. When it is violated, the mean time to detection equals the identity cache TTL (8 h), during which the agent operates with an unverified posture under a valid..."
  },
  "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": "f9cf6fe7700501bfeed3af86d112572870dfbd0d0f69041d2af25b23187655c1",
    "verified_classes": [
      "PostureBindingError",
      "PostureAssertion",
      "VerifierState"
    ],
    "verified_functions": [
      "verify_pat"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "PostureBindingError"
    ],
    "sample_fail_closed_invariants": [
      "nonce mismatch: posture assertion is a replay, not a fresh binding"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
