Six public next steps cover new readers, finished readers, update-seekers, referral-ready readers, curators, and writers.
ACTION LADDER1 step
Use one next action at a time. A reader who just got an answer needs a different ask than a curator, writer, or finished reader.
Show one action that fits the reader's current intent instead of asking everyone for the same follow or share.
This ladder uses published routes, copy buttons, feeds, and referrals. It does not buy traffic or perform account actions.
A step counts only when a current follower count, live URL, accepted citation, referral source, or measured visit supports it.
NEXT BEST ACTIONS
Answer, follow, save, refer, citeChoose the step that matches the reader
Answer the source question first
New readerUse when: Use when someone is still trying to find official files or understand which route to open.
Action: Send the answer page, then stop. Let the source route do the trust-building before asking for anything else.
Proof: Visible reply, accepted link, or measured visit to the answer route.
Start here if you want the official Epstein-file routes before the claims start: https://innercircleledger.com/answers/where-are-the-epstein-files/
Ask for the Page follow after value
Finished readerUse when: Use after a reader opens a Ledger page, asks a follow-up, or says the source map helped.
Action: Point them to the branded follow handoff or the quick card, not a long pitch.
Proof: Current visible Facebook Page follower count or account-side Page insight receipt.
If this Ledger source route helped, follow the Page so the next public-record update is easier to find: https://innercircleledger.com/fb/
Offer RSS when Facebook is not right
No algorithmUse when: Use for readers, curators, or researchers who prefer direct feeds to platform posts.
Action: Offer the feed or OPML bundle as a quiet return path.
Proof: Later return visit, accepted feed listing, public mention, or referral traffic.
Follow Ledger updates without waiting on a social feed: https://innercircleledger.com/news.xml
Ask for one qualified referral
Useful readerUse when: Use when someone already understands the Ledger and likely knows one person who tracks public records.
Action: Ask for one introduction, share, or source-check, not a blast to a list.
Proof: Referral reply, visible share, accepted link, referral URL, or measured referral visit.
If this helped, send one Ledger route to one person who would actually use the source map: https://innercircleledger.com/reader-referral-kit/
Offer the curator packet
List or feed ownerUse when: Use for newsletter roundups, resource pages, RSS directories, show notes, and public-record link lists.
Action: Send the curator kit with the route that fits their listing format.
Proof: Accepted listing, saved resource entry, public citation, or referral traffic.
For a source list or feed reader, the Ledger curator kit has RSS, JSON Feed, OPML, listing copy, and caveats: https://innercircleledger.com/curator-kit/
Make citation easy
Writer or moderatorUse when: Use when a writer, host, moderator, or page admin needs attribution language and caveats.
Action: Offer the media kit or moderator brief so the link can travel with the limits attached.
Proof: Writer reply, show-note link, moderator approval, live post URL, or measured referral.
Inner Circle Ledger has a free media kit with source routes, attribution language, and caveats in one place: https://innercircleledger.com/media-kit/
ACTION RULES
$0 spendKeep the ask useful
Match the reader's current intent
A source question gets an answer page. A finished reader gets a follow route. A curator gets feeds. Do not collapse every moment into the same ask.
Give one clean next step
Too many asks make the Ledger feel noisy. Choose the smallest useful action and let the reader decide whether to keep going.
Count evidence, not effort
Track live URLs, accepted links, referral sources, visible follower changes, and measured visits. Drafts and copied text are setup only.
Spend stays locked until proof exists
Do not boost a flat route. Paid tests remain held until account-side checks, exact approval, and evidence from free signals justify the next move.
PROOF LOG
Do not count a planned action.
Paste one line only after the action exists or produces a current signal. Keep the destination, route, and evidence together so the next batch can repeat what worked.
Copy action log
Reader stage | action used | Ledger route | destination or live URL | visible follow/referral/click evidence | repeat/change/pause