Composition

The repository provides low-level building blocks rather than a final VC protocol.

Core Responsibilities

• canonical VC and VP bodies
• schema and verification-method references
• context-separated proof verification
• explicit holder and status bindings
• optional source-neutral signer authorization
• deterministic conformance vectors
• optional canonical Midnight DID method binding

Consumer Responsibilities

• concrete credential-family claims and predicates
• DID resolver configuration and verification-method authorization policy
• issuer and verifier trust policy
• current status evidence and registry synchronization
• challenge freshness, replay prevention, audience, and trusted time
• proving artifacts, deployment, transport, wallet, and application behavior

Package Direction

Credential-family and application repositories depend on released core packages. The core never depends on a family, protocol, application, or sibling repository. This direction keeps releases independent and the dependency graph acyclic.

credential-did-midnight is a thin extension of credential-compact. Its standalone root includes the core once; its composition root assumes the consumer has already included the core composition root.

For Ledger 8, consuming contracts materialize trusted signer decisions locally because synchronous cross-contract calls are unavailable. See Signer Authorization for the local and authority-backed flows.