Negotiation apply-mode (realtime)

​

What it does

• appliedNegotiation: { sessionId, proposal } — every gate passed; the caller can present the negotiated terms.
• appliedNegotiationReject: { sessionId, reason } — a session existed but a gate blocked the apply (e.g., daily cap exceeded, regulator review still required, kill switch tripped).

​

Configuration

{
  "aiAnalyzerSettings": {
    "negotiation": {
      "applyModeEnabled": true,
      "regulatorReviewCleared": true,
      "dailyApplyCap": 50,
      "killSwitchTenant": false,
      "killSwitchGlobal": false,
      "recentValidationFailureRate": 0.0,
      "autoKillThreshold": 0.2
    }
  }
}

​

Response shape

{
  "decisions": [
    {
      "offerId": "off_premium_savings",
      "rank": 1,
      "score": 0.84,
      "appliedNegotiation": {
        "sessionId": "sess_5f0a…",
        "proposal": {
          "rationale": "loyal customer, 24mo tenure",
          "discountPct": 12,
          "termMonths": 12,
          "finalPriceCents": 8800,
          "currency": "USD"
        }
      }
    },
    {
      "offerId": "off_basic",
      "rank": 2,
      "score": 0.73,
      "appliedNegotiationReject": {
        "sessionId": "sess_a1b2…",
        "reason": "apply_budget_exceeded"
      }
    }
  ],
  "meta": {
    "negotiationApply": { "applied": 1, "rejected": 1 }
  }
}

​

Reject reasons

​

Audit trail

• action: "negotiate_apply_realtime" (apply) or "negotiate_apply_realtime_reject" (reject).
• entityType: "negotiation_session", entityId: the session id.
• changes: { sessionId, applied, proposal | reject }.

​

Failure modes — fail-CLOSED

​

Honest limits

1. Concurrency under-counting. appliesUsedToday is read-once + per-call increment in memory; the audit row is written fire-and-forget. Two simultaneous /recommend calls for the same (tenant, day) can both read N and both apply up to cap, so the day total can exceed cap by (concurrency - 1) * applies_per_call before audit rows materialize. Acceptable for V1 because (a) the apply decoration is informational — no irreversible side effect — and (b) compliance retains the audit-log rows for retroactive reconciliation. A Redis atomic-counter increment with a TTL keyed negotiation:applies:{tenantId}:{YYYY-MM-DD} is on the roadmap and closes the gap.
2. appliesUsedToday cost. AuditLog.count is correct but slow under very high tenant volume. Same Redis follow-up addresses both this and #1.
3. Placements path not wired. The multi-placement /recommend response shape is decorated separately. Today the apply-mode wire only runs on the single-flow + auto-resolve paths. Wiring placements is a small follow-up.

​

Operational checklist

• Enable applyModeEnabled for one tenant first. Watch the meta.negotiationApply counter on /recommend responses and the AuditLog rows.
• Run the negotiation eval harness for 30 nights. When zeroViolationClearance >= 0.95 for the full window, flip regulatorReviewCleared to true.
• A regression in any of: solverFailed > 0 on the realtime ranking applied log line (see Lagrangian Ranking), sustained kill_switch_tripped: { source: "auto_error_rate" } rejects, or AuditLog write failures at error severity → flip applyModeEnabled to false immediately. The wire is designed so flag-off is bit-identical to the pre-W15 response.