> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vexa.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Contributor rights

> Vexa's low-friction DCO path for individuals and head-bound authorization path for employer-owned contributions.

Vexa uses one conscious rights choice at pull-request intake and automates the remaining mechanics.
The canonical policy and operational commands live in
[`CONTRIBUTOR_RIGHTS.md`](https://github.com/Vexa-ai/vexa/blob/main/CONTRIBUTOR_RIGHTS.md).

| Path                       | Contributor action                                                      | Merge evidence                                                                   |
| -------------------------- | ----------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Independent                | Select the declaration and sign each commit with `git commit --signoff` | Declaration plus the required DCO check; no individual CLA                       |
| Employer/client-controlled | Select the corporate path and provide a legal/IP contact privately      | Individual DCO plus a private authorization receipt bound to the current PR head |
| Unsure                     | Select unsure as early as possible                                      | Rights review resolves the path before merge                                     |

Technical review may continue during rights review. A later push invalidates a corporate
verification, and only a designated verifier can bind a private receipt to the new head. Executed
agreements, signatures, addresses, and employment information never belong in public PR comments.

## Agent-assisted flow

Agents automate Git, not legal judgment. They ask the human to choose the path, check the
repository-local Git identity, use `--signoff` after authorization, identify failing commits by
SHA, and prepare safe remediation. They never select the declaration, sign for another person, or
rewrite/push history without explicit approval.

For the latest unsigned commit:

```bash theme={null}
git commit --amend --no-edit --signoff
git push --force-with-lease
```

Shared branches use the DCO App's individual remediation flow rather than third-party sign-off.

## Historical work

The gate is prospective. Earlier contributions are triaged by concrete risk instead of rewritten
or subjected to a blanket CLA campaign. Significant ambiguous work may receive a retrospective
attestation; corporate-directed work receives a contribution-specific corporate authorization;
material work that cannot be cleared is replaced or removed.