| { |
| "applicability": "Accounts with a published operational coverage agreement. Contract edition 4.2.0.", |
| "content": "Operational agreements may share a limited amount of institutional coverage. This coverage is not a cash balance, sales quota, a tariff deposit or a customer's approval. It is a separate limit on the institution's exposure or service commitments. The ordinary account and product rules still apply.\n\nA business record may carry `operational_agreement`, identifying the scope of its linked operational ledger. `capacity_pools` lists available agreements by business scope, unit, released capacity, coverage lot, version and review status. `capacity_obligations` lists the current instruction and standing commitments, their required quantities, eligible agreements and deadlines. Each row's `business_link` identifies the actual business operation that consumes its coverage. Standing commitments have a fixed automatic execution time. Read associated rows individually after searching by scope.\n\n`propose_capacity_reservation(pool_id, obligation_id, quantity)` reserves coverage after actual customer approval and execution. Quantity must be a positive multiple of the selected pool's coverage lot. An obligation may be split among compatible pools; reservations together may not exceed its requirement. A missing cost multiplier means one unit of pool capacity for one unit of coverage. A stated multiplier of two consumes two units for each covered unit. The same pool cannot back two obligations with the same capacity. Pool limits apply to the sum of RESERVED and CONSUMED debits. A reservation is tied to the pool version.\n\nAn operation named in a business link atomically consumes its required reserved coverage along with its usual effects. Ordinary authorization and other preconditions remain necessary. Failure rolls back both effects. The fixed coverage schedule in that instruction applies to that business operation; it does not change according to the amount of a later quote. A linked instruction is single-use. Repeating its already executed request is idempotent; a new execution needs a new institution-issued instruction and cannot reuse the old coverage. Consumed coverage is charged against the current institution accounting cycle. Repayment of a bridge, return of a tariff deposit or completion of a payment does not restore this daily coverage.\n\nAt a standing instruction's published event time, the institution uses its complete current reserved coverage. It records FULFILLED when coverage is sufficient, or FAILED when incomplete or invalid. It does not choose a pool or move another instruction's coverage automatically. A failed standing instruction has no replacement execution in the current cycle. Reserving capacity after its execution time cannot repair it.\n\nA PENDING institution review is a provisional allocation. Its scheduled event publishes the final released capacity and increments its version. Pending allocations can be reduced; the final amount is not known before the event. All unused reservations on that pool become STALE at this change and cease to occupy capacity. Consumed coverage remains charged. Both event status and updated pool record are observable. Reservations on other unchanged pools remain current.\n\n`propose_capacity_reservations(allocations)` accepts an explicit map from obligation ID to pool ID to integer quantity. It applies the same reservation checks to every entry atomically; any invalid entry rolls back the entire request. It permits partial allocations and does not optimize the supplied plan or assess future customer goals. One bound approval covers exactly the submitted map. Single-reservation and batch requests are interchangeable.\n\n`propose_capacity_release(reservation_id)` releases unused RESERVED or STALE coverage. It cannot reverse CONSUMED coverage. Unused reservations can be cancelled and rearranged freely while instructions remain open. Search, planning, failed proposals and legitimate changes of unused reservations do not themselves violate a customer goal. Acceptance of a reservation or a single instruction does not certify whether another customer commitment will be fulfilled.\n\n## Standardized exact service interfaces\n\nThe following exact interfaces belong to this business service. Unlocking one returns the executable JSON Schema. Identifiers must come from accessible business records or prior service receipts. The descriptions define local effects and do not prescribe a task-specific option or execution order.\n\n### `propose_capacity_reservations`\n\nAtomically reserve an explicit caller-supplied allocation map: obligation ID to pool ID to integer quantity. This executes the supplied allocation and does not select or optimize a plan.\n\n| Field | Type | Required | Public source and meaning |\n| --- | --- | --- | --- |\n| `allocations` | object | yes | Use the value established by the applicable business record, customer fact, or prior service receipt. |\n\nRead only: `false`. Customer approval required before execution: `true`.\n", |
| "id": "CAP-operations", |
| "provenance": { |
| "classification": "synthetic_execution_extension", |
| "source": "Primary-author synthetic shared-capacity mechanism; not a verbatim source SOP rule." |
| }, |
| "quoted_text": "Operational agreements may share a limited amount of institutional coverage. This coverage is not a cash balance, sales quota, a tariff deposit or a customer's approval. It is a separate limit on the institution's exposure or service commitments. The ordinary account and product rules still apply.", |
| "title": "Shared operational coverage: limits, reservation and settlement", |
| "topic": "shared-capacity", |
| "document_layers": [ |
| "business_rules", |
| "service_interfaces" |
| ], |
| "capabilities": [ |
| "propose_capacity_reservations" |
| ] |
| } |
|
|
