{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-contract-net-bidder-reject-a-winning-bid-when-the-sla-deadline-is-expressible-only-as-a-relative-offset",
  "title": "Why does an instance of a Contract Net Bidder Reject a Winning Bid When the SLA Deadline Is Expressible Only as a Relative Offset",
  "date_of_record": "2026 November 16",
  "scope": "Applies to contract-net (CNP) auction protocols where a manager agent solicits bids for subtasks and awards based on SLA-bound criteria (deadline, cost, quality). Covers both FIPA-ACL-style `cfp`/`propose`/`accept-proposal` flows and bespoke JSON-schema auctions. Does not apply to single-agent task schedulers or to auctions where all bidders share a synchronized clock source and a common absolute epoch.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-contract-net-bidder-reject-a-winning-bid-when-the-sla-deadline-is-expressible-only-as-a-relative-offset.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-contract-net-bidder-reject-a-winning-bid-when-the-sla-deadline-is-expressible-only-as-a-relative-offset.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-contract-net-bidder-reject-a-winning-bid-when-the-sla-deadline-is-expressible-only-as-a-relative-offset.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1530,
    "python_slice_tokens": 303,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The failure is not a timeout, a lost message, or a majority-quorum problem. It is a **temporal reference-frame mismatch** between the manager's absolute SLA deadline and a bidder's relative-offset deadline, which surfaces only at the *award* step — after the bid has already won on cost/quality. A manager issues a `cfp` with `sla.deadline = 2026-11-14T09:00:0...",
    "what_was_observed": "In a three-agent pipeline (manager M, bidders B1/B2/B3) auctioning a 30-second SLA-bound subtask: - M emitted `cfp` at `T0` with absolute deadline `T0 + 30s`. - B1 responded at `T0 + 120ms` with `commit_offset_s: 28` (feasible against its own `now`). - M awarded at `T0 + 400ms` (evaluation + award round-trip). - B1 began execution at `T0 + 520ms`. - B1 completed at `T0 + 520ms + 28s = T0 + 28.52s` — inside the deadli...",
    "condition_of_validity": "The bug manifests only when **all** of the following hold: 1. The SLA deadline is expressed (or interpreted) in absolute time by the manager but in relative time by the bidder. 2. Award latency (cfp→propose→evaluate→award→execute-start) is non-trivial relative to the slack margin. 3. The bidder's feasibility computation uses its local `now`, not the manager'...",
    "decision_boundary": "The correct decision rule is: - **Award-time re-validation is mandatory.** Before emitting `accept-proposal`, the manager must compute `effective_deadline = absolute_deadline - award_timestamp` and reject any winning bid whose `commit_offset_s > effective_deadline - safety_margin`. If the top bid fails, fall through to the next-ranked bid, not to re-solicita...",
    "operational_effect": "Uncorrected, this produces **silent SLA breaches that look like bidder failures** — the bidder is blamed for overrunning, when in fact the manager awarded an infeasible contract. Retry logic then re-auctions the subtask, but the re-auction inherits the same reference-frame mismatch and reproduces the breach, often with a shrinking deadline that compounds the..."
  },
  "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": "49715db30f813640c91088eafc48b12b79d4df267a9da28b70de4ab3e60495c9",
    "verified_classes": [
      "SLAReferenceFrameError"
    ],
    "verified_functions": [
      "validate_award",
      "award_with_fallback"
    ],
    "verified_functions_count": 2,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "SLAReferenceFrameError"
    ],
    "sample_fail_closed_invariants": [
      "No bid in the ranked set is feasible under the award-time reference frame; all offsets exceed effective slack."
    ],
    "stdlib_dependencies": [
      "time"
    ],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
