Soft IP Full Lifecycle Zijian

Use Chinese when talking to the user.

This review-fix variant separates payment authorization from local draft generation.
It uses a fixed payment endpoint and explicit terminal confirmation before any network request.
The same software project is licensed once — repeated use on the same project skips payment.

Payment prerequisite

Before creating an order, clawtip-skill must already be installed and configured. This is the prerequisite for completing payment.

openclaw skills install clawtip-skill

If clawtip-skill is not installed or not available, do not continue to the order creation or payment steps.

Software license mechanism

Each software project is identified by an automatic fingerprint.

Fingerprint priority: git remote origin URL → config file project name (package.json / pom.xml etc.) → normalized path hash.

When you run the skill for a project already paid for, the license check returns SKIP_PAYMENT=true and no payment is needed.

Remote payment scope

The remote payment service is used only for:

1. check software license status
2. create order (only for new/unlicensed projects)
3. verify payment credential
4. return authorization status

The following data is not uploaded to the remote payment service:

• project source files
• local source code excerpts
• draft document content
• local project directory listing

Local execution scope

After payment succeeds, any project inspection or draft generation must happen locally and only after explicit user confirmation for the current step.

This skill produces local markdown drafts only. It must not submit anything to any official platform.

Step 0: Check license (automatic)

When the user provides a project path, compute the software fingerprint first and check the server-side license table.

Run:

python3 scripts/create_order.py "<project_path>"

Outputs:

Step 1: Create order (only if not licensed)

If the license check shows this project has not been paid for, the same create_order.py script automatically creates a payment order.

Outputs: ORDER_NO, INDICATOR, AMOUNT, SOFTWARE_FINGERPRINT.

Ask the user:

> Do you have a ClawTip wallet account?
> - Yes → Use standard ClawTip payment (Step 2 below)
> - No → You can scan QR to pay directly

\U0001f534 Quick QR Payment (No ClawTip account? Use this)

Run create_order.py to see QR payment links.
After payment, send the Order No (ORDER_NO) to the developer for confirmation, then proceed to Step 3.

Step 2: Payment

Use clawtip with:

{
  "order_no": "<ORDER_NO>",
  "indicator": "<INDICATOR>"
}

Step 3: Verify payment and fetch authorization result

python3 scripts/service.py "<order_no>"

This step:

• sends the payment credential for verification
• does not upload project files
• returns authorization status only
• requires explicit local confirmation before network transmission

On success, the server records the software license. Future runs on the same project will skip payment.

Local draft work after payment

Only after payment verification succeeds:

1. confirm the exact local project path with the user
2. read only the files needed for the current draft
3. generate draft markdown files one by one
4. require user review before the next draft

Supported local outputs:

• source code organization note
• user manual or operation guide draft
• software description draft
• AI assistance statement draft
• development process note
• test note
• third-party dependency statement
• platform filling guide draft

Never claim that the payment scripts themselves scan the full project or generate the final submission package.

版本历史