> ## Documentation Index
> Fetch the complete documentation index at: https://docs.svrnos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cite GER

> Citation formats, Zenodo DOI, license terms.

## Citing the registry as a whole

```
Nzeutem, S. (2026). SVRNOS Governance Error Register v0.2.
Sovereign OS LLC. https://svrnos.com/research/governance-error-register
```

## Citing an individual code

Every code page carries a ready-to-copy citation block. Example for GER-501:

```
SVRNOS. (2026). GER-501: Escalation Not Implemented.
SVRNOS Governance Error Register.
https://docs.svrnos.com/ger/codes/501
```

The URL itself is the canonical permalink. Citing the URL is sufficient — regulators, journalists, and researchers can resolve it without any further attribution mechanism.

## Zenodo DOI

GER v0.2 is archived on Zenodo with a versioned DOI. Each minor release gets its own DOI; the "all versions" DOI resolves to the latest.

<Card title="Zenodo record (forthcoming)" icon="archive" href="#">
  DOI will appear here when v0.2 archive lands. Subscribe to the [changelog](/ger/changelog) for the announcement.
</Card>

## License

* **Code definitions, names, distinct-from boundaries, tags, glossary, attributions** — CC BY 4.0
* **Documented event titles** — sourced from the [AI Incident Database](https://incidentdatabase.ai), CC BY-NC-SA 4.0. SVRNOS displays titles and links out for full narratives; we do not redistribute the corpus.

You may use the GER in any work — commercial or non-commercial — with attribution. A hyperlink to the relevant code page is sufficient attribution.

## What we ask in return

If you cite the GER in regulation, litigation, audit programs, insurance products, or training material, **tell us**: [hello@svrnos.com](mailto:hello@svrnos.com). We track adoption visibly on the changelog as a public signal that the registry is being used.

This is not a license condition. It's a request that helps the registry mature.