X00 — Expansion candidate register #110

Outcome

Deferred and expansion capabilities each carry a value case, owning module, contract sketch, and threat notes, and receive an explicit go, no-go, or defer before any implementation issue is scheduled.

Owner

Product architecture. This is a decision register, not a feature milestone; a go decision files work under the owning module parent.

Entry dependencies

• None.

Exit gate

Every sub-issue ends with a recorded decision; each go names its owning module and links the bounded implementation sub-issues filed there.

Native sub-issues

• X00-01 — Decide the conditional Extensions module
• X00-02 — Re-file parked legacy expansion candidates with value cases
• X00-03 — Per-named-colorant ink limits for DeviceN and spot separations
• X00-04 — Barcode, slug, Braille, and dieline geometry validation
• X00-05 — Standards currency: PDF/X-6, PDF 2.0 output intents, and GWG 2022 check sets
• X00-06 — Verifiable receipts and content credentials for published artifacts
• X00-07 — XJDF/JMF job-ticket and device-outcome interchange
• X00-08 — Bounded local automation interface for agents and integrations
• X00-09 — PDF/UA accessibility preflight

Evidence and scope rules

Roadmap §5 keeps ink, imposition, marks, direct editing, collaboration, the plugin SDK, and several benchmark-gated items as conditional candidates that need a value case and their own module contract. Those legacy issues are no longer reachable after the rename, and the preflight coverage backlog's P1 rows point at them.

Sources

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