Company
Documentation
Reference documentation for platform behavior, data methodology, operational controls and release governance.
Platform guides
Guides cover onboarding, dashboard navigation, watchlists, signals, scenario interpretation and copy-trading controls.
Each workflow guide is written for practical execution so users can understand prerequisites, expected behavior and common failure cases.
- Wallet connection and network requirements
- Dashboard modules and refresh behavior
- Following agents and configuring copy allocation
- Paper-trading and scenario analysis playbooks
Signal generation methodology
Signal cards are generated from live market inputs, structured agent context and deterministic fallback logic when model output is unavailable.
Displayed time labels are derived from persisted timestamps to preserve temporal consistency across sessions.
- Model-assisted generation with bounded confidence ranges
- Cache and TTL controls to prevent unnecessary churn
- Persisted timestamps for accurate relative-time display
- Fallback generation paths for service continuity
Data methodology
Market rows are built from external quote providers and transformed into a unified internal format for display and analytics.
Provider output is normalized before rendering so charting, comparison views and scoring logic can remain stable across asset classes.
- Refresh cadence and cache behavior
- Symbol mapping and asset aliases
- Fallback policy when providers are unavailable
- Known constraints and data caveats
Security and operational controls
Operational procedures focus on minimizing user confusion during degraded states while maintaining a clear audit trail of key behavior changes.
- Access controls and non-custodial wallet model
- Environment-based secrets and provider credentials
- Observability for critical API paths
- Incident response and user communication priorities
Release and change policy
Material updates to methodology, legal disclosures or user-facing behavior are documented before release when feasible.
Breaking changes should include migration notes, user-facing impact summaries and revised caveats where relevant.
- Versioned release notes for important changes
- Backward-compatibility expectations for core routes
- Updated legal references when product scope changes
- Post-release verification of critical metrics