BBVP · Evidence · Trust
Build · Back · Verify · Prove

How Saami Salami Asl uses BBVP to build Elisence with evidence and proof

BBVP stands for Build, Back, Verify, Prove. It is the way Saami Salami Asl develops Elisence: not just by writing code or documents, but by backing every step with tests, evidence packs and clear proof of what works.

Build with intention Back with tests Verify behaviour Prove with evidence

This is not a legal framework. It is a practical, personal engineering discipline for digital health.

1 · Build

Design

In Elisence, “Build” means creating features, documents and flows with a clear purpose. Nothing is random or rushed:

Clear scope: Each feature has a defined role and boundary.
Simple UX: Normal people should be able to use it calmly.
Respect: Design respects families, clinicians and ministries equally.

2 · Back

Support

“Back” means every important change is supported by something solid behind it:

Notes & rationale: Why this change exists is written down.
Standards: Links to NHS, EU, GCC or other guidance where relevant.
Structure: Code and content follow repeatable patterns, not chaos.

3 · Verify

Testing

“Verify” is where ideas and code are actually checked. For Elisence, this includes:

Technical tests: Does the code run? Do endpoints behave as expected?
Safety checks: Does the system stay non-diagnostic and inside safe limits?
Consistency: Do results match the standards they claim to follow?

4 · Prove

Evidence

“Prove” is where everything is recorded so it can be shown later to ministries, investors or auditors:

Evidence packs: Bundles of tests, screenshots and logs kept together.
Versioning: Clear dates and versions so people know what they are looking at.
Honesty: If something is not finished, it is marked as “not done”, not hidden.

Why BBVP matters in Elisence

Trust

For a platform that aims to support ministries, hospitals and families, trust cannot be just words. BBVP is the way Saami Salami Asl turns that into daily practice—step by step, with proof.