Palynth engine v0.1: a live provenance experiment, verifiable in your browser — see it work
The solutions
The same graph answers all of these. What changes between them is the question being asked. Each one is labelled with what actually runs today.
01
A revision lands and nobody can say what scope it touched until somebody reads it against everything else.
What Palynth does
Traverse the graph from the changed asset and return every dependent artifact, with the reasoning attached to each.
02
What was ordered stops matching what was approved, and the mismatch surfaces at delivery.
What Palynth does
Compare the purchase record against the approved state of the same asset, and raise the conflict when it appears rather than when it arrives.
03
A submittal is approved against a design state that has since moved, and nothing records which state it was.
What Palynth does
Every submittal event references the asset state it was based on, so the question stays answerable later.
04
A decision in one discipline invalidates an assumption in another, and the two never meet.
What Palynth does
Typed relationships across disciplines make the dependency explicit before it becomes a clash.
05
The approved configuration is re-keyed into fabrication by hand, and drift enters silently.
What Palynth does
Carry the approved configuration and its provenance into fabrication as data rather than as a drawing.
06
What was installed is compared against what was approved by memory and photographs.
What Palynth does
Record installation as an event against the same asset, so the comparison becomes a query.
07
The owner receives a building and several thousand disconnected files.
What Palynth does
Hand over assets that carry their own decision history, verifiable after the software that produced it is gone.
Experimental means the mechanism exists and has been tested, and is not yet connected to a production pipeline. Roadmap means product direction, and nothing more.