governance

Trust

Leji is built to need as little trust as possible. The specification, schemas, tooling, and fixtures are public, permissively licensed, and run on your own machine. Leji has a named corporate steward, and what protects you is not trust in that steward's intentions: everything here is openly licensed, runs without any steward service, requires no steward endpoint, permits competing implementations and commercial services, and can be forked.

Who maintains this

Leji was created by Vuong Nguyen and is stewarded by Contexing, LLC. GOVERNANCE.md records how decisions are made, how maintainership transfers, and which assets transfer with it. Contexing holds the Leji name. The specification, schemas, and tooling are permissively licensed and may be forked by anyone, under a different name.

Commercial products

Contexing, LLC, Leji's steward, is developing LejiAI, a hosted Leji viewer at leji.ai for teams whose members do not work in git. It is optional. No conformance level requires it, no part of the specification depends on it, and the reference tooling remains local, offline, and account-free. What the hosted viewer adds is infrastructure rather than format capability: authentication, per-person access control, and operated hosting. Independent commercial products built on Leji, including ones competing with ours, need no permission.

Steward-authored proposals that touch areas its products depend on are labeled as such and carry a longer comment period, in public, so "no conformance advantage" is something you can check rather than something we assert. See GOVERNANCE.md.

The versioning promise

The specification and schemas are on the 1.0 line, frozen at GA with the 1.3.0 reference-tooling release (recorded in the repository's decision log). Within the line, schema changes are additive only; any incompatible change ships as a new line, never in place. The reference tooling versions separately and declares which spec lines it supports. Full rules: versioning.

Language

leji.org is written in English; translated pages say so and invite corrections.

If the steward disappears

Everything required to continue without the steward is already public and licensed for it: the specification (CC-BY-4.0), the schemas and all reference tooling (Apache-2.0), and the shared fixture suite the three SDKs are tested against. Validation, scaffolding, and conformance run offline and report nothing back. A fork or an independent implementation needs no permission and loses no capability.

The name and the logo are what the licenses do not cover: both are trademarks with their own usage terms, and the logo asset files sit outside the licenses above. A fork keeps everything the licenses grant, the complete specification, schemas, SDKs, CLI, and fixture suite, and needs no permission. It needs a different name and its own infrastructure: domains, package registrations, and signing keys are operated assets, not licensed artifacts. What a fork may and may not call itself is written down in the trademark and usage policy.

Independent implementations

The reference SDKs are three independent codebases (TypeScript, Python, Go) held behaviorally identical by one shared fixture suite, which is the same suite an outside implementation can test against. Conformance is self-attested against the published checklist; there is no certification program and no commercial gate: every level is reachable with the open spec and reference tooling alone.

Security

The reference tooling runs on your machine: no telemetry, no account, and nothing to depend on beyond your own machine. Validation, scaffolding, and conformance work fully offline, schemas and templates ship inside each package, and Leji's own validation and scaffolding logic makes no network requests. Contexing, LLC, Leji's steward, is developing a hosted service at leji.ai; the reference tooling never contacts it.

The federation commands you invoke deliberately (leji mounts hydrate --fetch, leji mounts update-pin --fetch, and leji conformance --federation=verify) contact the repository you named and nothing else. leji start and the optional onboarding handoff launch the coding agent you already have, whose network behavior is its own.

This website is separate from the tooling: leji.org, as deployed by its steward, uses Fathom for aggregate traffic analytics; the site source ships with no analytics, and a deployment adds its own. Report a vulnerability through GitHub private vulnerability reporting or security@leji.org; the process is in SECURITY.md.

The change record

This repository runs the same context layer controls the spec asks of adopters: a reviewed changelog, a generated index, and decision records, including the preview-to-GA transition and the decision to build a commercial hosted viewer. Releases are recorded in CHANGELOG.md, with a machine mirror.