ConstCheck a lineage against the identities its host graphs actually publish.
Self-consistency is not enough: a lineage annotates ids it does not own, so a renamed wall leaves a phase plan quietly talking about nothing. The caller hands over every stable id its graphs publish, which is why this stays a separate function; binding lineage to one named graph would make it useless to the next fold that lands.
A host id absent from the lineage is not an error. Lineage is additive, and a production may phase one wing and leave the rest unannotated. The refusals run the other way: a declared subject that resolves to nothing, and a derived artifact id that squats on a design identity.
Ids are compared exactly. Findings are returned with $input.subjects[i].id
or $input.derived[i].id paths and nothing throws; the lineage's own
consistency is validateDesignLineage's to check.
Every stable id the host graphs publish, in any order, duplicates allowed.
Lineage whose subjects and derived ids are checked.
Success, or every violation found.
Check a lineage against the identities its host graphs actually publish.
Self-consistency is not enough: a lineage annotates ids it does not own, so a renamed wall leaves a phase plan quietly talking about nothing. The caller hands over every stable id its graphs publish, which is why this stays a separate function; binding lineage to one named graph would make it useless to the next fold that lands.
A host id absent from the lineage is not an error. Lineage is additive, and a production may phase one wing and leave the rest unannotated. The refusals run the other way: a declared subject that resolves to nothing, and a derived artifact id that squats on a design identity.
Ids are compared exactly. Findings are returned with
$input.subjects[i].idor$input.derived[i].idpaths and nothing throws; the lineage's own consistency is validateDesignLineage's to check.