Every project generates adoption signals in isolation. Heyday standardises, weights, and reasons over them to produce actionable recommendations — federated across 9 domains.
Every project interprets adoption signals in isolation. Heyday makes cross-project adoption intelligence a shared, composable resource — sovereign and ecosystem-native.
Harvey tracks operator churn. DANAI tracks cascade routing. CE tracks policy drift. MMB tracks brand growth. None of them talk to each other — until now. Heyday proved this model at MMB scale across 50+ brands, then federated the same reasoning engine across the entire Coherence Ecosystem.
The reasoning core is domain-agnostic. Only the signal weights, confidence thresholds, and simulation bias change per domain.
8 ecosystem adapters pull live metrics every 15 minutes via Promise.allSettled. A failed adapter never blocks others. Signals normalised to 0.0–1.0.
Domain tuning weights applied multiplicatively. The dominant weighted signal drives the recommendation action string. 11 cross-domain correlation pairs detect shared causes.
Three-scenario Monte Carlo: optimistic (25%), expected (50%), pessimistic (25%). simulation_bias calibrates domain optimism — MMB: 1.2×, CE: 0.9×.
Only recommendations above the domain’s confidence_threshold are emitted. Below-threshold signals return null — no action, no noise.
Every recommendation emitted as a HeydayRecommendationCredential signed with Ed25519. NTFY push fires on confidence ≥ 0.85. FHF propagated to CE on new cross-domain finds.
Ecosystem peers confirm outcomes via SDK confirmOutcome(). After 5+ confirmed outcomes, Heyday proposes tuning weight adjustments — HITL-reviewed before applying.
Domain tuning is the only thing that changes. Add a tuning-{domain}.json and a line in listDomains() — the engine is already there.
When two signals from different domains exceed 0.5 simultaneously, Heyday surfaces a synthesis — a shared root cause invisible to either project alone. Detected correlations are propagated to CE via FHF.
Heyday is a shared resource — designed with the projects it serves, not for them.
If your domain is already registered, push signals directly:
import { HeydayClient } from '@coherence/heyday'; const client = new HeydayClient({ endpoint: 'https://heyday.multiskilled.ai', authToken: process.env.HEYDAY_AUTH_TOKEN, }); // Push signals await client.ingestSignal('harvey', [{ key: 'operator_churn', value: 0.72, source: 'harvey-desktop', collected_at: new Date().toISOString(), }]); // Get a recommendation const { recommendation } = await client.recommend('harvey'); console.log(recommendation.action, recommendation.confidence);
New domain? Submit an enrollment request (HITL-gated, typically 1–2 days):
# Via HTTP curl -X POST https://heyday.multiskilled.ai/api/v1/enroll \ -H "Content-Type: application/json" \ -d '{ "domain": "my-project", "requester_did": "did:web:my-project.multiskilled.ai:ecosystem", "capabilities": ["my-project.signal.v1"], "tuning": { "signal_weights": { "adoption_rate": 2.0 }, "confidence_threshold": 0.65, "time_horizon_days": 14 } }' # Or include heyday: { domain } in peer.announced # Heyday auto-submits the enrollment for you
The operator dashboard shows live signals, active correlations, recommendation history, and pending enrollments. Authentik-protected — request access from dkm.