Skip to content

Licensing and provenance

Four documents answer every licensing question about this repository:

  • LICENSE — the MIT license, one holder line: Copyright (c) 2026 Nick Burkard.
  • NOTICE — the distribution boundary record: it names each third-party component, its license, the pinned commit its files came from, and the path of the text that ships with it.
  • THIRD_PARTY_NOTICES.md — the prose provenance narrative behind those components.
  • tools/license_manifest.json — the machine-readable inventory: every tracked file assigned to exactly one license family, with its category, SPDX id, holder, provenance notes and how its legal text travels through the install prefix and the tutorial archives.

The manifest is the only exception source. Neither the checker nor the packers carry their own allowlist, so a change to a legal text or a new vendored file is recorded there or the check fails.

The five categories

Every tracked file is classified by origin, and the license that applies follows from the origin — never from the fact that the file sits in this repository.

Category Meaning What the license does
original authored by the project the root MIT license applies
derived built from a named upstream source the upstream terms keep applying
bundled third-party material carried in the tree or shipped in an artifact its own terms travel with it
generated machine output of a checked-in generator or an external tool origin only: the grant comes from the generator and its inputs
unresolved no provenance evidence in the repository no grant at all until an owner records an origin

The partition assigns every tracked file to exactly one family, with nothing unassigned and nothing double-assigned, and nothing in the unresolved category. A path belongs to the family with the lowest precedence number whose globs match it, after that family's carve-outs; a path matching nothing falls to the precedence-6 fallback, which a passing partition never reaches. The checker re-derives that partition from the files git tracks and reports the derived sizes; it never compares them against a recorded count, so adding a file does not stale the check: a file staged with git add is in that tree, so a new file must be classified before it can reach a commit, while a dependency tree such as an OpenUSD build a CI job stages inside the checkout, a build archive it downloads into the checkout root, a nested checkout or an uncommitted scratch file sit outside it and are reported as excluded rather than counted.

Generated is an origin class, not a grant

Three families are machine output, and a missing header in them is not a violation:

  • libs/rigExecBinary/generated/** — flatc headers generated from the RigExec schemas. FlatBuffers itself is Apache-2.0; the generated headers inherit nothing beyond what FlatBuffers' license says about output.
  • plugin/rigExecSchema/resources/** — generated schema resources that carry inherited upstream schema documentation text.
  • docs/nodes/** and docs/index.md — generated by docs/build_pages.py from libs/rigExecSchema/schema.usda and docs/operator_notes.py, both project-authored, so these pages are MIT. Never hand-edit them; edit the notes and regenerate.

So "generated" tells you where the bytes came from. It never tells you who granted rights, and it never converts inherited content into MIT.

What the MIT license verifiably covers

The MIT grant is asserted for project-authored material: libs/**, python/**, plugin/**, tests/**, bin/**, cmake/**, tools/**, CMakeLists.txt, justfile, the CI configuration, .clang-format, docs/requirements.txt, mkdocs.yml, the handwritten documentation, skills/**, the example generator scripts and the example README files, the project art families below, and the legal records themselves — minus the carve-outs below: the OpenUSD- and Epic-derived kernels, plugin/usdNoodles/**, the generated schema resources, and the Squarebit Eye shader in examples/biped/shaders.

Five files carry their own MIT header rather than relying on the root LICENSE: plugin/rigExecUsdview/profilerModel.py, plugin/rigExecUsdview/profilerUI.py, plugin/rigExecUsdview/execStackUI.py, asset_lib/components/compose.py and asset_lib/components/test_components.py. They name the same holder.

One caveat the manifest records explicitly: coverage is verified as project authorship, not as a settled chain of title. LICENSE and NOTICE name a single holder while the git history carries commits authored under other names. Until an owner records whether a contributor assignment keeps sole copyright, no tool should read the MIT grant as confirming more than that.

Third-party terms that are preserved

Component Holder License Where the text lives Pin
OpenUSD Pixar TOST-1.0 upstream, openusd.org/license; a copy ships as plugin/usdNoodles/LICENSE.txt 26.08
plugin/usdNoodles editor Meta Platforms (Pixar for moduleDeps.cpp) TOST-1.0 plugin/usdNoodles/LICENSE.txt OpenUSD PR 4156 at 4b753359d308d7d0416dcee464e1c7d130bc39dc
noodles GLSL shaders Meta Platforms MIT plugin/usdNoodles/NOODLES_LICENSE.txt ff5d473f10e8c37ceaf0da11ea7cb80805bc8314
Poppins font atlases The Poppins Project Authors OFL-1.1 plugin/usdNoodles/THIRD_PARTY_LICENSES.txt, installed under share/rigExec/plugin/usdNoodles/ same pin
thirdparty/flatbuffers Google LLC Apache-2.0 thirdparty/flatbuffers/LICENSE tag v25.12.19, commit 7e163021e59cca4f8e1e35a7c828b5c6b7915953
thirdparty/lzma Igor Pavlov public domain — no SPDX id thirdparty/lzma/DOC/lzma-sdk.txt, provenance in thirdparty/lzma/NOTICE.md 26.04
OpenRigLogic ports Epic Games, Inc. MIT quoted in the installed THIRD_PARTY_NOTICES.md; no separate text file, no header in the three port files 9ca65ac08b64a1ea5f0d79466e64706b3ac524ba
Squarebit Eye shader Squarebit LLC (Squarebit Studios) Squarebit Eye EULA URL only, squarebitstudios.com/squarebit-eye/eula —
libs/rigExecRuntime/runtimeMath.h Pixar TOST-1.0 header notice, upstream license link —
plugin/rigExecUsdview/volumeWeightUI.py Pixar OpenUSD terms existing header notice —

A public citation is not a license. The methods in Method references identify techniques RigExec implements; a reference to a paper grants nothing, and the harmonics constraint is reimplemented from a description because that repository states no license.

The art families the owner answers for

Six families were inventoried with no provenance evidence and stayed unresolved until the owner answered: the art in this repository is unique to the project, so it is MIT like the code (original-* families in the manifest, and the answered entries in owner_questions):

Family Paths What the owner answered
original-icon-atlas icons/** project-drawn art under MIT
original-usdview-icons plugin/rigExecUsdview/icons/** project-drawn art under MIT; the TOST terms of the plugin code around them say nothing about the images
original-component-library asset_lib/** project work under MIT
original-example-assets examples/** the biped geometry, the bust and rubberhose artwork and its textures are unique project art under MIT
original-doc-assets docs/examples/**, docs/images/**, docs/gifs/**, docs/assets/**, docs/*.svg project captures and tutorial stages under MIT
original-test-fixtures tests/fixtures/** project MIT; rigLogicReference.inc holds values upstream OpenRigLogic produced, and that upstream is MIT itself, so no separate grant is needed

The recorded evidence for these six is the owner's statement, not an independent chain of title; the copyright-holder question in owner_questions stays open for that reason. Two facts survive the answer: examples/biped/shaders/sbe_eye.glslfx is carved out to squarebit-eye-shader and keeps the Squarebit Eye EULA, because purchased third-party art is not ours to relicense, and the two icon families still ship into installed resources with no notice beside them — the root MIT covers them, but an installed consumer sees nothing. That is the concrete distribution gap the manifest's gaps records.

Install prefix. The legal root is share/rigExec. It carries the three root records, the manifest and the checker beside it under share/rigExec/tools, together with legal_members.py, the member reader the checker imports so an installed consumer runs it without a checkout; renamed aliases under share/rigExec/licenses (OpenUSD-LICENSE.txt, FlatBuffers-LICENSE.txt, LZMA-SDK-NOTICE.md, LZMA-SDK-LICENSE.txt); and source-relative copies under share/rigExec/thirdparty/... and share/rigExec/plugin/usdNoodles/... so that the links written in THIRD_PARTY_NOTICES.md resolve in the installed tree. The usdview texts ship whether or not RIGEXEC_BUILD_USDNOODLES built the editor.

No separate installed file exists for the Epic MIT text: it travels inside the installed notice. The Squarebit EULA is not installed and not checked in, and the two prose references below are deliberately left out.

Tutorial archives. Legal text sits at the archive root and under the source-relative paths the notice links to. docs/examples/usdview_rolling_ball.zip holds 14 legal members: root LICENSE, NOTICE, THIRD_PARTY_NOTICES.md, the source-relative copies of the FlatBuffers, LZMA and usdNoodles texts, tools/license_manifest.json, plus the historical aliases LICENSE-usdRig, NOTICE-usdRig, LICENSE-OpenUSD and THIRD_PARTY_NOTICES-usdRig.md left in place for existing consumers. Archive members are stored with CRLF endings, so a comparison normalizes CRLF to LF before flagging anything; drift from the source is an error and a line-ending difference is not. Every mapped member whose source resolves here is compared, whatever its status prose records. Two boundaries are recorded rather than inferred: the shipped tools/license_manifest.json copy is a provenance snapshot checked for presence and shape only, and a member whose entry records a stale exception is checked to still differ from its source, so a refreshed archive sends the record back for a refresh. Add-on-bound members are compared once --addon-root supplies their tree. A notice is validated where it sits: the links in a copy that travels under an archive root, such as godot_rigExec/THIRD_PARTY_NOTICES.md, must each reach a member of that directory.

USDZ examples. examples/biped/Biped.usdz and examples/2d/rubberhose/rubberhose.usdz carry no legal member at all today: they are payload-only archives, and the Squarebit Eye shader travels inside the biped archive with nothing but the URL in the notice.

Source-only prose references

THIRD_PARTY_NOTICES.md links files that are deliberately not legal texts and are not vendored as such:

The checker also names tools/check_licenses.py as a source-only tool reference: it is installed with the binaries, but it is a tool, not a legal text, and it is not a member of the tutorial archives. Each of these is recorded under prose_references so a missing archive member is not silently read as a missing license.

Checking it yourself

The checker is stdlib-only, so it needs no OpenUSD build:

python3 tools/check_licenses.py                 # audit the checkout
python3 tools/check_licenses.py --install /path/to/rigexec-install
python3 tools/check_licenses.py --archive docs/examples/usdview_rolling_ball.zip
python3 tools/check_licenses.py --self-test     # synthetic fixtures, no checkout needed
python3 tools/check_licenses.py --addon-root ../godot_rigExec

--install accepts a normal prefix, a DESTDIR staging tree and a relocated legal root. --quiet suppresses the per-member notes. In CTest the same checks run as testRigExecLicenseManifest (the checkout audit) and testRigExecLicenseChecker (its synthetic fixtures), both labelled fast:

ctest --test-dir build -R '^testRigExec(LicenseManifest|LicenseChecker|LegalPackaging)$'

testRigExecLegalPackaging covers the packers in docs/legal_members.py that write those members. The checker never hashes the manifest itself: the manifest's own bytes change whenever the inventory is refreshed, so inside an archive it is checked for presence, schema version and family-count shape only.

One limit is stated rather than papered over: the partition is re-derived from the checkout's git file list. In a tree with no git — an extracted archive, a vendored copy — the checker reports the partition as unverifiable instead of passing. Source headers are compared the same way: a header whose SPDX id or holder contradicts its family is an error for an owner to resolve, and the checker never edits a header or a family to make one agree.

What is still unverified here

  • The Godot tutorial archive is packaged from a sibling checkout at ../godot_rigExec that this repository does not track. Of its 27 mapped legal members, 18 are packed and 9 are recorded only: seven come from that add-on tree and two are texts this checkout supplies, so none of them can be written until the archive is rebuilt. Its copies of NOTICE and THIRD_PARTY_NOTICES.md predate the current files. Without an authorized add-on checkout there is no way to rebuild or validate that archive in this checkout, so those members stay recorded as stale or add-on-bound and the packer run for it is not a passing check here.
  • The Squarebit Eye EULA exists only as a URL; no text is checked in, and the biped USDZ carries none.