One useful owned-channel post per day gives every later comment or pitch a clean anchor.
Thirty days of source-first prompts. Publish by hand, adapt to the real news cycle, and count only visible results.
After the owned post is live, use the Reach Queue to screen up to three relevant replies by hand.
Send one personalized source tip only when the writer, host, or moderator already has a matching need.
Keep the calendar free. Paid tests stay held until the launch-readiness checks clear.
Thirty prompts for the next month
Where the files are
Owned post: Start with the simplest source question: where to find the public Epstein-file release points.
Follow-up: Queue three threads where people ask for release links, not allegations.
If you are trying to find the released Epstein-file material, this short answer maps the public starting points and links into the larger source map. https://innercircleledger.com/answers/where-are-the-epstein-files/
Big finds
Owned post: Point readers to the high-signal takeaways before sending them into the full archive.
Follow-up: Reply only where the thread asks what matters in the files.
The big-finds page separates the main public-record takeaways from the underlying document routes so readers can check the source path. https://innercircleledger.com/answers/what-are-the-big-finds-in-epstein-files/
Name-list caution
Owned post: Make the caveat visible: a name mention is not proof by itself.
Follow-up: Find one media-literacy or records thread where the caution directly helps.
A name appearing in released records is a research lead, not proof by itself. This answer keeps that distinction attached to the source route. https://innercircleledger.com/answers/does-a-name-in-epstein-files-prove-wrongdoing/
Data Sets 1-12
Owned post: Explain dataset labels for readers who are lost inside the release structure.
Follow-up: Queue court-doc or research communities asking about dataset numbers.
If the Data Set labels are the confusing part, this answer explains what those release routes are for and how to follow them back to source material. https://innercircleledger.com/answers/what-are-epstein-data-sets/
Full source map
Owned post: Introduce the complete public source map and keep the verdict caveat in the caption.
Follow-up: Pitch one link roundup or show-notes editor with the media kit.
Inner Circle Ledger has a free source map for DOJ, House, court, FOIA, and data-set routes. It is built for verification, not shortcut claims. https://innercircleledger.com/epstein-files/
Methodology
Owned post: Show how the Ledger separates allegations, responses, outcomes, corrections, and source dates.
Follow-up: Use in threads that ask how claims are checked.
The methodology page explains how the Ledger labels allegations, findings, closures, pleas, convictions, and corrections before anything becomes a claim. https://innercircleledger.com/methodology/
Weekly recap
Owned post: Recap the first six source routes and invite readers to bookmark the Share Hub.
Follow-up: Review which route earned the best clicks or replies before week two.
This week's useful routes are collected in the Share Hub: source map, answer pages, caveats, RSS, and outreach tools in one place. https://innercircleledger.com/share/
Trump-Epstein context
Owned post: Use the careful context route, not a sweeping claim.
Follow-up: Queue only discussions asking for the bounded context.
This route points to Trump-Epstein context while keeping the difference between a source trail and a conclusion visible. https://innercircleledger.com/answers/trump-epstein-context/
Federal case record
Owned post: Separate the federal prosecution file from broader archive discussion.
Follow-up: Use where the thread asks about charges, plea, or prosecution history.
For federal-case context, this file keeps the prosecution record separate from broader name-list speculation and links back to source material. https://innercircleledger.com/cases/epstein-federal-prosecution/
Citation language
Owned post: Help writers and moderators cite the Ledger without overstating it.
Follow-up: Send one personalized note to a writer who collects public-record links.
If you cite the Ledger, this answer gives the clean attribution path and points readers back to underlying public records. https://innercircleledger.com/answers/how-to-cite-inner-circle-ledger/
Safe sharing
Owned post: Publish a practical caution for people sharing records in fast threads.
Follow-up: Use in threads where screenshots or name claims are outrunning context.
This answer is built for safer sharing: exact route, disclosure, source caveat, and no claim that a name mention proves wrongdoing. https://innercircleledger.com/answers/how-to-share-epstein-files-safely/
Answer hub
Owned post: Introduce the stable answer URLs as a cleaner alternative to broad link drops.
Follow-up: Queue three narrow questions and match each to one answer page.
The answer hub has short, stable URLs for common Epstein-file source questions, name-list caveats, Data Set routing, and citation help. https://innercircleledger.com/answers/
Media kit
Owned post: Give writers, hosts, and moderators a single source-kit route.
Follow-up: Pitch one newsletter or podcast with one reason the route fits their work.
For writers, hosts, and moderators, the media kit collects best links and attribution language without presenting the Ledger as an official source. https://innercircleledger.com/media-kit/
Reach check
Owned post: Report the honest traffic posture: measured visits only, no fabricated totals.
Follow-up: Retire one low-quality destination and repeat one useful route with a new angle.
Traffic only counts when it is real and observable. The Traffic Pulse keeps drafts, candidates, and live placements separate. https://innercircleledger.com/traffic/
Discovery desk
Owned post: Show the workflow for finding better rooms before posting.
Follow-up: Find fifteen candidates, then move only fit candidates into Reach Queue.
The Discovery Desk is for finding places where a Ledger link actually helps: records questions, source routes, dates, and caveats first. https://innercircleledger.com/discovery-desk/
Reach queue
Owned post: Explain the 15-slot queue and the difference between planning and publishing.
Follow-up: Screen the next batch and mark each slot candidate, approved, live, or counted.
The Reach Queue turns possible rooms, comments, writers, and hosts into one-source, rule-fit placements before anything is counted. https://innercircleledger.com/reach-queue/
Comment kit
Owned post: Offer fifteen draft starters while making the anti-spam rule explicit.
Follow-up: Use only three replies, each adapted to a live source question.
The Comment Kit has draft starters for source questions, but a copied draft is not reach. Only visible, allowed comments count. https://innercircleledger.com/comment-kit/
Moderator brief
Owned post: Publish the permission-first path for groups and guarded pages.
Follow-up: Ask one moderator before any link appears.
The Moderator Brief keeps the permission ask, rule-fit check, allowed-use language, and no-link fallback in one place. https://innercircleledger.com/moderator-brief/
Link brief
Owned post: Make the case for earned links from newsletters, show notes, and source lists.
Follow-up: Send one citation-ready route to a real curator.
The Link Brief gives people a clean reason to cite the Ledger: exact routes, audience hooks, attribution language, and linking rules. https://innercircleledger.com/link-brief/
Pitch desk
Owned post: Show how one-to-one outreach differs from mass messaging.
Follow-up: Personalize one pitch to someone already covering the subject.
The Pitch Desk is for earning attention by being useful: one recipient, one route, one reason it helps their current work. https://innercircleledger.com/pitch-desk/
Press note
Owned post: Give aligned audiences a compact note they can cite.
Follow-up: Offer the press note to one writer, host, or moderator who needs a source-map explanation.
The Press Note explains the Epstein-files source map and how to cite it safely: source map, not a verdict. https://innercircleledger.com/press-note/
Daily tracker
Owned post: Shift from archive material to current public-record movement.
Follow-up: Use only when the thread asks what changed today.
For current public-record movement, the daily tracker is the better route than forcing an Epstein-files link into an unrelated conversation. https://innercircleledger.com/trump-tracker/
Source directory
Owned post: Point researchers to the source directory when they want publishers, dates, and source types.
Follow-up: Queue forums or newsletters that value source indexing.
The source directory lets readers check the publishers, source type, and where a record is used before they rely on a claim. https://innercircleledger.com/sources/
Timeline
Owned post: Give readers a date-first way into the archive.
Follow-up: Use in threads asking when events happened or how records connect over time.
The timeline helps readers move through the record by date instead of chasing disconnected claims. https://innercircleledger.com/timeline/
People directory
Owned post: Show that profiles are directories into records, not guilt labels.
Follow-up: Use only when someone asks what pages exist for a person.
The people directory links profiles to documented files. Inclusion is not a verdict; each page points back to records and outcomes. https://innercircleledger.com/people/
Case files
Owned post: Invite readers to search the full case archive by topic, person, or outcome.
Follow-up: Answer three questions by linking a specific case file, not the homepage.
The homepage search lets readers open case files by person, topic, or outcome while keeping source links, responses, and limits attached. https://innercircleledger.com/
Newsletter status
Owned post: Set expectations that email signup is not active yet and RSS is available now.
Follow-up: Direct readers who ask for updates to RSS until the email flow is verified.
Email signup stays closed until the mailbox and unsubscribe flow are verified. The RSS feeds are the clean follow path right now. https://innercircleledger.com/newsletter/
Growth playbook
Owned post: Remind the team that 10,000 views means useful, measured distribution, not spray-and-pray posting.
Follow-up: Compare the month-to-date route winners and repeat the useful ones.
The growth playbook keeps the 10,000-view target tied to useful links, rule-fit sharing, and measured results. https://innercircleledger.com/growth/
Outreach tracker
Owned post: Move all live posts, accepted pitches, and useful replies into one tracker habit.
Follow-up: Clean the queue: candidate, rules fit, ready, live, counted.
The Outreach Tracker keeps candidates, ready slots, live placements, and counted traffic separate so the next batch gets smarter. https://innercircleledger.com/outreach/
Month-end reset
Owned post: Review the month and repeat the strongest seven routes with fresh angles.
Follow-up: Keep channels that brought useful replies or measured visits; drop the rest for a week.
The post calendar is a rotation, not a script. Keep the routes that earned useful attention, refresh the angle, and stop anything that only creates noise. https://innercircleledger.com/post-calendar/
Use the calendar without sounding canned
Do not repeat the same link daily
Rotate answer pages, source maps, tracker pages, media kit routes, and methodology links so each post has a distinct reason to exist.
Anchor before outreach
Publish the owned post first when possible, then use it as the reference point for screened comments, pitches, and follow-ups.
Match replies to real questions
A calendar prompt is not permission to post anywhere. Move replies through Discovery Desk, Reach Queue, and community rules first.
Let results change the calendar
Repeat topics that generate measured visits or useful replies. Pause topics that produce arguments without source engagement.
Calendar work becomes reach only after it is live.
Use this line for each owned post, then move approved follow-up placements into Reach Queue, Outreach Tracker, and Traffic Pulse.
Copy daily line
Day | owned post URL | Ledger route | follow-up candidates | live comments/pitches | measured clicks/views | repeat/pause decision