> ## Documentation Index
> Fetch the complete documentation index at: https://uncoded.ch/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Daily Operations — Operator Routines

> What to do daily, weekly, monthly, and yearly. The rhythms that keep an unCoded operator informed without being overwhelmed.

<Info>
  **Operating an automated trading bot is a discipline, not a continuous task.** The bot does the work; you provide oversight. The right operator routines build situational awareness without demanding constant attention. This page is the rhythm guide.
</Info>

## The four cadences

| Cadence     | Time per session | Focus                                                |
| ----------- | ---------------- | ---------------------------------------------------- |
| **Daily**   | `2–5` minutes    | Health check — is the bot doing what I expect?       |
| **Weekly**  | `30` minutes     | Structured review — analyzing performance, decisions |
| **Monthly** | `60` minutes     | Tax archiving + capital review                       |
| **Yearly**  | `2–4` hours      | Full audit + accountant handoff                      |

Plus: **crisis** — kill-switch readiness for unexpected market events.

## Daily — the 5-minute health check

<Steps>
  <Step title="Open the Dashboard">
    Bookmark for one-click access. Log in.
  </Step>

  <Step title="Glance at the main panel">
    Confirm:

    * Kill switch is in expected state (usually OFF for normal operation).
    * Connection-state indicators all green for every active venue.
    * No urgent alerts or warnings displayed.
  </Step>

  <Step title="Skim the Live Trades panel">
    Quick visual scan:

    * Are positions roughly where you expect?
    * Any held abnormally long?
    * Any unexpected positions?

    The goal is intuition-building, not detailed analysis.
  </Step>

  <Step title="Glance at the day's closed trades">
    Compare against your Telegram chat. Totals match? Reasonable count?

    If your Telegram running total looks off, investigate further. Otherwise move on.
  </Step>

  <Step title="Check log stream briefly">
    Open the Logs panel for `30` seconds. Watch for repeated errors or unusual messages.

    Most days: nothing concerning. The brief check builds your "what does normal look like" intuition.
  </Step>
</Steps>

If everything looks normal: log out. The whole exercise is `2–5` minutes. The goal is not to make decisions every day; it's to confirm "the bot is doing what I expect."

## Weekly — the 30-minute review

<Steps>
  <Step title="Pull the week's analytics">
    Dashboard's analytics panel for the last 7 days. Compare against last week and your monthly running average.

    Trends to notice:

    * Trade frequency stable or shifting?
    * Win rate within typical range?
    * Drawdown character similar to backtest expectation?
  </Step>

  <Step title="Identify the week's worst trade">
    Open the order detail. Was the mode behaving as designed, or was there an anomaly?

    * Mode-design behavior → expected, no action.
    * Anomaly (unusual stop-loss trigger, weird fill, unexpected exit) → flag for investigation.
  </Step>

  <Step title="Identify the week's best trade">
    Same exercise. Was the gain due to the mode hitting expected rungs, or due to an unusually large move that the mode happened to capture?

    Lucky big wins are different from designed wins. Distinguish.
  </Step>

  <Step title="Check the Logs panel for recurring warnings">
    Search for any patterns. Recurring errors are a flag.

    Common: occasional "rate limit" warnings during busy market periods. These are normal if rare. Concerning: recurring authentication failures, configuration mismatches.
  </Step>

  <Step title="Confirm all expected pairs have traded">
    A pair that hasn't closed a trade in a week is a flag worth investigating. Possible causes:

    * Capital allocation too small for min-notional.
    * Mode's buy conditions never triggered.
    * Symbol moved in a way the mode doesn't capture.

    Decide: leave the pair, adjust capital, or remove from active set.
  </Step>

  <Step title="Make any deliberate operator adjustments">
    Add a new pair? Tune a mode parameter? Rotate API keys (if quarterly cadence aligned)?

    Document changes in your operator log: "2026-04-15: added `XRPUSDT` to BasicMode at `$3,000`. Reason: validated by 6-month backtest with `+15%` return."
  </Step>
</Steps>

Weekly reviews are where operator skill develops. The decisions you make here, deliberately and with data, compound over months.

## Monthly — tax archive + capital review (60 minutes)

<Steps>
  <Step title="Pull the Tax Report">
    Dashboard → Tax Report → select last month → export CSV/JSON.

    Archive to your designated tax folder (cloud drive or local with backup).
  </Step>

  <Step title="Cross-check with Telegram running total">
    Last Telegram trade-close of the month should show running total close to (or matching exactly) the tax report's net P\&L.

    Discrepancies investigate immediately — usually a data restore boundary or a manual close not reflected.
  </Step>

  <Step title="Review capital allocation">
    Is each mode's allocated capital still appropriate?

    * Is reserve still \~50%?
    * Has any pair drifted outside the 25% rule?
    * Should you scale up (after multiple consecutive non-negative months)?
    * Should you scale down (if regime mismatch persists)?
  </Step>

  <Step title="Audit the venue's API key activity">
    Each venue's audit log shows API key activity. Review for the month:

    * All calls came from your VPS's IP?
    * Any unfamiliar activity?
    * Any unusual error rates?
  </Step>

  <Step title="Plan structural changes for next month">
    Any deliberate changes? New venue, new mode, new pair? Document the plan; execute it deliberately at month-start, not on impulse mid-month.
  </Step>

  <Step title="Verify backups are running">
    Database backup script ran daily as expected? Off-site backups intact? Test-restore once a quarter to verify recoverability.
  </Step>
</Steps>

## Yearly — the full audit (2–4 hours)

<Steps>
  <Step title="Pull the full-year Tax Report">
    Dashboard → Tax Report → calendar year → export.
  </Step>

  <Step title="Verify against monthly archives">
    Sum of 12 monthly Tax Reports should equal (or closely match) the full-year report. Investigate discrepancies.
  </Step>

  <Step title="Verify against Telegram totals">
    Year-end Telegram running total should match.
  </Step>

  <Step title="Send to accountant">
    With clear documentation of trades, fees, P\&L, and exchange-side history.
  </Step>

  <Step title="Strategic review">
    Big-picture questions:

    * Did the bot do what I intended this year?
    * Should next year's setup look different?
    * Are my modes/pairs/venues optimized for the regime I expect?
    * Should I add or retire anything?
  </Step>

  <Step title="Operator runbook review">
    Update your runbook with this year's learnings:

    * Any new patterns observed?
    * Any incidents that taught lessons?
    * Any decisions you'd make differently?
  </Step>

  <Step title="API key rotation if not already done">
    Annual rotation as a hygiene baseline. Yes, you do quarterly rotation already, but year-end is a natural full-rotation moment.
  </Step>
</Steps>

## Crisis routine — when something is going wrong

<Steps>
  <Step title="Step back. Coffee. Walk.">
    Most "panic decisions" worsen outcomes. Take 5 minutes before doing anything.
  </Step>

  <Step title="Open the Dashboard">
    Look at actual positions, actual P\&L, actual unrealized exposure. Not what you fear; what is.
  </Step>

  <Step title="Compare to backtest expectations">
    Is this within historical drawdown ranges? If yes, the bot is operating within design parameters. Hold. If beyond historical range, engage further.
  </Step>

  <Step title="Decide: kill switch or not?">
    If you're genuinely worried (not just stressed): kill switch ON. Cost of false alarm: zero. Cost of buying into worsening situation: substantial.
  </Step>

  <Step title="Wait for clarity (an hour, a day)">
    Most market events resolve within hours. Wait for the situation to clarify before further action.
  </Step>

  <Step title="Decide with calmer head">
    Once the situation is clearer: re-engage the kill switch (or stay paused). Close positions manually if necessary. Document the incident in your operator log.
  </Step>
</Steps>

## Best practices

<Tip>
  * ✅ **Daily 5-minute Dashboard check** — builds intuition for normal behavior.
  * ✅ **Weekly 30-minute structured review** — where operator skill develops.
  * ✅ **Monthly tax archive + capital review** — keeps records clean and capital aligned.
  * ✅ **Yearly full audit + accountant handoff** — compliance and strategic review.
  * ✅ **Document all changes in an operator runbook** — future-you needs the context.
  * ✅ **Bookmark the kill-switch button** for fast crisis response.
  * ✅ **Have backup recoverability tested quarterly** — knowing restore works matters.
  * ✅ **Don't over-monitor** — daily checks are 5 minutes, not 5 hours.
  * ✅ **Don't under-monitor** — skipping weekly reviews lets anomalies grow.
  * ✅ **Maintain Telegram chat archive** — one extra source of truth for tax purposes.
  * ✅ **Match crisis-response calm to actual stakes** — a 5% drawdown isn't a crisis; a 30% drawdown might be.
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Monitoring" icon="heart-pulse" href="/operations/monitoring">
    Tools and habits for spotting issues before they're crises.
  </Card>

  <Card title="Tax export" icon="file-invoice" href="/operations/tax-export">
    The monthly/yearly tax routine in detail.
  </Card>

  <Card title="Updates" icon="rotate" href="/operations/updates">
    How to update unCoded safely.
  </Card>

  <Card title="Support" icon="life-ring" href="/operations/support">
    When and how to reach out for help.
  </Card>

  <Card title="Risk overview" icon="shield" href="/risk-management/overview">
    The risk framework these routines operate within.
  </Card>

  <Card title="Troubleshooting" icon="wrench" href="/troubleshooting/common-issues">
    For when something is wrong.
  </Card>
</CardGroup>