---
title: Licenses and credit
description: What VIABLE builds on, under which licenses, and how to credit it when you publish materials, papers or data.
updated: 2026-10-29
---

> All VIABLE docs, for people and their agents: https://developers.viablelab.org/llms.txt

# Licenses and credit

VIABLE builds on open research and open data. This page lists what it uses, under which license, and what to credit when you share a course, a paper or a dataset made with it.

## What VIABLE builds on

| Resource | What VIABLE uses it for | License |
| --- | --- | --- |
| [Learning Commons Knowledge Graph](/docs/resources/learning-commons) | Standards, what they break into, and the standards before them | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) |
| [Eedi Misconceptions Graph v1.0](/docs/resources/learning-commons), (c) 2026 Eedi Ltd., via Learning Commons | Math misconceptions to listen for, and the skills they hinder | [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/) |
| [VETTING](https://github.com/hichipli/vetting-python) | Checking each reply against rules and an answer key | MIT (reference implementation) |
| [The VIABLE CLI and its Agent Skill](/docs/project/cli) | Your own AI doing project work as you | MIT |
| Research methods in the export | How each measure is computed | Cited in `data_dictionary.csv` |

## Where the credit already appears

You don't have to add attribution inside VIABLE. It is already there:

- **In the activity editor**, beside every standard, with the date it was retrieved, and under the misconceptions.
- **In the activity's version**, which keeps each standard's and misconception's source, license and attribution.
- **In the research export.** `manifest.json` keeps each activity version's settings, standard and misconceptions included. When a version used them, `README.md` says how to credit them.
- **In the data dictionary**, measures name the papers they come from.

## When you publish

::: steps
1. **Materials with a standard's or a misconception's text.** Add a line such as: "Standards from the Learning Commons Knowledge Graph, CC BY 4.0." or "Misconceptions from the Eedi Misconceptions Graph v1.0, (c) 2026 Eedi Ltd., via Learning Commons, CC BY 4.0."
2. **A paper about an agent that uses VETTING.** Cite the [VETTING study](https://doi.org/10.1016/j.caeai.2026.100646).
3. **A dataset from the research export.** Keep `README.md`, `manifest.json` and `data_dictionary.csv` with it, so others know what each column means and where it comes from.
:::

> [!NOTE]
> Learners' data isn't open data. Share an export only as your approval and your consent form allow. Learners appear in it by pseudonymous codes, never by name.

## Your own materials and the models

What you and your learners put into VIABLE is covered by VIABLE's [Terms of Service](https://www.viablelab.org/terms-of-service) and [Privacy Policy](https://www.viablelab.org/privacy-policy). Replies come from the model you choose, and that model's provider sets its own usage terms. [Models](/models) lists each provider.

When a question set or a knowledge base holds someone else's material, its license still applies. Keep its credit with it, for example in the question set's description or the document itself.

::: cards
- [Learning Commons](/docs/resources/learning-commons): what VIABLE takes from it, when, and what it keeps.
- [The research export](/docs/research/export): the files, their documentation and how to cite what learners saw.
:::