A parsed CIP-57 blueprint.

A validator entry in the blueprint.

CIP-57 schema for a Plutus data type.

A single constructor alternative in a schema.

Load and parse a CIP-57 blueprint from a file path.

The compiled codes the four registry pins derive from: the application whose mint arm certifies an edge, and the witness policy the three token kinds are derived from.

The four policy pins of a registry are derived from these two, so every consumer of the application — the conformance rows, the devnet end-to-end and the bounded journey — binds to one source and moves together.

#173 I2: for the OPEN registry both now come from the registry partition's own blueprint. The record keeps its name because every consumer names its fields; renaming it is a sweep this ticket does not need.

#173 A173-BOOT: the four pins of an OPEN registry, read from the registry partition's own blueprint and nothing else.

The open registry's application is open.open — parameterless, so its compiled hash IS its policy id, with no applied hash to derive (A-001 row 1; Lean openPolicyParameters = []). Its three token witnesses are witness.witness in the SAME blueprint, which moved here from the naming partition in this ticket (I2). A boot therefore consults REGISTRY_BLUEPRINT alone: no naming blueprint participates, and NAMING_BLUEPRINT need not be set at all.

Both codes are read from the SAME blueprint, so a consumer cannot silently pair an open application from one build with witnesses from another.

Validate a Data value against a Schema, resolving $ref through the definitions map.

Find the first validator whose title starts with the given prefix and return its hash.

Find the first validator whose title starts with the given prefix and return its compiled script bytes as a ShortByteString. The hex-encoded compiledCode is decoded to raw bytes suitable for PlutusBinary.

Apply a Data parameter to a UPLC script. The blueprint's compiledCode is a flat-encoded UPLC program that expects one parameter. This function applies the supplied Data value to that parameter slot, producing the final script bytes.

Apply an integer parameter to a UPLC script.

`witness(kind, registry)` (#157 mint-matches-edge-deltas) takes its kind as a plain integer, and the deployment applies it three times. Wrapping the Data encoding here keeps the Data vocabulary inside this module, where the rest of the blueprint's encoding already lives.

Apply a raw bytes parameter to a UPLC script.

Apply an OnChainTxOutRef parameter to a UPLC script. Wraps applyDataParam with the canonical Constr 0 [bytes, integer] encoding produced by the 'ToData OnChainTxOutRef' instance — matching what the on-chain validator's parameter slot expects when the Aiken validator is parameterized by an OutputReference.

Apply the state validator's previousPolicies allowlist parameter. The on-chain parameter type is List<PolicyId>, encoded as List [B pid0, B pid1, …] (an empty List [] for a genesis cage, which makes migration into it impossible).

Apply request-validator parameters in source order: statePolicyId first, then cageTokenName.