# Personal ERP AI and SSH worker instructions

Read `/.well-known/erp-operations.json` before creating or renewing ERP work.

1. Never infer a renewal from status=done alone.
2. For Logic Monitor contracts, record the renewed outcome in the source system and let its signed outbox create the next ERP cycle. Never clone it in ERP.
3. For a confirmed fixed 7-day traffic cycle, call `POST /api/operations/renewals/complete` with taskId, sourceKind=`traffic_fixed_7d`, cycleDays=7, renewalOutcome=`renewed`, and currentEnd.
4. Authentication is mandatory, including `dryRun=true`. Send the ERP token in `x-erp-token` or `Authorization: Bearer`. Never log or persist the token.
5. Keep previousServer and nextServer separate. previousServer is report/memo context only. Never copy previousServer into nextServer or an H-column next-server field.
6. Send nextServer and nextQuantity only when explicitly confirmed for the next cycle. Omitted values stay `미확정`.
7. Preserve weekend contractEnd/originalDueDate. Use the preceding Friday for dueDate/reminderDate/executionDate.
8. Unknown or manual cycle types require review. Do not guess cycle dates.