Design impact
analyzeDesignImpact propagates a declared set of changed authored IDs through
the document graph and every current evaluation context:
Feature hashes
hashDesignFeatures resolves one effective configuration and parameter context,
then hashes the Merkle feature DAG:
- node ID and kind
- output kind
- versioned SHA-256 feature hash
- active direct dependencies in authored order
- resolved direct parameter values
- persistent topology references actually consumed by the node
What a feature hash proves
A matching hash proves that the normalized effective feature intent admitted by hash protocol v1 is identical. It does not prove:- a kernel version is unchanged
- two native shapes are geometrically identical
- topology keys are reusable
- a serialized shape artifact is safe to decode
- an unmodeled external dependency is unchanged
Document hash
hashDocument computes SHA-256 over canonical document JSON, optionally
excluding root metadata. It is broader than a feature hash and does not isolate
which outputs depend on a change.