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

# Contributing

Bug reports with a record, the evidence and the outcome you expected are the most useful contribution.

## Setup

Node >= 22, pnpm 11. `pnpm install --frozen-lockfile`, then `pnpm run typecheck`, `pnpm test`, `pnpm run build`. Network tests are opt-in: `pnpm test:live`.

## Rules that keep the tool honest

* Classification changes update `SPEC.md` and add a test that fails without the change. Expectations come from the protocol or the recorded evidence, never from running the engine and pasting its answer.
* A missing or unreadable input is never a pass and never a mismatch: it is `insufficient_evidence`.
* Never add a path where chain confirmation is described as a bank payout, or where an unsupported form becomes `matched`.
* Amounts are exact: strings in, bigint stroops inside. No floats.
* Read-only: no key handling, no signing, no transaction submission, no non-`GET` requests. Fixture tooling in `scripts/` may sign on testnet only.
* Generated files (`schema/`, `examples/`) are produced by `pnpm schema` and `pnpm examples`; CI fails when they are stale.
* Synthetic data is labelled synthetic. Do not add real customer data; redact first.
* Scripts under `scripts/` run with `node --experimental-strip-types`: no enums or parameter properties there.
* Commits: one logical unit each, conventional prefixes (`feat`, `fix`, `test`, `docs`, `build`, `ci`, `chore`). No AI co-author trailers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://stellar-developer-tools.gitbook.io/anchortrace-sdk/project/contributing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.