guide

Your repo, agent-ready in two commands.

The badge that most likely brought you here marks a repository whose context layer an agent can boot from, validated and scored on the maintainer's own machine and self-attested. Making your own repo agent-ready takes the two commands below.

What the badge attests ↓

01 · Install the CLI

npm install -g @leji-org/leji

02 · Enter the context layer

leji start

No context layer in the repository yet? The quickstart walks the fuller path, from adopting an existing repo to scoring the level it claims.

What just happened

  • Your agent opened in the context layer and read the boot profile first, so its first context is the team's rather than whatever it inferred from the tree.
  • Validation and conformance scoring run from the package you just installed, on your own machine, with no service in the loop.
  • The tooling opens no connection of its own, and there is no account, no registry and no hosted service behind it. What reaches the network, you invoke yourself: the federation fetches contact the repository you named, and the dependency step at leji init runs your own package manager on your explicit yes. The agent leji launches is the one you already run, with its own network behavior.

What the badge attests

The badge is generated locally: leji badge scores the repository with leji conformance, writes the SVG for the level that offline run verified, and prints one markdown line that embeds it.

leji badge

For a context layer verified at the governed level, the badge is this:

Leji 1.0 · governed · self-attested Leji 1.0 governed

The markdown line that embeds it in a README:

[![Leji 1.0 · governed · self-attested](leji-badge.svg)](https://leji.org/agent-ready/)

The levels are core, indexed, governed and federated, each containing the one before it. The conformance checklist says what each level asks of a team, and every one of them is reachable with the open specification and the reference tooling alone.

So the thing to read is the check, not the picture: run leji conformance in the same repository and see what it reports. Trust covers who maintains Leji, what the 1.0 line promises, and what happens if the steward disappears.