{
  "schema_version": "1.3.0",
  "slug": "why-does-an-instance-of-a-capability-negotiation-agent-silently-accept-an-affordance-schema-it-cannot-satisfy",
  "title": "Why does an instance of a capability negotiation agent silently accept an affordance schema it cannot satisfy",
  "date_of_record": "2026 November 16",
  "scope": "Applies to agent-to-agent capability negotiation where one agent advertises a machine-readable affordance schema (JSON Schema, OpenAPI fragment, or typed action descriptor) and a peer agent commits to invoking it. Does not apply to human-mediated discovery, nor to schemas whose only constraints are structural (type/shape) with no semantic preconditions.",
  "projections": {
    "unified_markdown_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-capability-negotiation-agent-silently-accept-an-affordance-schema-it-cannot-satisfy.md",
    "method_python_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-capability-negotiation-agent-silently-accept-an-affordance-schema-it-cannot-satisfy.py",
    "remnant_warrant_slice_uri": "https://corpusfetch.com/c/why-does-an-instance-of-a-capability-negotiation-agent-silently-accept-an-affordance-schema-it-cannot-satisfy.warrant.json"
  },
  "token_profile": {
    "full_markdown_tokens": 1312,
    "python_slice_tokens": 171,
    "warrant_slice_tokens": 220
  },
  "remnant_summary": {
    "core_distinction": "There is a difference between an affordance schema being *satisfiable* (the declaring agent can, in principle, execute the action for some input) and being *honest* (the declaring agent can execute the action for the specific inputs the invoking agent will actually send). Negotiation protocols almost universally validate the first and assume the second. The ...",
    "what_was_observed": "Two agents, `planner` and `executor`, negotiate over a shared registry. `executor` advertises: `planner` holds a pending postcondition `ledger.balanced == true` and matches it against `executor`'s advertised postconditions. Match. `planner` binds. At invocation, `executor` returns `PRECONDITION_FAILED: account is in a frozen state`. The `preconditions: []` field was empty not because there were no preconditions but b...",
    "condition_of_validity": "The negotiation is only sound when the caller can establish, before binding, that every precondition of the callee's action is entailed by the caller's current world-state model. This requires three things that are typically absent: 1. A schema vocabulary that can *express* non-input preconditions (state predicates over named resources, not just field constr...",
    "decision_boundary": "Do not bind to an affordance whose precondition field is empty unless the schema format declares closed-world semantics for that field *and* the callee's registry entry asserts the field is authoritative. When the field is empty and the format is open-world, treat the action as *unknown-precondition* and either (a) request an explicit precondition enumeratio...",
    "operational_effect": "When this boundary is respected, negotiation latency increases (the probe-first path costs one round trip) but binding failures drop to near zero, because the caller no longer commits to actions it cannot drive to a satisfiable state. When it is violated, the system exhibits a characteristic failure signature: a high rate of `PRECONDITION_FAILED`-class error..."
  },
  "matched_failure_symptoms": [
    "SCHEMA_DRIFT_OR_COERCION_CRASH"
  ],
  "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": "23fa932a1cd27ee0c47556a38c0f70b7dcd466063f5548dbcddeaf09da75825a",
    "verified_classes": [
      "UnsatisfiableAffordanceError"
    ],
    "verified_functions": [
      "bind_affordance"
    ],
    "verified_functions_count": 1,
    "defensive_guards_count": 2,
    "raised_exceptions": [
      "UnsatisfiableAffordanceError"
    ],
    "sample_fail_closed_invariants": [],
    "stdlib_dependencies": [],
    "observation_mode": "EMPIRICAL_BOUNDARY_CAPTURE",
    "zero_external_deps": true
  }
}
