Compatibility-aware composition
Interpret exact observed relationships, documented compositions and unknown combinations.
Three distinct outcomes
An executed planning adapter, a documented architecture relationship and an unreviewed pairing are not equivalent. The registry records relationships between exact catalog identities; matching protocol names never creates compatibility.
Sample workflow
DieWeaver plus ModelNative has a locally executed adapter relationship. The adapter passes only selected resources and rechecks capacity and planning constraints. This is a software-sample relationship, not physical signoff.
Hardware combinations
The GSH/solver and memory/fabric entries use documented composition boundaries. Required companions are surfaced. Customer-specific clocks, resets, addressing, security, target PDK/library and release manifests still require agreement and qualification.
Review output
Export the review JSON and keep it with the project. Unknown edges and missing dependencies remain visible. A compatible architecture record never automatically grants a license or makes a new silicon implementation qualified.