# Complete constructed cases and calculation

Every identifier and event is fictional. No actual person, send, response, credit return or billing observation is claimed.

C1: The existing purpose is answering an agreed source question. A Basic sender is not connected and the supplied input explicitly offers a free Open Profile route. There is no observed refusal or earlier unanswered InMail; no credit is needed. Decision: free route identified. Complete unsent teaching draft: “Thanks for pointing me to the field definition. Which published revision should I review? I can check that version and identify the unresolved terms.” Result: a draft and route decision, not a send or response.

C2: Existing member Premium has three units, a nonconnection, an offered member InMail route and an earlier unanswered InMail to that same member. Decision: hold the repeated InMail. A positive balance does not remove the documented boundary. There is no repeat draft or switch of product/account to bypass it.

C3: Ledger message A was sent on 2 October 2026 and explicitly declined on 4 October: “Thank you, but this is not relevant to the task I am working on.” The constructed return restores one unit. Response delay: two days. Decision: a returned credit and a negative response, not positive interest or a customer. Message B remains pending, not declined.

C4: The input offers eight member Premium units for use in Sales Navigator. Decision: hold the product mismatch. These eight units belong to the declared member pool and establish no capacity in another product. No interface was opened or other subscription started.

## The six actual input rows

E0 opening +5 → 5; E1 send A −1 → 4; E2 send B −1 → 3; E3 return A +1 → 4; E4 new allotment +5 → 9; E5 expiry −1 → 8. Total: 5 − 2 + 1 + 5 − 1 = 8. The five-unit monthly allotment is a chosen teaching input, not a universal plan promise.

The expired unit has a supplied basis of 3 August 2026, 10:00 UTC and expiry on 1 November 2026, 10:00 UTC: 90 days of credit age. This differs from the two days between sending message A and its response. The model does not establish a native consumption-order rule.

Result: two constructed sends, one explicitly negative response, no positive response, one pending message and one returned unit. A balance rise from five to eight does not establish three replies. No final response fraction is estimated with that pending case. Every case ends without an actual send.