Ingestion Layer
Chain indexers, market feeds, contract metadata, and governance events into raw storage.
Execution Architecture
Backend MVP plan: data in, scores out.
This is the minimum architecture needed to deliver reliable, versioned risk outputs.
Nightly Score Refresh
Top 250 Tokens
< 300ms p95 API
Versioned Model Bundle
System overview
Feature Pipeline
Deterministic feature jobs for wallet graph, liquidity behavior, semantic risk flags, and anomaly vectors.
Model Service
Batch scoring with calibrated outputs and attribution metadata written to a serving datastore.
Scoring API
Read-only endpoints for project score, confidence, decomposition, timeline, and model version fields.
Ops and Monitoring
Job orchestration, data quality checks, drift monitoring, and incident alerting for pipeline failures.
MVP service contracts
| Endpoint | Purpose | Key Fields |
|---|---|---|
| GET /v1/projects/{id}/score | Primary score view | score, confidence, risk_band, model_version, scored_at |
| GET /v1/projects/{id}/decomposition | Module explainability | module_scores, weights, contributions |
| GET /v1/projects/{id}/timeline | Recent risk-relevant events | events, timestamps, severity, source_type |
| GET /v1/models/latest | Transparency metadata | version, train_window, benchmark_metrics, changelog |
Execution phases
Phase A (Weeks 1-2)
Ingestion skeleton, canonical schema, and one-chain historical backfill.
Phase B (Weeks 3-4)
Feature jobs for wallet graph, liquidity, and contract semantics with reproducible run configs.
Phase C (Weeks 5-6)
Baseline model scoring pipeline and decomposition artifact generation.
Phase D (Weeks 7-8)
Read-only API and dashboard integration with nightly scheduled refresh.
MVP focus: reliability and transparent versioning first, model sophistication second.