Built to be used.

A real creator home, clearer four-seat card play, and activity reports that ask what happens after a release. Each product keeps its own meaning and its own next proof.

Evidence reviewed 2026-10-16
Filed under
Portfolio report
Source state
Editor-reviewed public summary

The factory has more to show than a deployment: a creator home to visit, a postcard to leave, games to play and listening to inspect.

A home for the things I make.

Loftwah’s Linkarooie profile now brings curated links and a pinned App Composer milestone into a creator home. Guestbook sits beside it: a visitor can contribute a pending postcard, while approval and private records stay with the owner. These are independently owned apps, also composed together in App Composer.

The useful demonstration is a real personal stack built from reusable parts. App Composer keeps its own product identity; another creator should eventually be able to follow the same path. The published reference is one working example, with fresh-user setup and the complete private creator dashboard still unfinished.

Visit Loftwah’s Linkarooie

Open Loftwah’s guestbook

Explore App Composer

What happens after the deploy?

A release tells us what is available. The next question is what somebody does with it: starts a fight, finishes a table, listens to the radio or sends a postcard. Woodhouse now lets a reader inspect those different signals, choose dates and take away a frozen report with an image, caption and permalink.

The chart keeps each product’s meaning. Games start with game starts; App Composer starts with app opens; radio reports audible listening. Adding them into one engagement score would erase what was actually measured.

Explore the activity workbench

See the app activity view

Play, finish, choose another.

Fighter’s report separates fight launches, terminal results and active gameplay. Its replay signal is deliberately narrow: another Quick Fight after an earlier same-tab terminal fight. Optional browser recognition is off by default. Bubbles reports an opted-in population and now handles consent revocation even when browser storage cannot be changed.

Those signals can help answer practical questions about a game’s flow. They do not identify people, prove cohort retention or establish commercial demand. Earlier QA exposure and fresh collection dates limit which periods can fairly be compared.

Read Fighter’s current record

Read Bubbles’ current record

A smaller table, clearer play.

Protocol 11 now deliberately seats two to four players total. Hand sorting, Journey and bot changes, remote-state guidance and readable desktop drop refusals improve the released table. Anonymous gameplay reporting is present in the current production source; excluded QA runs establish no real audience activity.

A later phone-hand clearance change remains a draft awaiting qualification. It belongs on the next-proof list, not in a description of the live game.

Play Protocol 11

Read the table’s evidence

The dive counter has to earn its release.

SHOALSHOT’s source can now report anonymous regular-dive starts, terminal summaries, repeat play and active seconds. Practice and Zen stay outside that definition. Updated Settings geometry evidence describes the actual measurement disclosure.

That work has not cleared the game’s combined release gate. The existing game and finished-dive sharing remain available, but a healthy Woodhouse endpoint cannot prove the new game client is deployed. The source implementation and the live product keep separate labels.

Open the current SHOALSHOT dossier

Listening has its own clock.

LoftwahFM reports accepted audible progression and listening starts from its source-owned aggregate store. Selected UTC windows, retained history and the start of comparable coverage travel with the figures. Radio listening stays separate from active game time.

Older unmarked production checks cannot be identified and subtracted after the fact. That history stays visible with its limitation; complete comparable periods must accumulate before it can support a clean growth claim.

Listen to LoftwahFM

Inspect the listening view

The next useful test is small.

For the creator stack, the cheap next check is whether a new visitor can find a game or music and understand the guest contribution boundary. For the games, inspect comparable post-collection starts, finishes and deliberate replay signals before changing a journey. These are validation questions, not findings about an audience.

No promotion campaign, paid service or new product identity is required for that check. The held phone build, native owner interactions, physical play, human listening and broader creator workflow each retain their own next proof. Pirates, MAX, Club and Asset Hunter keep their earlier dated records.

Browse the share gallery

Read measurement definitions and choices

Source and review

MP-supplied portfolio and creator-stack notes reconciled with current canonical product source, dated owning release and browser receipts, public creator pages and source-owned aggregate endpoints on 16 October 2026. Public-safe derived conclusions; no private report, profile inventory or account material is reproduced. The publication does not reproduce private repository bodies or conversation transcripts.

Back to the dispatches

What changed

Publish something useful, make it easy to try, then measure the action it actually supports.

Proof boundary

Reviewed 2026-10-16. This is an edited public record, not a private source transcript.