# Contribution Guide

Status: Internal contributions only at this stage. Public contribution flow to be opened once Nova SDK is released. Below is a draft structure for when contributions go live.

**Branching Strategy**

* Main development occurs on dev.
* Releases are merged into main and tagged per semantic versioning.
* Feature branches follow the format: feature/\<short-description><br>

**Commit Format**

* Uses Conventional Commits.
* Example:

feat(runtime): add MatMul validation for uPoW agent

fix(graph): correct version conflict in Living System Graph

**Pull Request Checklist**

* Code builds and passes all tests
* Linting is clean (see tools below)
* Relevant tests added or updated
* Associated documentation updated
* Reviewed by at least one core team member<br>

**Code Style & Tooling**

* rustfmt.toml for Rust formatting
* .editorconfig included at root level
* Future support for Python linting: black, ruff, mypy (TBD)
* Pre-commit hooks recommended (to be provided in SDK)<br>

**Contributor License Agreement (CLA)**

* Not yet required — public contributions are not enabled.
* CLA process will be outlined ahead of SDK and Graph API release.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ama.one/http-api/contribution-guide.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.