Community · Contributors Program

Build the language in the open.

NEXORA is an independent, MIT-licensed project in an early phase. The Contributors Program is how individuals, teams and organizations take part in its design, implementation and verification, with clear standards and public decisions.

Read the documentation

Contribution tracks

Four ways to contribute

Each track has an owner area in the repository and its own acceptance checks.

Language core

Interpreter, type checker, contracts and diagnostics. Changes ship with tests and keep the specification and the examples in sync.

Python · pytest

Developer tools

The command line, the language server, the VS Code extension and the npm launcher.

Tooling

Documentation

Guides, the language reference, runnable examples and translations. Documentation is tested against the interpreter.

Docs

Research and verification

Evaluate whether explicit contracts and structured output really help people and tools. Publish methods, data and negative results.

Research

How it works

From proposal to release

A predictable path, so contributors and maintainers know what to expect.

Propose

Open an issue describing the problem. Language changes start from a written design decision, not from a patch.

Issue · ADR

Implement and verify

Follow the contributing guide. Linting, the full test suite and the coverage threshold must pass in continuous integration.

CI required

Review and release

A maintainer reviews the change. Accepted work is recorded in the changelog and released under semantic versioning.

Changelog

Standards

What every contributor can rely on

Open licence

The project is distributed under the MIT licence. Contributions are published under the same terms.

Code of conduct

A written code of conduct applies to every space of the project, with a private channel to report problems.

Security policy

Vulnerabilities are reported privately and handled under the published security policy, before any disclosure.

For organizations

Evaluating NEXORA, funding work on a track, or running a joint study on verifiable code and AI tooling? Open a discussion in the repository describing your scope. The project is early, and collaboration is agreed case by case in public.