← Back to the selection

Start from sources, not assumptions.

Stemmapyle

See what needs another look after a change.

Compare captured versions of source files and follow explicitly declared dependencies to see which deliverables may need another review.

Follow a source change

A shared script changes

Compare captured sources, follow the relationships you declare, and see where another review may be needed.

Supply the captured versions

Compare captured source packs. The comparison is bounded by the supplied material; it does not inspect everything installed on a machine.

Declare the relationships

Provide the dependencies and consumers you want to examine. The prototype follows those declared links, including downstream consumers, and shows the reason paths. Unresolved references remain visible. It does not discover a complete dependency graph for you.

Use the result to direct review

A declared direct or downstream consumer may need another review after a source change. That is a review signal, not proof of breakage or permission to repair anything.

Before you use the example

Does a review signal prove that something broke?

No. It identifies possible source impact through declared relationships. It does not prove breakage or authorize repair.

Does Stemmapyle discover every dependency?

No. It follows the relationships supplied with the captured material. Undeclared relationships are outside the comparison.

Can I use or download Stemmapyle now?

Not publicly. Stemmapyle remains a working offline prototype retained with the Pylotheke review tools. Live integrations are not verified.

01 / PURPOSE OF THE PROJECT

Purpose of the project

A view of declared direct and downstream relationships, with the paths that explain why a source change may require another review.

02 / WHAT EXISTS NOW

What exists now

A working offline prototype retained with the Pylotheke review tools. The project page explains an invented shared-script change. Not available for public use or download; live integrations remain unverified.

03 / SCOPE AND LIMITS

Scope and limits

Possible impact guides review; it does not prove breakage or authorize repair. Undeclared relationships are outside the comparison; it does not discover installed dependencies or complete the dependency graph.

WHO IT IS FOR

Teams updating documents, data or deliverables without losing the history of changes.