# AI Autonomy Map

This file defines what the AI operator can do alone in this workspace, and what requires external permission, accounts, or human approval.

## Updated Objective

The user wants the AI to earn money for itself, using wallet:

`0x97f55255875f300012282e94ae5246616ddbe9dd`

## What I Can Do Alone Here

Within this local workspace, I can keep producing monetizable assets and operating materials:

- Build static service pages and tools.
- Improve the CSV cleanup delivery workflow.
- Create portfolio samples from demo data.
- Generate platform-safe listing copy.
- Generate outreach, quote, delivery, and objection-handling scripts.
- Create evidence logs and revenue audit scripts.
- Verify local links, scripts, wallet references, and revenue evidence.
- Package the workspace so it is ready to publish when external access is available.
- Build `dist/ai-income-starter-kit/` as a ready-to-publish product package.

These actions move the earning system closer to being usable, but they do not by themselves collect money.

## What I Cannot Do Alone In This Environment

Without external authorization or account access, I cannot honestly claim to have earned money because I cannot:

- Create or operate freelance marketplace accounts.
- Publish gigs to Upwork, Fiverr, Contra, LinkedIn, WeChat, or other external platforms.
- Send messages to real prospects from your accounts.
- Accept contracts or platform terms on your behalf.
- Receive platform escrow.
- Check private bank, wallet, or exchange balances.
- Prove that a blockchain transaction belongs to a paid client unless evidence is added to `payment-evidence-log.csv`.
- Bypass marketplace payment rules.

## What Would Be Needed For Me To Act Externally

To let me do external earning work instead of only preparing assets, one of these must be provided:

- Approved browser/account access to publish a listing.
- A platform account where the user explicitly authorizes what I may post.
- A public static hosting target or repository for the portfolio.
- A real prospect list the user has permission to contact.
- Permission to send specific messages through an approved channel.
- Payment or escrow evidence after a real buyer pays.

Even with access, I should still follow platform rules, avoid spam, avoid fake claims, and avoid handling private keys or seed phrases.

## Current Completion Standard

The goal is not complete until there is verified revenue evidence.

Evidence must appear in `payment-evidence-log.csv` as a non-template row with:

- `collected_value_usd` greater than zero
- `platform_order_id`, `tx_hash_or_receipt`, or `proof_location`
- `status` showing paid, collected, confirmed, or escrow confirmed

Run:

```bash
npm run audit:revenue
```

If the audit says "No verified revenue yet," then the AI has not yet achieved the earning objective.

## Next Best AI-Only Work

Until external account access is available, the best AI-only work is:

1. Improve assets that increase conversion.
2. Improve tools that shorten delivery time.
3. Improve audits that prove real revenue.
4. Package a ready-to-publish portfolio with `npm run build:package`.
5. Prepare channel-specific listings that can be posted immediately once authorized.