Valence accepts mesh contributions through a review workflow. Contributors provide mesh bytes and metadata; maintainers decide whether the entry belongs in the registry. To start contributing, visit the mesh upload form.
What contributors provide
- A mesh file or supported boundary artifact.
- Domain and mesh metadata.
- Source, license, and rights declarations.
- Enough provenance for a maintainer to verify the mesh is authentic.
Accepted file formats
Valence imports mesh files in ADCIRC fort.14 (.14), Aquaveo SMS grid (.grd), and 2DM (.2dm) formats. A boundary-only artifact — an outline polygon with no element connectivity — is also valid upstream provenance when registered with kind: "boundary".
What Valence checks
The service can stage uploads, compute digests, run structural gates, detect duplicate content, and prepare a review record. Visual previews are illustrative; source mesh bytes and manifest metadata remain authoritative.
Automated validation includes digest computation to ensure mesh identity, structural gates to verify element and boundary integrity, duplicate detection across the registry, and an advisory scope verdict (L1) to flag potential scope-fitness issues.
Contribution lifecycle
After submission, a contribution moves through the following states: pending (initial ingestion), processing (running automated gates), needs_review (queued for maintainer review), approved (maintainer approved; registry pointer live and manifest commit queued), and published (entry committed to git and mesh discoverable on the registry). Contributions may also be rejected; if rejected, the contributor sees a reason and can resubmit.
Rights and licensing
Contributors warrant that they have the right to contribute their mesh to the registry. See License Compatibility & Redistribution Blockers on GitHub for the full licensing assessment and what redistribution rights are needed.
Provenance
Valence expects real-world mesh records to carry provenance. Until provenance enforcement is fully tightened, contributors should treat missing source information as a blocking review problem.
See Trust, Provenance & Authority Boundaries for how provenance fits the registry's authority model.