Octaryn Engine
Verified access. Private rights.

Octaryn Engine uses a verified private-source contributor flow.

This site now does only two jobs: explain the project at a glance and send contributors to the verified intake flow. The private code repos become visible only after maintainer approval, and the private contributor records live in the private intake repo.

Open Intake Read Public Terms
octaryn-core + octaryn-editor Private response log GitHub OAuth Private backup repo
1. Read

Review the public intake summaries and contributor terms.

2. Intake

Complete the verified contributor intake flow.

3. Use the same account

Later PRs should come from the same GitHub account used for intake.

4. Submit PRs

Maintainers review PRs only after intake is on file.

Where things live

  • `octaryn-engine`: public workspace repo, legal docs, issue templates, and PR workflow.
  • `octaryn-core` and `octaryn-editor`: private code repos granted only after maintainer approval.
  • `octaryn-engine-site`: this minimal website.
  • Google Apps Script plus the private intake repo: verified contributor records and approval state.

What to do next

  • Read the public summaries on the intake page.
  • Complete the verified intake flow.
  • Wait for approval, then accept access and submit focused PRs.

Essential links

Public terms

Read the public summaries for license, contribution rules, and assignment terms.

 Contributor intake

GitHub-verified private intake required before a first substantive PR.

 How to contribute

Short intake and PR workflow for contributors.

 Assignment summary

Review the public summary of the contributor assignment terms.