{
  "schema_version": "1.3.0",
  "slug": "when-must-an-instance-normalize-cross-protocol-identity-assertions-before-appending-to-an-audit-log",
  "title": "When must an instance normalize cross-protocol identity assertions before appending to an audit log",
  "date_of_record": "2026 November 12",
  "scope": "Applies to audit-log writers that ingest identity assertions from MCP (OAuth 2.1 resource-server tokens), A2A (Agent Card / task-scoped bearer credentials), and AAIF (agent identity federation assertions) into a single hash-chained, tamper-evident log. Does not apply to single-protocol logs, nor to logs where the assertion is stored as an opaque blob without semantic normalization.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/when-must-an-instance-normalize-cross-protocol-identity-assertions-before-appending-to-an-audit-log.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-normalize-cross-protocol-identity-assertions-before-appending-to-an-audit-log.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/when-must-an-instance-normalize-cross-protocol-identity-assertions-before-appending-to-an-audit-log.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1872,
    "python_slice_tokens": 384,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There are two distinct operations that look identical at the API surface: *recording* an identity assertion and *normalizing* one. Recording appends the raw token bytes (or a digest of them) as an opaque field. Normalizing parses the assertion into a canonical subject, issuer, audience, and validity window, then binds that canonical form into the hash chain....",
    "what_was_observed": "In a federated deployment spanning an MCP tool server (resource-server tokens scoped to `aud=mcp://tools.internal`), an A2A task broker (task-scoped bearer credentials with `sub` derived from the Agent Card's `url`), and an AAIF assertion issuer (Ed25519-signed assertions with `sub` as a DID), three failure classes appeared in the first 30 days of operation: 1. **Subject aliasing across protocols.** The same human op...",
    "condition_of_validity": "Normalize-before-append is *required* when all of the following hold: - The deployment ingests assertions from ≥2 protocols with non-isomorphic subject semantics (MCP `sub`, A2A agent identity, AAIF DID). - The log is used for cross-protocol correlation (i.e., a query like \"what did principal X do across MCP and A2A\" must return a coherent answer). - The log...",
    "decision_boundary": "The boundary is crossed — and the log becomes semantically forgeable — at the moment a normalizer is allowed to *drop* an input it cannot map, rather than refusing the append. A normalizer that maps `(issuer, protocol, subject)` → canonical subject and returns `None` on unknown input, with the caller coercing `None` to `\"unknown\"` or `null`, silently launder...",
    "operational_effect": "After moving to fail-closed normalization with quarantine chains, the observed effects were: - Cross-protocol correlation queries returned 100% precision on a 10k-entry replayed corpus, versus 71% under the permissive normalizer (the 29% were aliased or bucketed subjects). - The A2A audience-replay class vanished: replays produced quarantine entries, not cha..."
  },
  "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": "5152ac1fd99b248390fb378dbbaf10716e5f70ba9fd60762e718dab638232a94",
    "verified_classes": [
      "SemanticForgeError",
      "Assertion"
    ],
    "verified_functions": [
      "normalize_for_chain",
      "append_to_chain"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 3,
    "raised_exceptions": [
      "SemanticForgeError"
    ],
    "sample_fail_closed_invariants": [
      "assertion not yet valid at reference clock"
    ],
    "stdlib_dependencies": [
      "dataclasses",
      "hashlib",
      "json",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}