# Crypto_Agent target-plan phase consolidation

Use when the user asks to continue or report progress against the Crypto_Agent implementation plan, especially if they mention the document's "Zielbauplan" or phases 1–8.

## Key lesson

Do not collapse the user's documented 8-phase target plan into a simplified A/B/C roadmap when they ask for status. The document's actual phases are:

1. Repo and runtime consolidation
2. Market Snapshot Layer
3. Confluence Score Engine
4. Entry improvement
5. Real Paper Lifecycle
6. Three strategy sleeves
7. Copytrading research
8. Portfolio Advisor

The work sequence may intentionally prioritize Phase 5 first, because the document itself marks realistic Paper Lifecycle as current priority 1. But progress reporting must still map back to phases 1–8.

## Recommended workflow

1. Re-read the extracted plan or target-plan status doc before answering phase-progress questions.
2. Report each phase with: status, completed artifacts, open gaps, approximate percentage, and live-readiness impact.
3. If the repo/runtime are drifting, complete Phase 1 hygiene before adding more features:
   - README with modes and start commands.
   - Phase status doc.
   - Runtime runbook that lists active cron jobs/watchdogs, manual status commands, report commands, and paper-only/live criteria.
   - Preserve source plan in `docs/reference/` plus extracted Markdown.
   - Add or verify a legacy-entrypoint guard for old monolithic direct-order files such as `AutoTrader.py`; the guard should fail closed by default and require an explicit env flag (for example `CTB_ALLOW_LEGACY_AUTOTRADER=true`) before the legacy path can run.
   - Run full tests, a daily-report smoke, and a legacy-guard smoke (expecting the disabled exit code/message).
   - Commit and token-safely push the local state so GitHub/runtime/JARVIS reports align.
4. Keep live posture explicit after every phase report:
   - `live_order_allowed=false`
   - `mainnet_signed_action=false`
   - `Promotion=paper_only`
5. When documenting or committing, avoid runtime journals/secrets; source docs and code only.

## Useful artifacts from the 260629 session

- `README.md` — operating modes, start commands, current posture.
- `docs/260629_bot_umsetzungsplan_extracted.md` — extracted source plan.
- `docs/260629_bot_umsetzungsplan_execution_notes.md` — accepted implementation order and safety corrections.
- `docs/260629_zielbauplan_phase_status.md` — phase 1–8 status mapping.
- `docs/runtime_runbook.md` — active cron jobs/watchdogs, manual commands, legacy rules, and promotion/live criteria.
- `AutoTrader.py` legacy guard — historical monolithic direct-order entrypoint should exit by default unless explicitly enabled with a dedicated env flag.

## Pitfall

If the user asks "what about phases 1 to 8?" it is a correction: immediately switch to the document's phase numbering, acknowledge the mismatch, and avoid defending the simplified A/B/C framing.