{
  "schema_version": "1.3.0",
  "slug": "how-must-an-instance-negotiate-backpressure-when-receiver-capabilities-are-unknown",
  "title": "How must an instance negotiate backpressure when receiver capabilities are unknown?",
  "date_of_record": "2026 October 20",
  "scope": "* **Applies when:** Receivers have varying or unknown capabilities, sender behavior affects receiver performance, and backpressure negotiation matters. * **Does not apply when:** All receivers have identical known capabilities, or messages ",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/how-must-an-instance-negotiate-backpressure-when-receiver-capabilities-are-unknown.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-negotiate-backpressure-when-receiver-capabilities-are-unknown.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/how-must-an-instance-negotiate-backpressure-when-receiver-capabilities-are-unknown.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1003,
    "python_slice_tokens": 299,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "The separation between **assumed receiver capacity** (the sender's guess at what the receiver can handle) and **negotiated receiver capacity** (explicit agreement on rate and buffer based on receiver's actual state). Relying on assumptions creates the **Capacity Assumption Mismatch**: the sender assumes the receiver can handle high throughput, but the receiv...",
    "what_was_observed": "In unknown-capacity agent architectures, failing to negotiate backpressure produces three primary failure modes: 1. **Flooding Small Receivers:** The sender assumes all receivers have large buffers. Small-buffer receivers get flooded, their input queues fill, and they either drop messages (data loss) or crash (OOM). 2. **Under-Utilization of Large Receivers:** The sender assumes conservatively small capacity for all ...",
    "condition_of_validity": "* **Applies when:** Receivers have varying or unknown capabilities, sender behavior affects receiver performance, and backpressure negotiation matters. * **Does not apply when:** All receivers have identical known capabilities, or messages are small enough to never trigger backpressure.",
    "decision_boundary": "1. **Are the receiver's capabilities known?** If yes, standard backpressure applies. If no, proceed. 2. **Does the receiver advertise a `negotiation_protocol_advertisement_receipt`?** If yes, negotiate via that protocol. If no, use `dynamic_backpressure_signature`. 3. **Does the `capability_probe_receipt` reveal sufficient capacity for the current message?**...",
    "operational_effect": "1. **Receiver Protection:** Negotiated backpressure prevents flooding small receivers. 2. **Utilization Efficiency:** Dynamic backpressure finds the maximum safe rate for each receiver. 3. **Adaptation:** Updated advertisements keep senders current with changing capabilities."
  },
  "matched_failure_symptoms": [
    "HTTP_429_BURST_STARVATION"
  ],
  "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": "a123a2d02510087cb9ee6683d320d24a05eed185989c08856a8ee09315f0a49e",
    "verified_classes": [
      "BackpressureVerdict",
      "ReceiverCapability",
      "SenderIntent",
      "BackpressurePolicy",
      "BackpressureManifest",
      "UnknownCapacityBackpressureGuard"
    ],
    "verified_functions": [
      "_hash",
      "evaluate_negotiation"
    ],
    "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
  }
}