v1 -> v2 Handoff

This page is the required handoff output for wiki v1. It captures open questions, clarification requests, and suggested v2 priorities.

Open questions (product + tech)

Should we keep connexion as the official term everywhere, or normalize to connection for external-facing docs?
Is onboarding considered complete after any one setup action, or should v2 define a minimum checklist (for example one connexion plus one validated data import)?
For ROI and PnL display, should fees always be treated as already embedded in transaction economics, or should fee treatment be explained separately per screen?
Should auto-generated deposits be explicitly visible and explained in UI copy, or remain mostly technical?
Which strategy condition types should be documented first in depth (priority shortlist) for non-technical readers?
Do we want user-level examples for each strategy type (DCA, SCALP, POSITION_CLOSE) with expected outcomes and failure cases?
For real-time events, what is the expected user-facing behavior when push is unavailable (fallback UX expectations)?
Should daily AI reports be considered core v1 product knowledge or a dedicated v2 section with governance and prompt versioning notes?

Confirm the official ownership matrix wording for each domain (webservice vs core vs portfolio vs worker vs findata vs agent).
Confirm recommended user path for first setup (exchange-first, wallet-first, or both equivalent).
Confirm stable category taxonomy source (bitcoin/stable/memes/defi/other) and who maintains tags.
Confirm whether synchronization behavior around orphan/missing external IDs should be documented as user-facing policy or technical detail.
Confirm report retention and visibility expectations (how long users keep daily reports, deletion policy language).
Confirm if BTC trend report should be documented as mandatory context or optional augmentation for daily reports.

Legacy wiki clones were used as hints and cross-checked with code.

Core ownership drift: legacy core wiki describes portfolio calculation ownership in core; current architecture and APIs place portfolio/position/coherence ownership in glacez-soa-portfolio.
Coverage gaps: legacy portfolio and simulator wiki clones are effectively empty, so v1 relied on code and API contracts.
Findata legacy depth: legacy findata wiki is minimal; v1 used current code for news ingestion/retention and market-data endpoints.

Add diagram-based workflow pages (onboarding, strategy execution, sync reconciliation, event push path).
Expand strategy section with concrete condition examples and edge-case behavior.
Add worked numeric examples for calculation formulas (average price, ROI, UGL/RGL, portfolio cost basis).
Add explicit service ownership matrix with "who owns what" plus escalation path.
Add synchronization edge-case playbook (importing status, stale records, auto-generated balancing transactions).
Add changelog or "recent updates" section to help AI agents track terminology drift.