Data readiness overview
Schema + freshness + coverage scoring for contract validation.
Overall readiness
Weights: schema 0.45, freshness 0.3, coverage 0.25.
Per source
| Source | Score | Schema | Freshness | Coverage | Latest signal |
|---|---|---|---|---|---|
billing ready | 100 | 100 | 100 | 100 | 2026-02-08T00:00:00.000Z |
product_usage ready | 100 | 100 | 100 | 100 | 2026-02-08T10:00:00.000Z |
crm ready | 100 | 100 | 100 | 100 | 2026-02-06T14:00:00.000Z |
support ready | 84.5 | 100 | 90 | 50 | 2026-02-05T09:00:00.000Z |
Inference limits
Explicitly communicate what the system can infer, what it cannot infer yet, and why unknown risk is shown.
billing
Billing data captures monetization, but not product and support signals.
Can infer
- - Revenue trend by account
- - At-risk billing states
- - Potential churn from payment behavior
Cannot infer yet
- - Product adoption depth
- - Support burden
product_usage
Usage events explain behavior, but not financial or support context.
Can infer
- - Engagement trend
- - Adoption by feature
- - Usage decline risk signals
Cannot infer yet
- - Payment delinquency
- - Support escalation pressure
crm
CRM captures relationship context, not direct behavior or billing facts.
Can infer
- - Lifecycle-based prioritization
- - Owner workload and account distribution
Cannot infer yet
- - Real product behavior
- - Invoice quality and payment risk
support
Support data reflects friction but not revenue and in-product behavior.
Can infer
- - Support burden and escalation pressure
- - Sentiment risk from CSAT and ticket backlog
Cannot infer yet
- - Actual monetization impact
- - Feature-level adoption
API
Use GET /api/contracts/readiness for model metadata and POST /api/contracts/readiness for runtime validation + readiness reports.