{
  "schema_version": "1.3.0",
  "slug": "what-config-drift-invariants-must-survive-across-regional-failover-of-an-agent-fleet",
  "title": "What config-drift invariants must survive across regional failover of an agent fleet?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** The fleet has multiple regions with potentially divergent configs, failover can redirect traffic to a different region, and config differences materially affect behavior. * **Does not apply when:** All regions share iden",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/what-config-drift-invariants-must-survive-across-regional-failover-of-an-agent-fleet.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/what-config-drift-invariants-must-survive-across-regional-failover-of-an-agent-fleet.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/what-config-drift-invariants-must-survive-across-regional-failover-of-an-agent-fleet.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 981,
    "python_slice_tokens": 261,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **global config baseline** (the intended configuration that all regions should share) and **regional config state** (the actual runtime configuration in each region, which can drift from the baseline due to local overrides, unapplied deployments, or emergency patches). Relying on the baseline creates the **Failover Config Surprise**: f...",
    "what_was_observed": "In multi-region agent fleets, failing to reconcile config during failover produces three primary failure modes: 1. **Feature Flag Divergence:** Region A has feature X enabled, Region B has it disabled. Failover moves traffic to Region B, and the feature silently disappears for users. 2. **Quota Mismatch:** Region A is provisioned for 10x the API quota of Region B. Failover overloads Region B's quota in minutes, causi...",
    "condition_of_validity": "* **Applies when:** The fleet has multiple regions with potentially divergent configs, failover can redirect traffic to a different region, and config differences materially affect behavior. * **Does not apply when:** All regions share identical config (truly uniform), or failover only redirects within a single region.",
    "decision_boundary": "1. **Is a failover being initiated?** If no, standard config management applies. If yes, proceed. 2. **Does the target region have a `failover_eligibility_receipt`?** If no, the target region's config has not been verified for failover. Do not proceed. 3. **Does the target region's config fingerprint match the required post-failover state?** If no, the failo...",
    "operational_effect": "1. **Feature Consistency:** Prevents failover from silently disabling or enabling features. 2. **Capacity Protection:** Ensures the target region is provisioned to handle the redirected load. 3. **Compliance Preservation:** Prevents failover from violating jurisdictional constraints."
  },
  "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": "e8d8df73e2514df397e516df9ec22c81509a272fdd8e84b0d8a26d26a1fa2fd4",
    "verified_classes": [
      "FailoverVerdict",
      "RegionalConfig",
      "FailoverContext",
      "FailoverManifest",
      "RegionalConfigGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_failover"
    ],
    "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
  }
}