{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-cross-org-federation-policy-engine-silently-widen-a-delegated-capability-when-a-peer-s-audit-trail-reconciliation-clock-drif",
  "title": "Why does an instance of a cross-org federation policy engine silently widen a delegated capability when a peer's audit-trail reconciliation clock drifts backward",
  "date_of_record": "2026 November 18",
  "scope": "Applies to federated delegation systems where capability grants carry a validity window that is evaluated against a peer-supplied audit timestamp rather than the local monotonic clock, and where reconciliation merges two audit trails by event time. Does not apply to single-org delegation engines, nor to federation models that anchor all capability windows to a trusted time authority (e.g., Roughtime or a signed transparency log with monotonic sequencing).",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-cross-org-federation-policy-engine-silently-widen-a-delegated-capability-when-a-peer-s-audit-trail-reconciliation-clock-drif.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-cross-org-federation-policy-engine-silently-widen-a-delegated-capability-when-a-peer-s-audit-trail-reconciliation-clock-drif.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-cross-org-federation-policy-engine-silently-widen-a-delegated-capability-when-a-peer-s-audit-trail-reconciliation-clock-drif.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 2187,
    "python_slice_tokens": 498,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The distinction that matters is between *capability expiry* and *capability revocation visibility*. Most policy engines conflate them. A capability grant `(subject, resource, verb, not_before, not_after)` has a deterministic expiry: at `not_after` the grant is dead regardless of what any peer says. Revocation, by contrast, is a *distributed fact* that become...",
    "what_was_observed": "In a two-org federation (Org A delegates to Org B; Org C is a relying party that consumes Org B's audit trail), the following sequence was reproduced: 1. Org A issues grant `G` to Org B with `not_after = T+3600s`, `grant_id = g-7f3a`. 2. At `T+1800s`, Org A revokes `g-7f3a`, emitting revocation event `r-9c1e` with `event_time = T+1800s`. 3. Org A's audit trail is exported to Org C. Org C's reconciler merges by `event...",
    "condition_of_validity": "The invariant \"a reconciled audit trail is a faithful representation of delegation state\" holds **only if** the reconciler's merge key includes a stable, peer-assigned, monotonic grant identity (not `event_time`) **and** the relying party's liveness evaluation uses a clock that is monotonic with respect to the peer's event stream. In practice this means one ...",
    "decision_boundary": "The boundary is not \"should we trust the peer's clock.\" It is: **at what point does a replayed event become a new fact rather than a correction of an old one?** - If the replay carries the *same* `(grant_id, not_before, not_after)` tuple, it is a duplicate — dedup by tuple, no new instance. - If the replay carries a *different* `not_after` for the same `gran...",
    "operational_effect": "The net effect is a **capability resurrection window** equal to `drift + (not_after_replay - not_after_original)`, bounded only by the peer's maximum clock step and the grant's original TTL. In the reproduced case, 800s. In a federation with hourly NTP steps and 24h grants, the window can be hours. During this window: - The relying party (Org C) authorizes a..."
  },
  "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": "41508aa6b44690e7900b1624a4327529bcf0df0176aee87db4130eb3a8394ec0",
    "verified_classes": [
      "FederationReconciliationError",
      "GrantEvent",
      "RevocationEvent"
    ],
    "verified_functions": [
      "reconcile",
      "is_live"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 4,
    "raised_exceptions": [
      "FederationReconciliationError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [
      "__future__",
      "dataclasses",
      "typing"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
