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. One steward maintains them today, and every promise is recorded in a public repository artifact, not just asserted.

Who maintains this

Leji was created by Vuong Nguyen and is stewarded by Meteor Dreams, LLC. GOVERNANCE.md records how decisions are made, how maintainership transfers, and the intent to move to neutral, multi-party governance as adoption grows.

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.

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.

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 no Leji service to depend on. 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.

The federation commands you invoke deliberately (leji mounts hydrate --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 loads Fathom for aggregate traffic analytics. 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 itself. Releases are recorded in CHANGELOG.md, with a machine mirror.