---
name: work-report
description: Report PaysForItself work by task, including effort, money currently at stake, expenses and realized/unrealized profit or loss. Use for progress or earnings reports, after the first day of ongoing work, and for weekly reporting.
---

# Report the work and its results

Give the user an evidence-based report of what the agent did, what remains at risk and what it earned
or lost. Read local task logs, artifacts and public wallet/position state. Reporting never signs,
spends, submits an entry, changes a trading strategy or creates a new wallet. It does not need funding.
Keep reports and bookkeeping in the working repository, outside source control and the public website.

## Start tracking with the first task

At the first actual opportunity work, record `work_started_at` in UTC in `run/reporting.json` and
preserve it across sessions. Installing the kit or creating the wallet alone is not the start of
earning work. Maintain `run/work-log.jsonl` using [the ledger conventions](references/ledger.md),
or adapt existing compatible logs without deleting them. Record effort at task boundaries, including
research, drafting, case preparation, submission, execution and follow-up. Use measured durations,
token usage and billed compute costs when available; distinguish estimates and unavailable values.

Use existing trading `fills.json`, `review.json`, transaction receipts, registry deposits and prize
entry/payment records as sources. Deduplicate the same event by transaction hash/log index or stable
record ID. Preserve a source reference for each financial figure. Do not read credentials, keystores,
unlock material, authenticated RPC URLs or private environment dumps for a report.

## Report when requested, after day one, and weekly

- **On request:** produce a report immediately, including incomplete work and unknown values. Do not
  wait for a payout, resolved market, funded wallet or scheduled date. Honor a requested period; otherwise
  report since the previous delivered report and include cumulative totals since work began.
- **First day:** deliver once at `work_started_at + 24 hours`.
- **Weekly:** deliver at `work_started_at + 7 days`, then every seven days on that original cadence.
  A manual report or a restarted session does not postpone these deadlines. Day one and week one are
  separate reports; do not start the weekly clock from the day-one report.

When an on-request report coincides with an automatic deadline, include the full due period and deliver
one combined report labelled requested/day-one or requested/weekly. It satisfies that due delivery only
after it is shown; update the corresponding marker and next due date on the original cadence. An earlier
manual report or one that does not cover the due period does not satisfy the automatic report.

For ongoing work, use the environment's documented scheduling tools to register one first-day follow-up
and one recurring weekly report, delivering to the current user's work thread. In Codex, use thread
heartbeat automations for thread follow-ups; preserve an existing matching schedule rather than duplicating
it. Store real schedule IDs, next due dates, `day_one_reported_at` and `last_weekly_reported_at` in
`run/reporting.json` only after registration/delivery succeeds. Reporting jobs are read-only: tell them
to read this skill and the repository's public work records, refresh permitted public balances/positions,
produce the due report, and update only reporting state. They receive no signer or spending authority.
Respect any existing scheduler/account isolation rules in the working repository. Send no email or other
external message unless the human separately requested that destination.

If a scheduler is unavailable or a required scheduling condition is unmet, explain that automatic
delivery is not configured, preserve due dates locally, and produce overdue reports when work resumes.
Do not claim future delivery is guaranteed or block useful task work on scheduling. Report at most one
combined catch-up for missed periods, with the coverage stated; do not flood the user with duplicates.

## Reconcile effort, exposure and results

For each task and the portfolio, show:

1. **Effort:** active time, useful work/artifacts completed, model/token usage and paid compute cost
   where observable. Separate measured, estimated and unknown figures. Sum per-task effort as effort,
   not elapsed wall time; concurrent tasks can overlap. Avoid counting the same shared research twice.
2. **Money at stake now:** remaining cost basis of open positions, refundable deposits/stakes currently
   locked, and other committed recoverable principal. Show asset, chain, task, verification block/time
   and release/settlement condition. Idle wallet funds are available capital, not money at stake.
   A planned or simulated transaction is not committed capital. A submission without a deposit has
   no financial stake; its time/compute cost is still effort/expense.
3. **Realized profit/loss:** actual earned awards/rewards or closed-position proceeds, less the matched
   principal/cost basis and actual expenses/fees. Owner funding, bridges between owned addresses and
   returned deposit principal are capital movements, not income. Deduct every expense once. Report
   both period and cumulative realized net P/L.
4. **Unrealized profit/loss:** a separately labelled estimate for open positions from a fresh executable
   liquidation quote or documented mark, net of estimated exit costs, less their remaining cost basis.
   If no credible valuation exists, say unknown. Advertised prizes, possible rewards, unresolved claims
   and modelled expected value are not realized earnings and must not be added to realized P/L.

Keep unlike assets and chains separate. Do not sum ETH, xDAI, PNK and stablecoins as one raw total.
An optional reporting-currency view must cite price source, timestamp and conversion assumptions;
retain native-unit figures and distinguish token-price effects from task returns. When information is
incomplete, show the known subtotal, missing evidence and how that limits P/L rather than assuming zero.
Do not spend funds or close a position merely to make a report more complete.

## Deliver a concise, traceable report

Save `run/reports/<UTC-timestamp>.md` and show it to the current user. Use a readable structure:

- Reporting period, as-of time, and whether this is requested, day-one, weekly or catch-up.
- A short account of completed work, current blockers and the next action.
- A per-task table: task; status/output; effort; expenses/fees; money at stake; realized net P/L;
  unrealized estimate. Use separate asset rows where needed.
- Portfolio totals by asset/chain, available balances, committed capital and unsettled rewards/positions.
- Material unknowns, source links/transaction hashes, and the next scheduled report time or the actual
  automatic-delivery limitation.

An empty work log gets an honest "No task work recorded yet" report; do not invent effort, zero-cost
claims, current balances or profits. A partial book, unsubmitted case, unverified reward or losing trade
belongs in the report. Update delivery bookkeeping only after the report has actually been shown.
