Repository documentation

Moving from NVIDIA-dev/literate-ai

Literate AI is now published from jordanhubbard/literate-ai. The former NVIDIA-dev/literate-ai repository is archived and read-only. This page covers what existing users need to do; ADR 0049 records the design.

Installed CLI

Check how litai was installed with litai --version and litai doctor.

• Prefix install (make install) on 1.0.x: reinstall once from the public repository. Releases 1.0.x check only the old repository, and because it is not public they cannot download from it, so they never update on their own. Clone the public repository and run make install again with the same PREFIX:

  git clone https://github.com/jordanhubbard/literate-ai.git
  cd literate-ai
  make install PREFIX=/your/previous/prefix   # omit PREFIX if you used the default
  

  From 1.1.0 on, self-update checks the public repository.

• Pip or editable install: download the wheel from the latest release and install it with python -m pip install path/to/WHEEL.whl in the same environment.

• 1.1.0 or later: self-update follows the declared move automatically, even when the wheel was built from an old clone.

Projects initialized by an earlier release

Nothing in the project needs editing. .literate/initialization-origin.json keeps naming the repository that initialized it; that is provenance. litai update from a public-repository build recognizes the move and plans normally. A project initialized from any other repository is still refused with project.update_origin_changed.

Historical update recovery accepts GitHub's SCP spelling (git@github.com:owner/repository) and fetches it over the same SSH transport; recorded URLs keep their transport. It fetches from the recorded predecessor at the exact recorded commit and admits only bytes matching the baseline digest; it does not redirect historical recovery to the successor or rewrite initialization or catalog provenance. A historical locator it cannot use leaves the conflict for review.

As with every upgrade, a changed installed framework no longer matches the project's Standard pin. Plan, review and apply the rebind:

litai project lifecycle rebind-standard --project . --output rebind.json
litai project lifecycle rebind-standard rebind.json --project . --apply --authorize-rebind

The same reviewed path supports a retained project that already has a receipt policy but has no lifecycle driver. A distinct first-binding plan explicitly shows the absent previous binding and preserves all existing receipt requirements and the runner identity. Do not delete that policy to force initialization. First binding changes configuration only; native harness integration and fresh accepted execution remain required. Existing custom executable drivers refuse this route.

See Configuration and CLI reference for rebind details.

Clones of the literate-ai repository

The public repository has no shared history with the old one. Do not push old branches or tags to it.

git remote rename origin nvidia-dev          # keep the archived remote for reference
git remote add origin https://github.com/jordanhubbard/literate-ai.git
git fetch origin --tags --force              # replace old local release tags
git switch -C main origin/main

--force replaces local v* tags with the public historical markers. Each marker's README names the original release commit in the archived repository. Port unfinished work by committing its final tree onto origin/main, then run make public-export-check before pushing; see Public repository export.

Links in older documents

Issue, pull request, commit and CI-run links created before 2026-09-30 point at the archived repository and keep their original numbers. Issues that were still open moved to the public repository with new numbers; the work queue links to them.