> For the complete documentation index, see [llms.txt](https://faction-os.gitbook.io/faction-os-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://faction-os.gitbook.io/faction-os-docs/contributing.md).

# Contributing to FactionOS

## Contributor License Agreement (CLA)

By submitting a pull request, issue, or any other contribution to this repository, you agree to the following terms:

1. **Copyright Assignment.** You hereby assign to Max aka Mosheh (@moshehbenavraham) all right, title, and interest — including all copyright — in and to your contribution. This assignment is irrevocable and applies worldwide.
2. **Original Work.** You represent that your contribution is your original work and that you have the full right to make this assignment. You represent that your contribution does not infringe any third-party intellectual property rights.
3. **No Compensation.** You acknowledge that you will receive no compensation for your contribution and that the copyright holder may use, license, sell, or otherwise exploit your contribution in any way, including in proprietary or commercial products.
4. **Moral Rights.** To the fullest extent permitted by law, you waive any moral rights you may have in your contribution.

**If you do not agree to these terms, do not submit a contribution.**

***

## Development Baseline

* Use Node.js 26.2.0 or newer for the core workspace.
* Use npm workspaces from the repository root.
* Consult the product PRD in `docs/PRD.md` and the UX PRD in `docs/PRD_UX.md` before changing product behavior.
* Treat historical extraction files as evidence only. Current behavior lives in source, specs, README files, and `docs/`.

## Branch Conventions

* `main` - production-ready history.
* `feature/*` - product or documentation features.
* `fix/*` - bug fixes.
* `docs/*` - documentation-only changes.

## Commit Style

Use conventional commit prefixes where practical:

* `feat:` for user-facing features.
* `fix:` for bug fixes.
* `docs:` for documentation.
* `refactor:` for behavior-preserving code changes.
* `test:` for test-only changes.
* `chore:` for tooling, dependency, and maintenance work.

## Local Checks

Run the relevant subset before opening a PR:

```bash
npm run format:check
npm run lint
npm run typecheck --workspaces --if-present
npm test
git diff --check
```

For documentation-only edits, `git diff --check` is the minimum required check.

## Pull Requests

1. Keep one logical change per PR.
2. Link the relevant spec, PRD section, issue, or documentation gap.
3. Update tests and docs when behavior changes.
4. Call out privacy, security, hosted-service, adapter, or media-provenance impact.
5. Do not delete historical artifacts until traceability and Phase 08 deletion gates say they are safe to remove.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://faction-os.gitbook.io/faction-os-docs/contributing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.