Edition Records - Condition Coverage Map

Use this endpoint when you need to verify that a set of named modules is fully covered in a specific edition record — particularly when you need the exactly-one-per-module constraint enforced and want a structured coverage map rather than a simple boolean. Prefer this over generic schema validators when working with library edition records that carry publisher/jurisdiction/source/revision context. It is a declared-record analysis tool, not an independent certification service.

• Missing required module: a requested module name has no matching declared-present entry in the edition record
• Duplicate module entry: more than one declared-present entry found for a requested module, violating the exactly-one constraint
• Invalid edition reference: editionRef, editionRevision, or manifestDigest does not match any known edition record
• Unsupported data class: dataClass value outside allowed enum ('public','synthetic') returns validation error
• Too many required modules: requiredModules array exceeds maxItems:4 limit
• nonpersonalMetadata not set to true: const constraint violation causes request rejection
• Empty or malformed rows array: row entries that cannot be bound to module declarations return partial coverage results