Operations and contribution

Configuration

Keep secrets outside documentation and source control. Use .env.example as the public contract and store real values only in the designated local settings surface.

Testing

Run the repository checks listed in the quickstart. A passing narrow test does not prove unrelated interfaces or scientific claims.

Run the suite auth audit before presenting the adapter fleet as synchronized. A green audit means the policy files agree and forbidden material was not admitted; it is not a substitute for browser login testing in each application.

Troubleshooting

  1. Confirm the repository and branch.

  2. Reproduce with the smallest supported input.

  3. Capture the exact command and error.

  4. Check the documented runtime and lockfile.

  5. Open an issue with secret-free evidence.

Security and privacy

The gateway transports and validates requests; it does not convert model output into scientific authority.

Contributing

Read CONTRIBUTING.md, SECURITY.md, SAFETY.md, and the repository license when present. Keep changes bounded and include the checks that justify acceptance.

Releases

The current public documentation describes 0.1.0 with status local-api. Consult the repository history and release notes for changes.