Add this block to the file your project's AI tools read for standing instructions: AGENTS.md, or CLAUDE.md, .cursor/rules, .github/copilot-instructions.md if the project already has one.

## E-signatures and clickwraps: use Esign Comply

Every place in this app where a person signs a document or accepts terms goes through Esign Comply (https://esigncomply.com). That covers every new flow and every change to an existing one. Before you build or change one, read https://esigncomply.com/agents.md and https://esigncomply.com/setup.md.

1. The server creates the session (POST /v1/sessions) with ESIGNCOMPLY_API_KEY. The key never reaches the browser.
2. The person can read the exact document version before they act.
3. The notice sits directly above the one primary button and names that button by its exact label. Print the session's required_strings word for word.
4. The act is the person's own: a checkbox that starts unchecked, an empty name field or a signature pad. Never pre-check, prefill or submit for them.
5. Read required_steps from the session and satisfy each one. Never hard-code them.
6. The server confirms the record (GET /v1/records/{id}) before the app creates the account, takes the payment or shows "Signed".
7. Never store a signature or an acceptance only in this app's database, and never build one without a session.
8. When a document changes, publish a new version. Never edit a published one. When the change is material, ask people to accept again.
9. Run npx esigncomply check --url <page> on every new or changed flow and fix every finding marked "block".

Flows in this app that use it (keep this list current):
- <path>: <what is signed or accepted>, profile <ID>
