Optional registration

Add a graph to the registry

Your meaning graph can live in your own public Git repository and be referenced directly. Registering it is optional; the registry adds discovery, pinned provenance and connections to ModelSpec and the OpenVaultDB Directory.

OptionalGit-backedNo MeaningGraph account

Registration does not require publishing your graph to MeaningGraph or hosting it here. Keep the graph in your repository, then add a record to the public registry if you want it to be easier to find and reuse.

Contribution steps

Register a repository

Add graphs/$records/<id>.yaml to the MeaningGraph registry, with the repository URL, full 40-character commit, meaning-file paths and the SPDX licence for those files. List ModelSpec model files and their licence when the meanings bind to a model.
Add dependency records under dependencies/$records/ for the registered graphs your meanings reference. Add a maintainer record under maintainers/$records/ when the maintainer is new to the registry.
From the registry checkout, run npm ci && npm run index, then ingitdb validate and npm run check. The checks validate the full commit, paths, licences, meanings and dependencies.
Open a GitHub pull request with the graph record, any needed dependency or maintainer records, and regenerated index.json. This uses your GitHub account; no MeaningGraph account or hosted publishing is required. See the authoritative registration instructions and submit a registry pull request.

Keep control of your data

Registration is separate from a local draft

A downloaded local draft is for editing and previewing on your own machine. It does not submit a registry record. Registration happens only when you contribute the record and its supporting files to the registry repository.

Open the MeaningGraph registry