Reference — Resonance Official Program

Phase 2 + 2.5 state (live as of 2026-05-07 23:18 UTC):

• partners.use_universal_formula = true — universal reward formula active for Resonance Official
• partners.bounty_pool_pct = 0.050 — Weekly Bounty enabled at 5% of weekly emission
• partners.notification_channel_id = 1482567375063748668 — bounty announcements channel
• event_families populated for all 14 monitored events (10 unlocks + 4 core), per mig 057
• All 10 role-progression milestones (Echo → Resonat) is_active=true (re-enabled 2026-05-07 after the 2026-05-05 incident-response deactivation)
• Phase 1 ladder unchanged below
• Activity Score reset to 0 for all users 2026-05-07 (Soneium S10 fresh-start alignment); first natural rollover Mon May 11 00:00 UTC

This page renders the entire Resonance Official brand program as the canonical example. Use it as the model when designing your own program with template.yml.

Overview

The Resonance Official program contains:

• 4 core events, each with 10 supersession tiers spanning Tune-In L0 through L90.
• 10 unlock events, each gated at a specific tune level (L0, L10, L20, … L90).
• A tightened quality gate running at strictness 7.
• Reaction gating with credibility filtering, burst-window collapsing, and a default reactor threshold of 5.

In total, that's 50 monitoring_rules rows for a brand-server pair: 40 core-event tiers (4 events × 10 tiers) plus 10 unlock-event rows.

Core events — full tier values

quality (10 tiers)

Tier	Tune L	RSNC	Cap/wk	Cooldown
0	0	15	50	300s
1	10	20	58	300s
2	20	25	66	300s
3	30	30	74	300s
4	40	35	82	300s
5	50	40	90	300s
6	60	50	98	300s
7	70	58	106	300s
8	80	65	114	300s
9	90	75	120	300s

L90 ceiling: 75 RSNC × 120 claims/wk = 9,000 RSNC/week, achievable only with sustained engagement that passes the tightened quality gate.

gm_checkin (10 tiers — gentler curve, daily ritual)

Tier	Tune L	RSNC	Cap/day
0	0	10	1
1	10	11	1
2	20	12	2
3	30	14	2
4	40	16	2
5	50	19	2
6	60	22	3
7	70	26	3
8	80	32	3
9	90	40	3

reaction_threshold (Popular Content — 10 tiers)

Tier	Tune L	RSNC	Cap/day
0	0	15	3
1	10	17	4
2	20	20	5
3	30	22	6
4	40	26	7
5	50	30	8
6	60	36	9
7	70	44	10
8	80	52	11
9	90	60	12

social_link (10 tiers — infrequent, weekly cap)

Tier	Tune L	RSNC	Cap/wk
0	0	30	10
1	10	34	12
2	20	40	14
3	30	46	15
4	40	55	17
5	50	65	18
6	60	76	19
7	70	88	20
8	80	92	20
9	90	100	20

Total earning ceiling per tune level (core events only)

Theoretical maximum if every cap binds across all four core events:

Tune L	quality	gm_checkin	reaction_threshold	social_link	Total core ceiling
L0	750	70	315	300	1,435
L10	1,160	77	476	408	2,121
L20	1,650	168	700	560	3,078
L30	2,220	196	924	690	4,030
L40	2,870	224	1,274	935	5,303
L50	3,600	266	1,680	1,170	6,716
L60	4,900	462	2,268	1,444	9,074
L70	6,148	546	3,080	1,760	11,534
L80	7,410	672	4,004	1,840	13,926
L90	9,000	840	5,040	2,000	16,880

These are weekly figures. Most members will earn a fraction because passing the tightened gate every claim is hard.

Unlock events — full table

Tune L	event_type	RSNC	Cap	Trigger summary
0	thread_starter	30	2/day	Create thread; ≥2 distinct users post in it within 24h
10	stage_host	120	1/wk	Host a Stage instance; ≥3 distinct attendees
20	deep_reply	24	5/day	Reply to a message that already has ≥3 unique-user reactions
30	conversation_starter	40	3/day	Your message gets replies from ≥3 distinct users within 1h
40	voice_sustained	48	3/wk	Stay in voice ≥60 continuous minutes (no channel-hopping)
50	mentor_reach	36	3/day	Reply to new member (joined ≤7d, <5 server msgs) within 24h of their post
60	traffic_director	80	1/wk	@mentioned by ≥5 distinct users within a 24h window
70	resonance_beacon	60	3/wk	Post external URL; ≥3 distinct reactors; passes quality gate
80	answered_question	90	2/day	Reply to a question; OP reacts ✅/🙏-class or reply gets ≥3 reactions
90	dawn_patrol	72	1/day	First message in a channel after ≥8h silence; passes quality gate

See Unlock Events for the full per-event detection-config breakdown.

Quality-gate parameters used by Resonance Official

Parameter	Value
default_strictness	7
threshold_formula	40 + strictness * 6 → 82 at strictness 7
Anchor-score penalty (H1)	−30
Chain-similarity threshold (H3)	0.6
Chain-similarity penalty max (H3)	30
Reply-inheritance bonus (parent passed)	+10
Dead-channel penalty (H4)	−10
Dead-channel member threshold	≥100
Min reactor credibility	40
Burst-window seconds	30
Spread-window seconds	300
Default reactor threshold	5
Voter-reward requires parent pass	true
URL allowlist	*.rsnc.network (other URLs are weak anchors)

Where to look in code

• Rule seed (40 core tiers + 10 unlocks): workers/sql/migrations/038b_resonance_official_seed.sql
• Schema migration (adds min_tune_level, snapshot table, lookup RPC): workers/sql/migrations/038_program_rebalance.sql
• Effective-rule lookup RPC: get_effective_rules_for_user(p_brand_id, p_server_id, p_user_tune_level) — Postgres function defined in the migration above.
• Event-handler tier selection: workers/src/event-handler/index.js — at the monitoring-rules lookup, calls database.getMonitoringRuleForTuneLevel(...).
• Unlock-event handlers: discord-bot/src/webhooks/unlock-handlers/ — one module per unlock event (thread-starter.js, stage-host.js, deep-reply.js, conversation-starter.js, voice-sustained.js, mentor-reach.js, traffic-director.js, resonance-beacon.js, answered-question.js, dawn-patrol.js).
• Quality-gate scoring + heuristics: discord-bot/src/webhooks/gateway-event-handler.js — composite score, H1/H3/H4 inserted around line 188–215, reaction gating in the reaction_threshold handler.
• Tune-In service (gen-multiplier formula, charge-multiplier removal): workers/src/shared-services/services/tune-service.js — generateLevels() and _activateTuneEffects() are the changed functions.
• /cooldowns rendering (tier badges + Upcoming Unlocks): discord-bot/src/commands/cooldowns.js.