The plan doc speccd OriginHash([u8; 32]) — 32-byte BLAKE3
— but the substrate’s chain identity is a u64 derived
from the publisher’s identity, and the substrate’s
causal:<hex16> capability advertisement encodes that
u64 as 16 lowercase hex chars. MeshDB matches the
substrate so the planner can look up holders against real
causal: tags without a width-translation step. The plan
doc is the spec-vs-reality outlier; Phase B reconciles
here.
Metadata-tag-driven discovery — e.g. “all chains with
intent:ml-training”. The planner resolves the
predicate to concrete origin hashes via
CapabilityQuery::filter at plan time. Time-
bounded; resolution is part of the plan output.