Run two measured weeks before changing the whole strategy. Keep the same fields so winners are obvious.
SPRINT BOARD14
Two weeks of focused source-first distribution. Check traffic daily, then repeat the route that produces real visits or useful referrals.
A 10,000-view month needs about 334 measured page views per day. Treat the number as a pace marker.
Stop after three useful group comments or posts in a day, sooner if the conversation turns low-quality.
Paid reach stays held until attribution, billing caps, policy classification, and mobile preview checks pass.
DAY-BY-DAY PLAN
Measure before expanding volumeOne primary action per day
| Day | Action | Route | Use when | Copy |
|---|---|---|---|---|
| Day 1 | Page anchor | Route | Publish or refresh one owned Page post with the current reason to use the source map. | |
| Day 2 | Where-file reply | Route | Answer one public source-location question with one relevant link and disclosure. | |
| Day 3 | Dataset post | Route | Explain Data Sets 1-12 and EFTA routing without implying that every file has been reviewed locally. | |
| Day 4 | Writer pitch | Route | Send one personalized tip to a writer or newsletter already covering the records. | |
| Day 5 | Name caution | Route | Use when a thread turns a name mention into an unsupported conclusion. | |
| Day 6 | Rules check | Route | Review one Reddit-style or forum target and save the allowed participation path before posting. | |
| Day 7 | Analytics review | Route | Keep the two best angles, drop the weakest one, and reset the next week around measured visits. | |
| Day 8 | Federal case | Route | Use the prosecution file when the discussion is about charges, not broad list speculation. | |
| Day 9 | Document thread | Route | Comment only where the thread is already asking about document IDs, datasets, or source routing. | |
| Day 10 | Second pitch | Route | Offer the media kit as a source aid to one public-records, law, or civic outlet. | |
| Day 11 | Short thread | Route | Use a controlled Ledger account only; post a short source-map thread with no sensational claim. | |
| Day 12 | Tracker context | Route | Use the tracker only when the conversation is about the Trump network rather than the files themselves. | |
| Day 13 | Second community | Route | Choose one new community target, answer a specific question, and skip unclear self-promo rules. | |
| Day 14 | Decision day | Route | Decide what repeats next week. Keep paid spend at zero unless every launch gate is verified. |
CHANNEL FIT
Skip bad-fit reachChoose the room by reader need
Start where identity is clear
One Page post gives later replies a public anchor. Do not boost it until the paid checks are done.
Use source questions, not volume
Good fits ask where records are, what a document ID means, or how to verify a claim. Skip slogan-only threads.
Pitch a source aid
Send one relevant page to someone already covering DOJ releases, court records, public accountability, or Trump-network context.
Rules before links
Read current rules first. If links are unwelcome, summarize the source path without dropping the Ledger URL.
Credibility over traffic
Use a short thread for reuse and discovery. Count site visits, not impressions.
Make repeat visits possible
Point interested readers to RSS, the tracker, the answer bank, or a bookmarkable route after the first useful exchange.
COPY BLOCKS
Disclosure stays attachedSix notes to adapt during the sprint
When someone asks where to start
I publish Inner Circle Ledger. If useful here, this answer points to the public Epstein-file starting points and keeps the source caveats attached: https://innercircleledger.com/answers/where-are-the-epstein-files/
When EFTA IDs come up
I publish Inner Circle Ledger. For EFTA or dataset-number questions, this explains how the DOJ Data Sets 1-12 routing works before anyone makes a claim about a specific file: https://innercircleledger.com/answers/what-are-epstein-data-sets/
When a thread overstates a mention
I publish Inner Circle Ledger. A name appearing in released material is a research lead, not proof by itself. This short answer keeps that caution attached: https://innercircleledger.com/answers/does-a-name-in-epstein-files-prove-wrongdoing/
For a newsletter or host
Possible source aid for your coverage: Inner Circle Ledger has a free Epstein source map, answer bank, and citation language with official release routes kept separate from interpretation: https://innercircleledger.com/media-kit/
When a group blocks outside links
No worries on links. The safest source path is DOJ and House release gateways first, then dataset or document IDs, then exact-page context before making a claim.
When someone wants updates
For a non-algorithm follow path, Inner Circle Ledger has a news RSS feed and a daily tracker here: https://innercircleledger.com/news.xml
DECISION RULES
Keep, drop, or pause.
If a route sends measured visits or earns useful replies, repeat it with a new angle. If it creates arguments without clicks, pause that destination for a week. If a partner links back, prioritize that over joining more groups.
Paid stays held
Do not spend beyond the approved cap, and do not spend at all until account verification, billing controls, attribution, and mobile preview checks pass.