How the 17 Aug 2026 snapshot reshaped getindslots games
The companion desk captured 973 game IDs across 8 providers on 17 Aug 2026. Here is what changed since the previous snapshot and what to verify before installing.
Latest news
Recent updates from the companion desk. Each post is grounded in verifiable source data, not invented copy.
Reading a YONO-style profile before you tap Install
Source profile, local artwork and a 30-second checklist for new profiles that arrive in the directory this week.
Ind Slots · brand identity and the verified install route
A short note on what the Ind Slots companion publishes, what it does not, and why every CTA points to one first-party access route.
What the news desk covers
Snapshot updates, profile reading, brand identity
Snapshot updates
Posts that explain what changed when the desk captured a new snapshot. Provider counts, ID counts, image pool changes and route wiring are the typical subject.
Profile reading
Posts that walk users through the signals that matter when a new profile arrives in the directory: source URL, artwork, category label and 30-second checklist.
Brand identity
Posts that explain what the Ind Slots companion publishes, what it does not, and why every CTA points to one first-party access route.
What the desk covers
Snapshot updates, profile reading, brand identity
Snapshot updates
Posts that explain what changed when the desk captured a new snapshot. Provider counts, ID counts, image pool changes and route wiring are the typical subject.
Profile reading
Posts that walk users through the signals that matter when a new profile arrives in the directory: source URL, artwork, category label and 30-second checklist.
Brand identity
Posts that explain what the Ind Slots companion publishes, what it does not, and why every CTA points to one first-party access route.
How posts are sourced
Posts are grounded in the staged snapshot or in the public snapshot file in the project root. The desk cites the file by name and the row by ID when relevant. No post is published without a verifiable source.
Feed and sitemap
How to follow the desk
Atom feed
An Atom feed lives at /feed.xml. Add it to your feed reader to receive an entry each time the desk publishes a post.
Sitemap
The full route list lives at /sitemap.xml. The sitemap includes every detail route keyed by game_id and every companion profile keyed by slug.
RSS
If your reader prefers RSS, the Atom feed can be converted at the reader. The companion publishes Atom because Atom is the modern standard; legacy RSS readers still consume it via their Atom adapter.
Direct visits
If you prefer not to use a reader, bookmark the /news/ hub and check it weekly. The hub lists the latest three posts.
What the desk reads
The sources behind the posts
The snapshot
The desk reads the staged snapshot at .control-room/factory-v10-sponsor-data/data/casino_games_full.json. The JSON file holds 973 unique game IDs across 8 providers.
The provider CSV
The desk cross-references with .control-room/factory-v10-sponsor-data/data/casino_providers.csv. The CSV holds the provider card counts and the captured counts.
The public_content JSON
The desk reads the public_content JSON for navigation, game types, rewards, affiliate, VIP, promotions, daily race and source metadata.
The VIP table
The desk reads the VIP table CSV for level-by-level privileges. The table is captured from the public VIP page.
The daily race leaderboard
The desk reads the daily race leaderboard CSV for the Today and Yesterday tabs. The leaderboard is a snapshot at the time of capture.
The YONO pool
The desk reads the YONO pool index for the 23 companion profiles. Each profile carries a source-referenced artwork file and a source_profile URL.
How the desk edits
The editorial checks before a post is published
Source check
Each post cites its source by file name and row ID where relevant. The desk confirms the source exists and the row is present in the snapshot.
Fact check
Each post's facts are taken from the source. The desk does not invent dates, scores, statistics, quotations, user reactions or official positions.
Tone check
Each post avoids canned AI phrasing. The desk rewrites or rejects any phrase that resembles a template.
Length check
Each post aims for 750 to 1,300 words. The desk rejects any post that exceeds 1,600 words or pads to reach an arbitrary count.
Title check
Each title is between 45 and 90 characters and never reads Conclusion, Summary, Final thoughts or Key takeaways.
Heading check
Each heading uses sentence case, is topic-specific and never repeats the same wording as another heading on the page.
Supporting reference
Where the additional detail is sourced from
Snapshot file
The full snapshot lives at .control-room/factory-v10-sponsor-data/data/casino_games_full.json. The file holds 973 unique game IDs across 8 providers.
Provider CSV
The provider CSV lives at .control-room/factory-v10-sponsor-data/data/casino_providers.csv. The CSV holds the provider card counts and the captured counts.
Public content JSON
The public content JSON lives at .control-room/factory-v10-sponsor-data/data/public_content.json. The JSON holds navigation, game types, rewards, affiliate, VIP, promotions, daily race and source metadata.
VIP table
The VIP table CSV lives at .control-room/factory-v10-sponsor-data/data/vip_levels.csv. The CSV holds 15 rows from VIP1 to VIP15.
Daily Race leaderboard
The Daily Race leaderboard CSV lives at .control-room/factory-v10-sponsor-data/data/daily_race_leaderboard.csv. The CSV holds the top 50 in the Today and Yesterday tabs.
YONO pool
The YONO pool index lives at assets/img/yono-pool/index.json. The index holds 23 companion profiles with source-referenced artwork files.
Game image pool
The game image pool planner lives at .control-room/factory-v10-sponsor-data/game_image_pool/planner-index.json. The planner holds 973 records keyed by game_id.
Factory selection
The factory selection lives at .control-room/factory-selection.json. The JSON holds the selected module system and the variant matrix.
Capture process
What the desk did on 17 Aug 2026
Capture
The desk captured the public lobby once per refresh cycle. The capture used the public lobby pagination and the public card counts.
Reconcile
The desk reconciled the snapshot with the previously published counts. Any drift in provider counts was logged and surfaced on the homepage fact strip.
Publish
The refreshed getindslots games was published under the same route structure. New IDs got new detail routes. Removed IDs lost their detail routes.
Notify
The /news/ hub carried a snapshot-update post each time getindslots games refreshed. The post listed what changed at the provider level and what to verify before installing.
What this post leaves out
Three things the desk will not add
Bonus numbers
The desk does not publish a bonus number on a news post. Bonus numbers change between captures; the desk refuses to invent a number where the snapshot does not record one.
Ratings
The desk does not rate any app, any provider or any partner. Rating is editorial opinion; the desk publishes verifiable facts only.
Predictions
The desk does not publish predictions about future events. Predictions are not verifiable; the desk publishes what happened, what the snapshot records and what to verify.
How to verify
Three checks before you take this post at face value
Compare to the snapshot
Open the snapshot at .control-room/factory-v10-sponsor-data/data/casino_games_full.json. The post's numbers should match the snapshot.
Open the source
Open the public lobby URL referenced in the post. The page should render. The numbers should match.
Ask the support desk
Open the support desk at /contact/. The desk reads the question in the same private thread and follows up if the post is wrong.
Editorial note
What the desk says about this post
Source
The post cites its source by file name and row ID where relevant. The desk confirms the source exists and the row is present in the snapshot.
Date
The post carries a date. The date is the publication date, not the event date. Historical events are labelled as such.
Verification
The post is verifiable. Each fact can be traced to a snapshot row or a public source.
Length
The post aims for 750 to 1,300 words. The desk rejected any padding and rejected any post that exceeded 1,600 words.