> For the complete documentation index, see [llms.txt](https://slippay.gitbook.io/slippay-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://slippay.gitbook.io/slippay-docs/smart-contract-and-open-source/ai_disclosure.md).

# AI disclosure

The Open Track requires full disclosure of AI-generated or AI-assisted artifacts. This is that disclosure, written plainly.

## How AI was used

SlipPay is built by a two-person team (Manuel Galmanus, engineering; Mario, business/regulatory). Manuel uses AI coding assistants heavily and routinely — primarily Claude (via Claude Code) and an in-house agent ("Wave"). Disclosure by artifact type:

| Artifact                                                     | AI involvement                  | Human ownership                                                                                 |
| ------------------------------------------------------------ | ------------------------------- | ----------------------------------------------------------------------------------------------- |
| Soroban subscription contract (`lib.rs`)                     | AI-assisted drafting + review   | Every line read, tested, and audited by Manuel; 5/5 unit tests; F1–F8 audit fixes human-decided |
| Off-chain API (Deno/Hono)                                    | AI-assisted                     | Human-reviewed; security middleware human-specified                                             |
| Web app / landing                                            | AI-assisted (copy + components) | Design direction + copy decisions human                                                         |
| This application's prose                                     | AI-assisted drafting            | Facts human-verified against the repo before submission                                         |
| Architecture & regulatory positioning (BCB Res. 519/520/521) | Human (Mario + legal counsel)   | AI used only to summarize, not to decide                                                        |

## What is NOT AI-decided

* The regulatory strategy (Res. 561/519/520/521 compliance path, domestic dollarization positioning) is human + legal-counsel work.
* The decision of what to claim in this application: every factual claim was verified against the actual codebase before submission. Aspirational features (e.g. PYUSD support, the Pix-anchor integration) are labeled as roadmap, not as shipped — explicitly, to avoid AI-fluency masking gaps.

## Honesty note

We treat "AI-assisted" as the default state of the codebase, not an exception. The relevant question for a reviewer is not "did AI touch this" (it did, everywhere) but "is it verified and does it work on-chain" — which the mainnet deploy, matching Wasm hash, and passing tests answer directly.


---

# 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://slippay.gitbook.io/slippay-docs/smart-contract-and-open-source/ai_disclosure.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.