Institutions investing in kindness and wellbeing programmes can usually say how many acts got logged. What they struggle to say is what those acts started. That gap — between a count and a multiplication effect — is what RippleCore is built to close.
The mechanic is deliberately narrow
A member logs a story act or a quick act: a caption, a category, a map-visibility level, and a story audience. Nothing more is required. From any act, another member can say “I was inspired” — that creates a new act linked back to the one that sparked it, extending its Ripple Chain. Inspired is the one action allowed to feel like an event; everywhere else, the product stays quiet on purpose.
Ripple Chain leads, Ripple Score supports
An act’s detail view surfaces the chain of acts it went on to inspire, and drilling from one act into another remounts the detail — so you can follow a chain the same way you’d follow a conversation. The human story leads. The numbers support it, and never headline.
A member’s cumulative impact is reflected back to them as a concentric Ripple Score ring — a personal reflection of their own activity, not a leaderboard rank pushed at them. (RippleCore does have a leaderboard, inside the Circle hub — it just isn’t the frame Ripple Score itself is presented in.)
Why this is evidence, not a vanity metric
The reason this matters for an institution is reconcilability. Ripple Score and Ripple Chain length aren’t a black-box dashboard number — admin totals reconcile to the acts members actually see, because every read is scoped to your Circle server-side, not filtered on the client. That’s the difference between “we logged 1,000 acts” and “those acts inspired 3,500 more”: the second claim has to be traceable back to real, linked acts, or it isn’t worth making.
If you want to see it against your own numbers, book a demo.