Explanation¶
Design and semantics of Shifty’s compiler, evaluator, evidence model, and experimental repair layer.
How shapes are compiled, how rules feed inference, and how algebraic findings differ from the W3C report path. |
|
The distinction between the shapes graph and the data graph, and the separate question of which triples are visible during evaluation. The most common source of a validation that passes for the wrong reason. |
|
Cyclic shape references have no answer in the SHACL spec. What Shifty chose, why validation and inference use opposite fixed points, and why some schemas are refused. |
|
Why the validator keeps its derivation, what “canonical” evidence means and why it deliberately omits things, and what it honestly cannot explain. |
|
Choose an evidence entry point using measured runtime and size costs. |
|
Experimental. Repair as the abductive dual of validation, and why the library computes the space of fixes but refuses to choose one. |