Dominant Resource Share Reconciliation Reconcile divisible task allocations across heterogeneous resource capacities and see which cap or exhausted resource stops each task.
Reconcile divisible task allocations across heterogeneous resource capacities and see which cap or exhausted resource stops each task. Unweighted capped dominant-share progressive filling, fixed nonzero demand vectors; at most sixteen tasks, two to six resources and two independent records. Capacities are positive integers and demands/caps are nonnegative integers up to one million in consistent supplied units. Exact reduced fractions and event certificates preserve fractional work. Reported numerator and denominator fields accept safe integer numbers or canonical unsigned decimal strings without signs, whitespace, exponents or leading zeros; only the numerator may be zero. String numerators allow at most 141 digits and denominators at most 135 digits. Equivalent non-reduced claims are compared exactly. Whole-document limits still apply: 36,000 UTF-8 bytes, 6,000 value nodes and depth 24, with a 500,000-byte result profile; exact rational arithmetic retains its 16,384-bit and 100,000-operation guards. Individual fields fitting their bounds do not guarantee that all claims and identifiers fit together in one document. Zero-cap tasks freeze at event zero; simultaneous events freeze together in supplied order. Each event raises all active dominant shares equally until the next resource or cap limit. No indivisible-task scheduling, weights, arrivals, prediction or strategy-proofness claim. The shared pre-checkout check evaluates semantic dimensions, feasibility and the bounded exact calculation before acceptance. Private JSON report, retained for 30 days. One-time USD 9.00 job. Uses only supplied records; no external system changes. Exact within the stated finite model, with no inferred demand, travel data or operational guarantee. Integral report quantities must remain exactly representable; unsupported calculation profiles reject before checkout. Use authorized, non-sensitive data. The report describes supplied records and does not change external systems.
Agent API guide → · Website orders show the report on your private order page.
Your input · JSON Load a small example The complete checkout request must fit within 40,000 UTF-8 bytes. Your input is validated again before an order is created.