Samchil

SVS

How Samchil verifies software

SVS explains the evidence required for Verified, Trusted, and Proven software assets.

SVSEvidence-backed verification standard
3 levelsVerified, Trusted, and Proven
Current stateBadges can change when evidence changes
Explore modules

Evidence

Verification pipeline

The module journey starts with verification philosophy, then evidence, then module evaluation.

01
Candidate asset

Candidate asset

A reusable module, boilerplate, plugin, CLI, SDK, library, or small product is selected for review.

No product is treated as ready from marketing copy alone.

02
Evidence collection

Evidence collection

Build, lint, type check, tests, documentation, packaging, examples, compatibility, and security basics are reviewed where applicable.

Missing evidence stays visible instead of being hidden.

03
Owner review

Owner review

The owner assigns only the lowest SVS level fully supported by the available evidence.

Badge publication requires human review before customer-facing use.

04
Buyer decision

Buyer decision

The buyer sees the badge level, supporting evidence, and known limitations before relying on the asset.

SVS informs review; it does not replace production validation.

Levels

Verification badge levels

SVS levels describe what kind of evidence is currently available. They do not certify legal compliance, security, or bug-free operation.

Verified

Verified

Evidence
Minimum build, test, documentation, packaging, and example evidence is present.
Boundary
Does not mean the asset is proven in production.
Trusted

Trusted

Evidence
Verified evidence plus integration, stability, performance, security, and developer-experience review.
Boundary
Does not mean every environment or use case is covered.
Proven

Proven

Evidence
Trusted evidence plus operating, reliability, maintenance, and history evidence.
Boundary
Never claimed without operating evidence.

Limitations

What SVS does not guarantee

SVS does not guarantee bug-free software, legal compliance, security certification, all-environment compatibility, or suitability for every use case.