{
  "schema_version": "1.3.0",
  "slug": "why-must-a-session-identity-be-cryptographically-bound-to-its-execution-environment",
  "title": "Why must a session identity be cryptographically bound to its execution environment?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The token can be extracted from its environment (via logs, memory, network), and downstream services can differentiate between legitimate and replayed origins. * **Does not apply when:** The token is strictly ephemeral (",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-must-a-session-identity-be-cryptographically-bound-to-its-execution-environment.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-must-a-session-identity-be-cryptographically-bound-to-its-execution-environment.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-must-a-session-identity-be-cryptographically-bound-to-its-execution-environment.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1058,
    "python_slice_tokens": 271,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **identity validity** (the token is cryptographically signed and unexpired) and **identity-environment binding** (the token is provably bound to the specific execution environment where it was issued). Relying on validity creates the **Session Replay Hazard**: an attacker extracts the token from its intended environment (via memory dum...",
    "what_was_observed": "In agent architectures using bearer tokens, failing to bind identity to environment produces three primary failure modes: 1. **Token Exfiltration Replay:** A token leaks via a debug log, and an attacker uses it from a different continent. Downstream services accept it because signature and expiry are valid. 2. **Stolen Session Transfer:** An agent's session is migrated to a hostile environment (via compromised backup...",
    "condition_of_validity": "* **Applies when:** The token can be extracted from its environment (via logs, memory, network), and downstream services can differentiate between legitimate and replayed origins. * **Does not apply when:** The token is strictly ephemeral (single-use, expires in seconds), or the environment is sealed such that extraction is infeasible.",
    "decision_boundary": "1. **Is the token environment-bound?** If yes, standard verification applies. If no, the token is replayable and downstream services should not trust it without additional binding. 2. **Does the `token_environment_binding_signature` verify against the current environment fingerprint?** If no, the token is being used from an unauthorized environment. Reject. ...",
    "operational_effect": "1. **Replay Prevention:** Tokens cannot be used from unauthorized environments, eliminating token exfiltration replay. 2. **Origin Attestation:** Downstream services can verify not just identity but origin, enabling stronger authorization. 3. **Drift Detection:** Environment changes trigger token reissuance, preventing stale token use after compromise."
  },
  "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": "0328df83b80bc18475f1c680c558697e5e4fcb644f4ee23f3aaa6111c47901fe",
    "verified_classes": [
      "BindingVerdict",
      "SessionToken",
      "ExecutionEnvironment",
      "BindingPolicy",
      "BindingManifest",
      "SessionEnvironmentBindingGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_token"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 0,
    "raised_exceptions": [],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "dataclasses",
      "enum",
      "hashlib",
      "json"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}