X00-03 — Per-named-colorant ink limits for DeviceN and spot separations #142

Outcome

Decide whether Loop enforces per-ink maxima for named colorants.

Parent and boundary

Parent: #110. This is an expansion candidate. Produce a value case, owning module, contract sketch, and threat notes, then record go, no-go, or defer. No implementation lands from this issue. A new public PDF, schema, worker, or workflow contract needs an architect checkpoint with concrete fixtures and migration behavior.

Grounding

• Preflight backlog P1 row devicen-per-colorant-ink-limit (legacy #600, Ink Manager): DeviceN ink limits per named colorant are not checked beyond inventory.
• Typical demand: packaging and spot-heavy jobs, with white, varnish, and metallic inks.

Decision inputs

• A limit model per named colorant, a profile schema sketch, fixtures, and an independent oracle.
• On go: an L01 check sub-issue and an L13 fix sub-issue.
• Failure case: a named-colorant limit never reads the process-color total as a substitute.

Required proof

Decision record with the value case (user, frequency, current alternative, evidence), owning module, contract sketch, fixtures or corpus plan, independent oracle where a claim is made, and risks.

Handoff

State go, no-go, or defer. On go, file bounded implementation sub-issues under the owning module parent and link them here.

Sources

Approved master roadmap §5 · Gap review of the issue suite against the approved roadmap, 2026-09-27.