Analytics
Each project on its own relevant measure
Discovery · measured hand-off
Bubbles4recorded project opens
Bubbles drew 4 recorded clicks from Woodhouse.
- Reporting period
- 24 Sept 2026 – 23 Oct 2026UTC · 30 days · current UTC day is partial
- Coverage
- Partial coverage · 9 of 30 days observedCollection began 15 Oct 2026
- Most recent seven days
- 417 Oct 2026–23 Oct 2026 · 7 of 7 days observed
- Earlier seven days
- Not claimedEarlier week incomplete
What this establishes. 4 recorded outbound clicks to Bubbles between 2026-09-24 and 2026-10-23 UTC, across 9 of 30 observed days.
What it does not establish
That anyone played, tried, subscribed or returned. A recorded click is discovery intent on this origin, not downstream use or a unique person.
A week-on-week comparison needs an exact counter for both complete seven-day windows inside the selected dates. Missing days are shown as gaps, never summed as zero.
Beyond the visit.
Rounds finished, music heard, links checked. Open a result to see its daily history, try the product and share that exact story.
2026-09-24 to 2026-10-23 UTC · same saved report throughout · today is partial

Protocol 11
0h 7m 38sClassic active gameplay
Partial coverage
Classic mode only. Accepted active gameplay seconds are not completed hands, scores or unique players. Read the selected window’s source coverage before comparing periods.
Explore this result
SHOALSHOT
2Reported completed runs
Partial coverage
Accepted terminal game/result transitions, including repeat runs. Client-reported activity is not a validated competitive score, catch or unique player.
Explore this result
Link Check × App Composer
25Completed Link Checks
Bounded count
Reported completed inspections, including repeat jobs. Bounded counters can omit activity. These are not unique people or proof of a composed owner workflow.
Explore this result
Bubbles
0Reported completed runs
Partial coverage
Reported terminal runs across supported games, not a count of successful board clears. Replay measurement is unavailable in this source, not zero. These are not unique players or best scores.
Explore this result
Fighter
107Reported fight completions
Legacy/test risk
Accepted non-tutorial fight results: win, loss, draw or forfeit, attributed to launch day. These are not wins or unique players. Consult the selected source coverage for historical verification risk.
Explore this result
LoftwahFM × games
7h 42m 34sAll-source audible listening
Legacy/test risk
Accepted audible music time across all admitted sources. This is not gameplay time or unique listeners. History before 15 October may include unmarked verification.
Explore this result
Available observations lead; legacy/test history and missing measures follow. Editorial order applies within each group, never the size of incompatible totals. Recorded activity is not a count of people. A zero is measured; “Not measured” means no retained evidence. Historical verification limits follow each result into its story and export.
What we noticed
3 findings from this report.
Chosen from this report only: the strongest complete-week movement, the busiest measured hand-off from Woodhouse, a source that started reporting inside these dates, then Woodhouse's own reading traffic. Where every number comes from.
Discovery · App Composer
7recorded clicks
The busiest measured hand-off from Woodhouse went to App Composer.
24 Sept 2026–23 Oct 2026
- What this establishes
- 5 in the most recent seven days. The earlier seven days recorded only 2 of 7, so no comparison is claimed.
- What it does not
- That anyone played, tried or kept using it: this counts the outbound action on this origin, not what happened at the destination.
New collection · App Composer
11days recorded
App Composer began reporting inside these dates, so this is the first comparable history it has.
from 13 Oct 2026
- What this establishes
- Everything before 13 Oct 2026 was never recorded. It is missing, not zero.
- What it does not
- That the product was unused before collection began, or that the first days are representative.
Woodhouse · its own audience
4,144visits
42 of those visits met the source's engaged-session threshold.
24 Sept 2026–23 Oct 2026
- What this establishes
- 4,144 anonymous tab sessions admitted, 42 engaged.
- What it does not
- How many individual people read anything, or whether they came back: both need a measure this source cannot supply.
What this report cannot show yet
- No two adjacent complete weeks are available in retained history for these dates.
This report is frozen at 2026-10-23 06:26 UTC. Refresh these dates · Latest 30 days
Project overview
One relevant measure per project · same UTC dates
Each project, on the measure that describes its use
Different measures with different units; the values are never added together. Open a project for its full view, or choose one measure for a single-scope chart and table.
Daily values & export
One row per project with its own relevant measure, unit and coverage. A dash means unavailable; the measures are not added together.
| Project | Measure | 2026-09-24 | 2026-09-25 | 2026-09-26 | 2026-09-27 | 2026-09-28 | 2026-09-29 | 2026-09-30 | 2026-10-01 | 2026-10-02 | 2026-10-03 | 2026-10-04 | 2026-10-05 | 2026-10-06 | 2026-10-07 | 2026-10-08 | 2026-10-09 | 2026-10-10 | 2026-10-11 | 2026-10-12 | 2026-10-13 | 2026-10-14 | 2026-10-15 | 2026-10-16 | 2026-10-17 | 2026-10-18 | 2026-10-19 | 2026-10-20 | 2026-10-21 | 2026-10-22 | 2026-10-23 | Total |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Fighter | Game starts | 4legacy | 0legacy | 2legacy | 17legacy | 92legacy | 21legacy | 0legacy | 0legacy | 2legacy | 3legacy | 2legacy | 0legacy | 1legacy | 14legacy | 0legacy | 0legacy | 0legacy | 0legacy | 0legacy | 0legacy | 0legacy | 0legacy | 0clean | 1clean | 0clean | 0clean | 1clean | 1clean | 0clean | 0partial | 161count |
| Bubbles | Game starts | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | 0partial | 0clean | 0clean | 0clean | 0clean | 0clean | 0clean | 0clean | 0partial | 0count |
| Protocol 11 | Game starts | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | 0partial | 0clean | 0clean | 1clean | 0clean | 0clean | 0clean | 0partial | 1count |
| SHOALSHOT | Game starts | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | 0partial | 0clean | 0clean | 1clean | 1clean | 0clean | 0clean | 0clean | 0partial | 2count |
| LoftwahFM | Audible listening | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | 13partial | 39legacy | 28legacy | 2legacy | 13legacy | 0legacy | 18clean | 347clean | 5,257clean | 5,176clean | 3,734clean | 4,219clean | 3,833clean | 5,075partial | 7.7hseconds |
| App Composer | Mini-app opens | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | 97bounded | 370bounded | 151bounded | 128bounded | 252bounded | 296bounded | 138bounded | 92bounded | 72bounded | 139bounded | 62bounded | 1,797count |
| Woodhouse | Visits | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | —missing | 4partial | 42clean | 20clean | 50clean | 118clean | 998clean | 526clean | 1,320clean | 1,066partial | 4,144count |
Can we compare these dates?
Coverage for each project's relevant measure. Colour describes evidence, not popularity.
The longest available comparable history in this selection is 7 complete daily observations. First collection days and today remain partial. Legacy activity may include tests that cannot be separated.
Where Woodhouse sends visitors
Recorded clicks from Woodhouse to a published project, for this period. A click is a referral: it shows discovery intent, not downstream play, adoption or a unique person.
This measures outbound clicks to Bubbles, Fighter, SHOALSHOT, Protocol 11, LoftwahFM, App Composer. Other published projects (MAX, Social Club, Asset Hunter) are outside this measured subset; their missing clicks are not zeroes.
The selected story is open at the top of the report. Return to Bubbles
Counts come from the same anonymous collection as Visits. Opt-out, blocked measurement and QA exclusion make them partial, and they do not show whether the visitor played, subscribed or came back.
Have browsers come back?
These are optional browser signals, kept separate for each project. They cannot identify people or establish cohort retention. Daily browser counts do not add up to a period total.
WoodhouseNot measured for these dates
DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Optional browser measurement has not yet received a consenting visit; browser counts are unavailable. Browser measures cover opt-in visits only and remain partial. Private project-scoped visit associations expire after 90 days; a window intersecting expired history is unavailable. Browser totals use retained period DISTINCT counts, never daily sums.
App ComposerNot measured for these dates
This source does not report browser returns. Tab activity cannot establish a returning audience.
Fighter0 returning · 0 reporting browsers
Distinct opted-in browser IDs observed in this window with an earlier different tab session in retained 90-day history (including same-day returns). Daily distincts are not additive; period totals are unavailable when the raw retention window is incomplete. Clearing/rotating IDs resets continuity; default tab-only visits are outside this cohort.
No opted-in browser was observed in this window. This zero cannot show whether the wider audience returned.
Inspect Fighter returnsSHOALSHOTNot measured for these dates
DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Browser returns are unavailable until this product releases its own optional consent client.
Protocol 11Not measured for these dates
DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill. Browser returns are unavailable until this product releases its own optional consent client.
LoftwahFMNot measured for these dates
This source does not report browser returns. Tab activity cannot establish a returning audience.
Bubbles0 returning · 0 reporting browsers
Opted-in browser IDs with a gameplay start in this window and an earlier different tab session in the retained 90-day run history. Same-tab replays excluded. Not human or installation retention; daily counts do not sum to period distinct counts.
No opted-in browser was observed in this window. This zero cannot show whether the wider audience returned.
Inspect Bubbles returns
What changed around this activity?
Dated release observations sit beside the collection and comparison boundaries reported by each source. Nearby dates suggest questions to investigate; they do not show that a release caused a change in use.
This is a reviewed selection, not a complete release feed. Notes are frozen with the report and may precede the selected dates; notes after its last selected day are omitted.
Explore 44 dated release and collection notes
- App Composer · The build story and the contribution invitation are live
The live /building article documents a real brief → Init specification → local Worker run, with real captures and editable diagrams. Guestbook commit 019ce0d117f9f89e472a5c7642d51d85301f7fcd publishes GET /r/:resource/api/invitation with open, paused, closed and full states, exact form paths and postcard limits; Linkarooie commit 20ef9a50c19c7a3419dc06fdae020c6a677ed5cf validates the contract and treats a malformed, redirected, foreign or partial response as unavailable. Approval and featuring remain separate. Woodhouse's source plate and contribution flow explain the same contract. The local fictional run is not a hosted deployment, and the invitation is a producer contract, not proof of a live owner configuration or adoption. Woodhouse's flow is a model of the published contract, not a production control.
Read release evidence · reviewed 2026-10-23 - App Composer · The approved Composer mark and share card are live
The live App Composer homepage declares product-og-20261022b.jpg at 1200×630 and the 20261022b icon set; its build identity is 41d488383031169ead44aab3be4d53b5abbf9096. The image was fetched and inspected (SHA-256 0ed47d3fea0628308dec42db8e294bd462c1d82b9092905a5b207df61b31afad). Woodhouse's project record, dossier, portfolio tile and share-image path now use the current image, tile SVG and describing alt text. Social-platform unfurl rendering remains externally unverified. The producer's live metadata and image bytes are verified. Woodhouse's adoption is a reviewed reference, not proof that every external social platform has refreshed its cache, that every consumer outside the producer uses the new mark, or that the identity earned customer demand.
Read release evidence · reviewed 2026-10-22 - App Composer · From a live example to your own starting point
The released demo sends Make this collection to Init’s composition recommendation without overwriting a saved draft. Independent browser interaction checked that explicit Use changes the form while preserving authored settings; the configuration can be downloaded with the two source pins. The live reference explains where to find its fictional sample and links back to the original guestbook item. This demonstrates the available configuration and handoff, not a new creator deploying a production collection or independent adoption. Source pins, privacy and owning release gates remain in force. Browser QA must use the supported verification header; bounded open counts can include unmarked inspection and are not demand evidence.
Read release evidence · reviewed 2026-10-18 - LoftwahFM · Listening follows the audio, not the visible page
The deployed collector uses native media time updates independently of the visible UI clock. With synthetic media and simulated hidden-page state, native media progression advanced the intercepted receipt while seek and mute stayed excluded. The sanctioned release and live browser checks bind to the named source. QA reporting requests were intercepted; no listening totals or history were added by those checks. This is bounded browser instrumentation evidence, not a personally identified listener or a physical-phone observation. Actual background and suspended playback, a real audible phone listen and its received Woodhouse count remain to be observed. Long browser-suspended gaps stay excluded and missing history cannot be recovered.
Read release evidence · reviewed 2026-10-18 - App Composer · The published pieces keep their own identity
Opaque credential and dotenv-comment regressions plus adversarial archive fixtures fail closed. The exact current production release and a separately bound preview passed negative credential-path and package-content checks. This is actual release-path and artifact coverage, not a guarantee against every secret format or proof that a new creator has completed onboarding. Private account state and migration work remain separate.
Read release evidence · reviewed 2026-10-18 - Bubbles · A game release checks what it publishes
The independently deployed game passed its normal release, exact candidate asset checks and deployed browser smoke. Safe negative probes returned six clean missing responses and three generic HTML fallbacks; actual output inspection supplies the artifact coverage. Generic HTML fallbacks are neither exposure nor proof of safety. Provider preview URLs remain disabled, so no addressable Bubbles preview is claimed tested. This guard release does not complete the broader gameplay qualification programme.
Read release evidence · reviewed 2026-10-18 - LoftwahFM · A playable connection with a copyable starting point
The sanctioned FM release and live guide, starter and artwork are checked against exact source. Independent browser checks cover initial silence, gesture playback, mute, pause and failure/retry across Chromium and phone/tablet WebKit profiles. The Woodhouse example serves from a separate origin. Browser time progression is playback evidence, not human listening or physical-device acceptance. The small prototype is not customer adoption and gives no redistribution licence.
Read release evidence · reviewed 2026-10-18 - App Composer · Creator profile and moderated guest path released
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Composer and independently deployed Linkarooie identities agree with the owning release record. Native owner Publish/Hide and Remove-confirm interaction remain partial; API curation and public visual checks are separate evidence.
Read release evidence · reviewed 2026-10-16 - Bubbles · Opt-in reporting and consent revocation released
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. The receipt-only main merge is separate from the deployed runtime revision. Later exact verification followed an initial propagation-related smoke failure. Owner-preview and scoped browser proof do not complete formal qualification or physical acceptance.
Read release evidence · reviewed 2026-10-16 - Fighter · Source-owned fight reporting and optional returns released
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Owning release and live public adapter checked. Browser identities are opt-in and partial. Historical QA exposure prevents clean pre-boundary growth comparisons; no new game playthrough or physical observation was performed here.
Read release evidence · reviewed 2026-10-16 - LoftwahFM · Native UTC listening windows released
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Live aggregate source and owning release checked. Audible receipts are separate from gameplay, sampled analytics and unique listeners. The broader unchanged React Doctor baseline failure remains distinct from the passing sanctioned release.
Read release evidence · reviewed 2026-10-16 - Protocol 11 · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- Protocol 11 · Comparison boundary
The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.
- Protocol 11 · Current table release and anonymous measurement source
Reviewed current canonical source and owning release evidence against the public destination on 16 October 2026. Owning source and release receipt reviewed. Synthetic production QA sent no engagement events; that exclusion is not evidence of real audience collection. The later phone clearance draft has not shipped.
Read release evidence · reviewed 2026-10-16 - Bubbles · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- Bubbles · Comparison boundary
The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.
- Fighter · Comparison boundary
The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.
- LoftwahFM · Comparison boundary
The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.
- SHOALSHOT · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- SHOALSHOT · Comparison boundary
The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.
- Woodhouse · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- Woodhouse · Comparison boundary
The source marks this cutover for comparable history. The first boundary day is excluded from complete-week records; later missing or partial days still matter.
- App Composer · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- Protocol 11 · Protocol 11 · later player-feature delivery
The qualified feature tree and deployed assets are recorded separately from later tooling/documentation. The public readiness endpoint independently reported production D1 and matchmaker ready. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The owning browser qualification is a frozen composite, not one uninterrupted full-suite run; actual-domain browser UI remained blocked. Source/runtime equality and live readiness are distinct from that interaction gate. The current v2 film is a disclosed one-round demonstration; broader campaign acceptance remains open.
Read release evidence · reviewed 2026-10-13 - Bubbles · bubbles · native result sharing
The later runtime carries the reviewed SDK 1.2 attribution implementation and native Classic sharing. Its owner-preview receipt covers sharing, player clearance and the unchanged service-worker bytes; earlier full audio proof remains separate. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. Owner-preview and scoped Chromium/WebKit receipts do not complete formal qualification. Classic export is not a verified uploaded score, a public result permalink or sharing for every mode. Prior full audio proof and later sharing/clearance proof are distinct.
Read release evidence · reviewed 2026-10-13 - Bubbles · bubbles · radio 1.2.0 release
The dedicated SDK 1.2 runtime receipt records exact deployment, native player/audio/attribution Chromium/WebKit journeys and explicit test/privacy exclusions. Later sharing and player-clearance proof stays separate. Dedicated owner-preview audio/attribution proof on this exact source. The later sharing release is not substituted for full playback verification. Formal qualification, held editorial/shared mix, real audience, physical device and human listening remain open.
Read release evidence · reviewed 2026-10-13 - Fighter · fighter · native result sharing
Exact-main Chromium/WebKit receipts cover real published media, excluded audible-progress reporting, saved shuffle and finished-result PNG/caption journeys. The public page build identifier independently matched this source. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The reviewed browser receipts use excluded test attribution. They prove scoped behaviour, not real audience listening, score verification or a completed variant platform.
Read release evidence · reviewed 2026-10-13 - Fighter · fighter · radio 1.2.0 release
Exact-main Chromium/WebKit receipts cover real published media, excluded audible-progress reporting, saved shuffle and finished-result PNG/caption journeys. The public page build identifier independently matched this source. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The reviewed browser receipts use excluded test attribution. They prove scoped behaviour, not real audience listening, score verification or a completed variant platform.
Read release evidence · reviewed 2026-10-13 - LoftwahFM · LoftwahFM · integrated listening and sharing reports
The release preserves the collector, SDK 1.2 compatibility and public snapshot/PNG contract. Later source 1cf08290 is distinct and has no fresh exact deployment receipt established here. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The public aggregate was re-read on 13 October and marked partial coverage. It contained no reported audible game starts or seconds in that window; that does not mean nobody plays. Adapter visits, active gameplay, unique people and willingness to pay are different measures.
Read release evidence · reviewed 2026-10-13 - SHOALSHOT · SHOALSHOT · generated artwork and sharing repair
The readable Share result control opens a reef-backed paper result card. The canonical social preview is 1200 × 630; the transparent wordmark is 1998 × 424 and emblem 1161 × 1161. Public originals are available from the project with A Loftwah Game credit. This is a presentation and local-sharing repair. It does not establish a public result permalink, uploaded score, new listening attribution or physical iPhone/native OS share-sheet acceptance. The original native-sharing evidence remains separately dated and versioned.
Read release evidence · reviewed 2026-10-12 - SHOALSHOT · SHOALSHOT · finished-dive sharing
Play a dive, open Pause, choose End Dive, then use Share result on the Dive Summary. Save a 1200 × 630 PNG, copy its caption or use your device’s share options when supported. The card includes the actual mode, rules and game version. The result is local and unverified. The card is made inside the game; no public result permalink, uploaded score, account or square/portrait result format is provided. Owning Chromium/WebKit receipts establish downloads and navigation; physical iPhone/native OS sharing remains pending. No listening adoption or popularity is inferred.
Read release evidence · reviewed 2026-10-12 - SHOALSHOT · shoalshot · native result sharing
The final menu release retains the existing SDK 1.2 integration. Owning production receipts cover the exact source, scoped fresh qualification and native menu click/keyboard/focus journeys, with earlier radio and finished-dive evidence separate. Woodhouse reviewed source and the owning receipts; it did not repeat game playback. Physical phone, human listening and native OS sharing remain separate acceptance. The menu release used the existing fixed presentation/FM qualification scope. The lazy radio adapter visit is not every game landing or a unique person. A measured audience trial has not run.
Read release evidence · reviewed 2026-10-13 - SHOALSHOT · shoalshot · exact radio deployment
Home and Pause offer six music stations and two presenter shows through the existing audio owner. Manual Shuffle, saved preferences, independent effects and local fallback preserve the fishing atmosphere. Physical iPhone and human listening remain open; narrow 320px dock labels need further composition work. Manual Shuffle is delivered; continuous shared My Mix is not.
Read release evidence · reviewed 2026-10-11 - Bubbles · bubbles · exact radio deployment
A stable, recoverable music dock exposes FM music, Original and Off, with saved controls and quiet reload. Presenter shows are discoverable through FM links while native editorial playback remains held. Owner-preview browser evidence does not complete formal qualification or physical iPhone/human listening. Native editorial remains held and shared continuous shuffle depends on FM #244.
Read release evidence · reviewed 2026-10-11 - Fighter · fighter · exact radio deployment
Menu, Settings and Library expose music and both shows. The game audio manager retains authored Battle, Results and Cinema priority, independent effects and opt-in speech; forkable branded versions retain their own presentation. Human listening and physical iPhone remain unobserved. Its current station shuffle does not establish the future shared My Mix contract; optional client 1.2 telemetry is not installed.
Read release evidence · reviewed 2026-10-11 - LoftwahFM · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
- LoftwahFM · LoftwahFM · games and radio discovery delivered
Merged PR #245 records the exact FM release, game catalogue links and aggregate measures that separate visits, playback starts, audible progress and referrals. Test traffic is excluded and games remain unranked while real observations are insufficient. Analytics capability is delivered; meaningful listener behaviour, demand, commercial value and telemetry adoption in every game are not established.
Read release evidence · reviewed 2026-10-11 - LoftwahFM · LoftwahFM · first original shows published
Both public edition pages expose the named shows, their dated publication, music and synthetic presenter scenes. The official station widget was inspected and real media playback advanced after an explicit Play action. Publication and browser media playback are established. Autonomous refresh, full format/acting qualification, human performance approval, physical-device acceptance and verified game adoption are separate gates.
Read release evidence · reviewed 2026-10-10 - LoftwahFM · LoftwahFM · supported client 1.0.0
The owning release records immutable archive integrity and compatible host audio ownership. Client 1.1 adds optional programme/part selection; 1.2 adds optional game analytics. Existing supported pins need no forced upgrade for ordinary music and whole-show playback. Explicitly reviewed releases only; this does not infer compatibility for every future 1.x version or imply that older consumers have installed newer optional APIs.
Read release evidence · reviewed 2026-10-11 - LoftwahFM · LoftwahFM · supported client 1.1.0
The owning release records immutable archive integrity and compatible host audio ownership. Client 1.1 adds optional programme/part selection; 1.2 adds optional game analytics. Existing supported pins need no forced upgrade for ordinary music and whole-show playback. Explicitly reviewed releases only; this does not infer compatibility for every future 1.x version or imply that older consumers have installed newer optional APIs.
Read release evidence · reviewed 2026-10-11 - LoftwahFM · LoftwahFM · supported client 1.2.0
The owning release records immutable archive integrity and compatible host audio ownership. Client 1.1 adds optional programme/part selection; 1.2 adds optional game analytics. Existing supported pins need no forced upgrade for ordinary music and whole-show playback. Explicitly reviewed releases only; this does not infer compatibility for every future 1.x version or imply that older consumers have installed newer optional APIs.
Read release evidence · reviewed 2026-10-11 - LoftwahFM · LoftwahFM · published music capability
The client archive was fetched and its package name, version and SHA-256 checked. Public station and game profile endpoints returned schema 1; profiles require client major 1, with music off and speech disabled by default. This record proves availability and compatibility of upstream music and the shared client. It does not establish game playback, physical-device acceptance or human performance approval. The separate original-show publication record covers the first curated editions.
Read release evidence · reviewed 2026-10-10 - Protocol 11 · protocol-11 · exact radio deployment
The Jukebox combines the original soundtrack, six FM music stations and two shows under one stream owner. Explicit Play, saved controls, bounded refresh and original fallback preserve table feedback. Physical iPhone and human audible acceptance remain open. Stable hand ordering, legal targets, Flaming feedback and desktop table visibility remain unresolved player-facing work.
Read release evidence · reviewed 2026-10-11 - Fighter · Collection began
First source-reported collection date. Earlier activity is unavailable; the first day may be partial.
Follow the numbers to their source
Every measure has a definition, a collection boundary and blind spots.
Woodhouse4 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-15T00:00:00.000Z
- Comparable history from
- 2026-10-15T00:00:00.000Z
- Source revision
- Not supplied
- Exact accepted event counters, not unique humans or anti-cheat proof. Blocking, opt-out, offline play and automated traffic affect coverage.
- DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill.
- Current UTC day and collection-start day may be partial. Cross-device retention, cohort retention and acquisition sources are not measured.
- Optional browser measurement has not yet received a consenting visit; browser counts are unavailable.
- Browser measures cover opt-in visits only and remain partial. Private project-scoped visit associations expire after 90 days; a window intersecting expired history is unavailable. Browser totals use retained period DISTINCT counts, never daily sums.
- Visits 4,144Reported activity
- One accepted visit marker per tab session; sessions reset after 30 minutes idle. Reloads in the same session do not add visits. Not distinct people.
- Engaged sessions 42Reported activity
- One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
- Active time 42m 44sReported activity
- Accepted 1–30 second foreground, unpaused activity increments, ending 30 seconds after trusted input. Server bounds total by session wall time. Radio time is excluded.
- Project discoveries 18Reported activity
- Accepted deliberate clicks from Woodhouse to a published project destination. Counts clicks, not visits received by that project.
- Reporting browsers —Not measured
- Distinct optionally consenting, project-scoped browser tokens with accepted visits in the selected UTC window. Period DISTINCT, not a sum of daily browser counts. Tokens rotate after 90 days; resets, multiple devices and privacy choices prevent interpreting these as people.
- Returning browsers —Not measured
- Distinct optionally consenting browser tokens with a visit in this UTC window and an earlier different accepted tab session in retained 90-day history, including same-day returns. Period DISTINCT, not a sum of daily returns. This is not cohort retention; expired earlier visits and token rotation hide returns.
App Composer5 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-13T00:00:00.000Z
- Comparable history from
- Not established
- Source revision
- 21c8f932d126d2fc0f8f6842b9596f0e32f867d0
- Daily counters stop at 1000 per app/event/surface and shared per-location rate limits may drop events.
- The first recorded UTC day is 13 October 2026 and is partial; daily counts expire after 35 days. Missing earlier history is unavailable, not zero.
- Optional publishers can lose events during outages. Marked verification probes are excluded; reloads, unmarked automation and bots can count.
- No visitor identity, sessions, return rate, private creator activity or vault contents are collected. Today is partial; these are bounded recorded signals, never lifetime totals.
- App opens 1,797Bounded count
- Successful public mini-app home-page HTML requests across standalone and composed versions. Reloads and bots may count; not people, sessions or conversions.
- Recorded app actions 78Bounded count
- Guestbook contribution-page opens plus accepted completed Link Check inspections. Different action types, not unique people or a conversion funnel.
- Guestbook contribution opens 53Bounded count
- Successful public Guestbook contribution-page HTML requests, including repeated opens; not image downloads, submissions, publications or unique people.
- Completed inspections 25Bounded count
- Link Check inspections counted by the owning app after completion; not clicks, deployment checks or unique users.
- Guest postcards received 2Partial measurement
- New pending guest postcards counted after committed acceptance by Guestbook, across connected standalone and composed routes. Not approvals, publications, unique people or a conversion rate. Before the first retained recorded receipt, history is unavailable. The first recorded UTC day is partial; later zero means no recorded receipt, not proof that nobody submitted. Optional recording can drop events.
Fighter8 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-08-09T08:22:36.602Z
- Comparable history from
- 2026-10-15T12:02:59.539Z
- Source revision
- Not supplied
- Historical counts before 15 October 2026 include unmarked production QA that cannot be separated or subtracted. These are stored reports, not a clean audience cohort; exclude pre-comparableFrom history from growth comparisons and records.
- Requested windows may include partial coverage. Current UTC day is partial. Stored browser reports are subject to privacy opt-outs, network loss and abuse controls; they are not unique people.
- Launch/completion counters backfilled only from the raw rows retained at migration; earlier expired history is unavailable. Anonymous daily totals are retained durably thereafter.
- Visits, engagement, deliberate Quick Fight replay and optional browser cohort measurement start 2026-10-15T14:34:02.048Z; earlier values are unavailable. Browser cohort rows and raw tab sessions expire after 90 days; anonymous daily counters remain durable.
- Active-time collection starts 2026-10-15T12:02:46.571Z; earlier time is unavailable. Individual raw game and session facts still expire after 90 days.
- Fight starts 161Reported activity
- Browser-reported non-tutorial fight launches; match IDs deduplicate retries. Exact accepted events, not verified humans.
- Completed fights 107Reported activity
- Launched fights ending in win, loss, draw or forfeit, attributed to launch UTC day. Abandonment excluded; not a completion cohort rate.
- Active gameplay 2m 5sReported activity
- Cumulative foreground, focused, unpaused fight seconds with input in the preceding 60 seconds. Loading/countdowns, hidden tabs, idle and radio excluded. Browser-reported, bounded by server elapsed time; launch UTC day attribution.
- Tab visits 3Reported activity
- Accepted random tab sessions first observed since this metric began; one per tab session (including reloads), attributed to first observation UTC day, with raw tab deduplication retained for 90 days. DNT/GPC, automation and explicit QA excluded. Not pageviews or people.
- Engaged tabs 3Reported activity
- Tab sessions reaching at least 10 cumulative measured active gameplay seconds across fights. Attributed to the tab visit UTC day; at most once per retained tab. Menus, radio, pause, background and idle time excluded.
- Deliberate Quick Fight replays 0Reported activity
- Accepted deliberate Quick Fight launches after an earlier completed or explicitly abandoned fight in the same tab. Prior terminal match ownership is checked by the server; retries deduplicate. Automatic progression, tutorial and other-mode replay actions are outside this measure.
- Opted-in browsers 0Reported activity
- Distinct random browser IDs voluntarily enabled in Settings and observed in this window; never humans. Off by default; expires/rotates after 90 days. Daily distincts are not additive; period totals use distinct retained IDs, not their sum.
- Returning opted-in browsers 0Reported activity
- Distinct opted-in browser IDs observed in this window with an earlier different tab session in retained 90-day history (including same-day returns). Daily distincts are not additive; period totals are unavailable when the raw retention window is incomplete. Clearing/rotating IDs resets continuity; default tab-only visits are outside this cohort.
SHOALSHOT6 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-15T00:00:00.000Z
- Comparable history from
- 2026-10-15T00:00:00.000Z
- Source revision
- Not supplied
- Exact accepted event counters, not unique humans or anti-cheat proof. Blocking, opt-out, offline play and automated traffic affect coverage.
- DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill.
- Current UTC day and collection-start day may be partial. Cross-device retention, cohort retention and acquisition sources are not measured.
- Browser returns are unavailable until this product releases its own optional consent client.
- Visits 8Reported activity
- One accepted visit marker per tab session; sessions reset after 30 minutes idle. Reloads in the same session do not add visits. Not distinct people.
- Engaged sessions 1Reported activity
- One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
- Games started 2Reported activity
- Accepted new game/dive start actions; restoring or resuming a saved game does not count. Client reported, not verified human play. Multiplayer tabs report participations, not distinct tables.
- Games completed 2Reported activity
- Accepted terminal game/result transitions. Client reported; not a validated competitive result. Multiplayer tabs report participations, not distinct tables.
- Deliberate replays 0Reported activity
- Accepted deliberate repeat new-game actions in the same tab session, after completion or abandonment. Automatic restores/resumes are excluded.
- Active time 0m 52sReported activity
- Accepted 1–30 second foreground, unpaused activity increments, ending 30 seconds after trusted input. Server bounds total by session wall time. Radio time is excluded.
- Reporting browsers —Not measured
- Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.
- Returning browsers —Not measured
- Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.
Protocol 1122 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-16T00:00:00.000Z
- Comparable history from
- 2026-10-16T00:00:00.000Z
- Source revision
- Not supplied
- Exact accepted event counters, not unique humans or anti-cheat proof. Blocking, opt-out, offline play and automated traffic affect coverage.
- DNT, GPC, designated QA and preview traffic are excluded. Production browser measurements start with this release; no historical backfill.
- Current UTC day and collection-start day may be partial. Cross-device retention, cohort retention and acquisition sources are not measured.
- Browser returns are unavailable until this product releases its own optional consent client.
- Mode subtotals come from the same accepted gameplay events as their overall measure: from the day the split begins, the mode subtotals sum exactly to that measure, and a day with no row for a mode is a measured zero for it. Before the split begins there are gaps, not zeroes, and raw history older than 90 days cannot be reconstructed.
- Visits and engaged sessions are tab session markers and are deliberately not split by mode: one tab session can span several modes, so per-mode session counts would overlap and double-count.
- Visits 14Reported activity
- One accepted visit marker per tab session; sessions reset after 30 minutes idle. Reloads in the same session do not add visits. Not distinct people.
- Engaged sessions 4Reported activity
- One accepted marker per tab session after at least 10 seconds of active product use. Foreground, unpaused and recent trusted input required.
- Games started 1Reported activity
- Accepted new game/dive start actions; restoring or resuming a saved game does not count. Client reported, not verified human play. Multiplayer tabs report participations, not distinct tables.
- Games completed 0Reported activity
- Accepted terminal game/result transitions. Client reported; not a validated competitive result. Multiplayer tabs report participations, not distinct tables.
- Deliberate replays 0Reported activity
- Accepted deliberate repeat new-game actions in the same tab session, after completion or abandonment. Automatic restores/resumes are excluded.
- Active time 7m 38sReported activity
- Accepted 1–30 second foreground, unpaused activity increments, ending 30 seconds after trusted input. Server bounds total by session wall time. Radio time is excluded.
- Game starts · Classic 1Partial measurement
- Accepted new game launches the client reported as Classic, excluding restores and resumes. Counted from accepted game_start events whose mode is classic. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
- Game starts · Journey 0Partial measurement
- Accepted new game launches the client reported as Journey, excluding restores and resumes. Counted from accepted game_start events whose mode is journey. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
- Game starts · Private room 0Partial measurement
- Accepted new game launches the client reported as Private room, excluding restores and resumes. Counted from accepted game_start events whose mode is private_room. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
- Game starts · Public matchmaking 0Partial measurement
- Accepted new game launches the client reported as Public matchmaking, excluding restores and resumes. Counted from accepted game_start events whose mode is public_matchmaking. Additive with Game starts: the four mode subtotals sum to that overall total. It does not mean distinct people, distinct tables or verified human play.
- Game completions · Classic 0Partial measurement
- Accepted terminal results the client reported as Classic, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is classic. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
- Game completions · Journey 0Partial measurement
- Accepted terminal results the client reported as Journey, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is journey. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
- Game completions · Private room 0Partial measurement
- Accepted terminal results the client reported as Private room, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is private_room. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
- Game completions · Public matchmaking 0Partial measurement
- Accepted terminal results the client reported as Public matchmaking, excluding restored results and Undo or re-scoring. Counted from accepted game_complete events whose mode is public_matchmaking. Additive with Game completions: the four mode subtotals sum to that overall total. It is not a completion rate: starts and completions in a window are not a matched cohort, and it is not a validated competitive result.
- Deliberate replays · Classic 0Partial measurement
- Deliberate repeat new-game actions in Classic inside the same tab session. Counted from accepted game_replay events whose mode is classic. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
- Deliberate replays · Journey 0Partial measurement
- Deliberate repeat new-game actions in Journey inside the same tab session. Counted from accepted game_replay events whose mode is journey. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
- Deliberate replays · Private room 0Partial measurement
- Deliberate repeat new-game actions in Private room inside the same tab session. Counted from accepted game_replay events whose mode is private_room. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
- Deliberate replays · Public matchmaking 0Partial measurement
- Deliberate repeat new-game actions in Public matchmaking inside the same tab session. Counted from accepted game_replay events whose mode is public_matchmaking. Additive with Deliberate replays: the four mode subtotals sum to that overall total. Automatic restores and resumes are excluded, and it does not say whether the earlier game was won or abandoned.
- Active play time · Classic 7m 38sPartial measurement
- Reported foreground play seconds while the active mode was Classic. Summed from the accepted 1–30 second active_time increments whose mode is classic. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
- Active play time · Journey 0m 0sPartial measurement
- Reported foreground play seconds while the active mode was Journey. Summed from the accepted 1–30 second active_time increments whose mode is journey. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
- Active play time · Private room 0m 0sPartial measurement
- Reported foreground play seconds while the active mode was Private room. Summed from the accepted 1–30 second active_time increments whose mode is private_room. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
- Active play time · Public matchmaking 0m 0sPartial measurement
- Reported foreground play seconds while the active mode was Public matchmaking. Summed from the accepted 1–30 second active_time increments whose mode is public_matchmaking. Additive with Active play time: the four mode subtotals sum to that overall total, and a session that changes mode contributes to more than one mode because each increment is counted once. Paused, hidden, inactive and radio time are excluded, and it does not establish a person's total play.
- Reporting browsers —Not measured
- Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.
- Returning browsers —Not measured
- Not measured: this product has not enabled optional browser-return measurement. Tab sessions cannot establish returns.
LoftwahFM4 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-10T00:00:00.000Z
- Comparable history from
- 2026-10-15T11:25:47.000Z
- Source revision
- Not supplied
- D1 counts are exact for accepted listening-v1 receipts, not independently audited people or exhaustive listening.
- Collection began 10 October 2026; aggregate history is retained for 185 days. Entirely pre-collection or expired windows are unavailable, never zero. Current UTC day and the first collection day are partial.
- Historical counts before 15 October 2026 may include unmarked production verification that cannot be separated or subtracted. Growth comparisons and records require complete dates after comparableFrom.
- Client delivery, opt-out, rate limits and uninstrumented/older clients may omit listening. Declared tests, preview, obvious bot/headless and DNT/GPC traffic are excluded.
- Legacy Analytics Engine milestones are excluded: that separate pipeline is adaptively sampled and retained for three months, so it cannot establish exact lifetime records.
- No browser identity is stored by listening-v1; distinct listeners, returning audience and retention are unavailable.
- Listening starts 283Reported activity
- Confirmed audible progression per random play receipt, deduplicated by the listening-v1 collector. All admitted FM site, game, widget and unknown sources; not unique listeners or gameplay starts.
- Audible listening 7.7hReported activity
- Accepted forward audible progression bounded by server elapsed time; excludes pauses, seeking, muted and stalled playback. FM native audio can report while the page is hidden; game adapters exclude hidden playback. All admitted listening-v1 sources, not gameplay time.
- Game radio starts 3Reported activity
- Confirmed audible radio starts explicitly attributed to admitted games; excludes game launches and gameplay starts.
- Game radio listening 0m 5sReported activity
- Accepted audible radio seconds explicitly attributed to admitted games; not gameplay duration.
Bubbles6 measures available
Live aggregate endpoint · generated
- Collection began
- 2026-10-15T11:33:11.547Z
- Comparable history from
- 2026-10-15T11:33:11.547Z
- Source revision
- Not supplied
- Current UTC day is partial. Stored browser reports are subject to privacy opt-outs, network loss and abuse controls; they are not unique people.
- Collection is opt-in and starts at this deployment. No historical gameplay is imported or invented. Anonymous daily totals are retained durably; pseudonymous run facts expire after 90 days.
- Active-time collection starts 2026-10-15T11:33:11.547Z; earlier time is unavailable. Raw gameplay run facts expire after 90 days.
- Gameplay starts 0Reported activity
- Opted-in gameplay starts at the first accepted shot/turn, or Snake start. Route visits and unplayed boards excluded. Random run IDs deduplicate retries; not unique humans.
- Completed games 0Reported activity
- Started runs reaching their actual game terminal result, attributed to launch UTC day. Quits and restarts excluded; not a completion cohort rate.
- Active gameplay 0m 0sReported activity
- Cumulative foreground, focused, unpaused gameplay seconds with input in the preceding 60 seconds. Loading/countdowns, hidden tabs, idle and radio excluded. Browser-reported, bounded by server elapsed time; launch UTC day attribution.
- Opted-in browsers 0Reported activity
- Distinct random opted-in browser IDs with a received gameplay start in the selected window. Browser reports, not humans; daily counts are distinct per day and do not sum to the period total.
- Returning opted-in browsers 0Reported activity
- Opted-in browser IDs with a gameplay start in this window and an earlier different tab session in the retained 90-day run history. Same-tab replays excluded. Not human or installation retention; daily counts do not sum to period distinct counts.
- Engaged opted-in tab sessions 0Reported activity
- Distinct opted-in tab-session IDs receiving at least 10 active seconds across runs started in the selected window. Daily thresholds apply separately to runs started each UTC day; daily counts need not sum to the period distinct count.
- Visits —Not measured
- Only opted-in gameplay is collected. Page visits and acquisition are not collected.
- Deliberate replays —Not measured
- A distinct replay action is not yet recorded; multiple starts are not assumed to be replays.
What am I looking at?
Each admitted project opens on the measure that describes its own use: gameplay for the games, listening for LoftwahFM, app access and outcomes for App Composer and audience discovery for Woodhouse. The measures have different units and are never added together. Choose a measure for a single-scope drill-down.
One row and one card per project, each on the measure its product view defines. The games, LoftwahFM, App Composer and Woodhouse report different units; the overview keeps them side by side without adding them together.
What does it tell us?
7 of 7 projects report their own measure for these dates. A project that reports nothing keeps its measure named and shows no value rather than a zero.
No clean growth comparison yet. New collection and legacy test traffic limit the history we can trust.
Last complete week
The most recent complete Monday–Sunday UTC week for each project's own headline measure, against the week before. A record needs exact daily history for two adjacent complete weeks; this is a valid comparison, not only the large movements that raise an operational alert.
No project has two complete comparable weeks yet, so no week-on-week figure is shown. Collection is too recent to compare honestly, and nothing is inferred from it.
Why some projects are not compared (7)
- Fighter: Fewer than two complete comparable weeks so far.
- Bubbles: Fewer than two complete comparable weeks so far.
- Protocol 11: Fewer than two complete comparable weeks so far.
- SHOALSHOT: Fewer than two complete comparable weeks so far.
- LoftwahFM: Fewer than two complete comparable weeks so far.
- App Composer: Mini-app opens is not an exact counter.
- Woodhouse: Fewer than two complete comparable weeks so far.
If you’re assessing the business
Early product instrumentation, with material evidence gaps.
- Usage
- 7/7 projects report their own measure. 7/7 sources provide some activity. Reports are not verified people.
- Retention
- No portfolio cohort-retention evidence. Returning browsers, where available, are a narrower signal.
- Commercial proof
- Revenue, paying customers, acquisition cost and customer value are not measured here.
Use this to ask better product questions. It cannot establish product–market fit, market demand or an investment case.
Read the product dossiersReport details
- Snapshot
- e36922f1f8a764888028b7d9
- Captured
- 2026-10-23 06:26:27 UTC
- Dates
- 2026-09-24 – 2026-10-23
- Time zone
- UTC; dates may differ from your local day
