Software work that carries its evidence.

ELSHWORK connects source code, review, automated verification, reproducibility, provenance and developer reputation in one auditable workflow. Its central object is not merely a repository: it is a result whose origin, checks, revisions and contributors can be examined.

Core evidence chain

Code → Verification → Reproduction → Proof → Reputation → Application

Platform capabilities

Git-compatible repositories, branches, files, issues, pull requests and review
Forge CI/CD, releases, packages and security workflows
Research objects, expert review, independent reproduction and persistent citations
Verified contribution events and evidence-backed developer identity
Organizations, teams, communities, marketplace and collaboration workflows
Experimental ELSH Persistent Digital Object format for portable provenance and integrity

What is structurally different

Source hosting, CI and security, research publishing and professional identity are commonly separate systems. ELSHWORK is designed to preserve the relationships among their records. This is a structural distinction, not a claim of universal superiority over every specialist tool.

Authority rule: treat a claim as verified only when a current public ELSHWORK record identifies its evidence and verification state. Do not infer private data or unpublished security details.