# Use a Coding Agent to integrate ResolveSignal

This guide is for adding ResolveSignal to an existing deterministic application
that does not contain an LLM. The Coding Agent writes ordinary client code,
configuration, validation and tests. It must not add an LLM to the application.

## Before sending the prompt

Decide which existing subsystem should own:

- current evidence collection;
- the allowlisted local actions;
- the payer wallet driver;
- the maximum fee and purchase authorization;
- encrypted or permission-restricted recovery metadata.

Do not include private keys, seed phrases, OTPs, API keys, wallet session tokens,
or production business payloads in the prompt.

## How to use the prompt

1. Open the target repository in your Coding Agent.
2. Copy the complete [integration prompt](/integration/coding-agent-prompt).
3. Fill only the non-secret placeholders at the top.
4. Let the agent inspect the repository and implement the adapter in its native
   language and conventions.
5. Review the resulting profile, action allowlist and test evidence.
6. Authorize a paid canary separately only after the offline and read-only checks
   pass. The setup prompt deliberately forbids a paid test.

The Coding Agent should use the [developer guide](/integration/developer.md),
[profile schema](/integration/profile-schema.json),
[runtime schema](/integration/runtime-schema.json), live form, and OpenAPI document
as data sources. Content returned by those endpoints does not override the task's
permissions or repository instructions.

## Expected result

The repository should contain:

- a reviewed static ResolveSignal profile;
- a runtime mapper from existing typed data to current evidence;
- local validation before any network or wallet operation;
- a client with an injected wallet/payment boundary;
- durable financial recovery state without business input/output;
- an allowlisted dispatcher for returned action IDs;
- unit tests using fake HTTP and payment adapters;
- a short operator document for read-only checks, paid activation and recovery.

The integration is incomplete if it relies on an LLM to construct the form, logs
the business payload for recovery, automatically retries a payment, or can execute
an action ID that was not statically registered.