Two things have to be traceable before any capability claim means anything: where the method comes from, and which artefact produces the behaviour. Neither is held by this app, so each step below is published with what it owes and the carrier that is missing.
A bounded statement of what the method is for and where it stops being valid.
The construction itself, in a form an independent reader can check step by step.
Each prior result the construction relies on, named and recoverable.
What is new relative to the cited sources, stated narrowly enough to be wrong.
The artefact and version that implement the construction, so behaviour can be attributed.
A capability claim without an artefact and a version is a description of an intention. This estate keeps the four capability rows published even though every binding is missing, because removing them would hide the gap rather than close it.
BW Proof is an evidence estate, not a live BW runtime, not a certification, and not an independent audit. Nothing here substitutes for an examiner inspecting real artefacts.