Development

Extend CodeNib through its shared registries and contracts, verify the changed surface at the right test tier, and keep evaluation artifacts reproducible.

• Extend

  Contribute a language

  Add chunking and graph capabilities through the language registry, then promote each backend only after its contract checks pass.

  Follow the language workflow →

• Verify

  CI/CD

  Choose among unit, integration, serial, graph-consumer, core, and slow verification tiers.

  Run the right checks →

• Publish

  Releasing

  Build and inspect distributions, run install smoke tests, and publish a release without bypassing artifact checks.

  Prepare a release →

• Storage

  Local workspace provider

  Publish a validated missing-directory generation through the Linux native ownership boundary and manage its caller-owned receipt lifecycle.

  Use the local provider →

• Measure

  Benchmarks

  Run the evaluation harnesses, prepare benchmark inputs, and package reproducible result bundles.

  Open Benchmarks →

Project contracts

Use Naming for project and package terminology. Evaluation inputs and outputs have their own reproducibility contracts; read Harnesses and metrics before running them.