Portfolio architecture
Twelve products.
Separate systems.
Woodhouse publishes the record, not the machine room. This atlas explains how each project is actually built, which ones share a capability, and what nobody has verified yet.
Reviewed 7 November 2026. Project identity and lifecycle come from the reviewed Woodhouse catalogue. Architecture facts come from each project's own source tree and public deployment. This is a dated projection of that review, not a live code scanner.
Looking for something to use? The project dossiers are the product record. Want to try a working connection? The Factory is the bench. This page is the engineering underneath both.
- Live: a public route answered at review
- Demo or prototype
- Planned, not serving
- Unknown or withheld
The whole portfolio on one plate.
Every project in the current catalogue, grouped by what it does, plus the publisher. The plate draws the shared capability the source proves; the ledger below carries every verified relationship, including measurement and contract reads.
Read the diagram in text
Play — Games you can open today, or pause and keep in the record.
- Bubbles: Deterministic bubble puzzles with a shared radio Status: live.
- Fighter: Authored character journeys with a small D1-backed service Status: live.
- SHOALSHOT: Mobile-first fishing arcade with a shared radio Status: live.
- Protocol 11: A responsive card table with rooms and matchmaking Status: live.
- Pirates: A source-first reconstruction of Master of the Secret Sea Status: unknown.
Listen — Music, stations and the shared radio capability.
- LoftwahFM: A music platform and the portfolio's shared radio capability Status: live.
Build — Tools for making, finding and composing things.
- Asset Hunter: A rights-aware catalogue of reusable assets Status: live.
- App Composer: Agent-operated app setup and independent app composition Status: live.
Collect — Personal catalogues and public showcases.
- Foilbury: A showcase for collectible cards and cabinets Status: live.
Everyday — Software that helps outside a game.
- MAX: A connected companion for an existing walker Status: live.
- Plans With You: Calendar protection that plans a cancellation Status: live.
- Liferaft: Offline desktop recovery for large .mbox archives Status: live.
Verified capability relationships
- Bubbles uses the radio client from LoftwahFM: radio client 1.2.0.
- Fighter uses the radio client from LoftwahFM: radio client 1.2.0.
- SHOALSHOT uses the radio client from LoftwahFM: radio client 1.2.0.
- Protocol 11 uses the radio client from LoftwahFM: radio client 1.2.0.
Every project, by what it does.
Each row opens a profile with the stack, runtime, storage, identity, delivery route and the unknowns. 12 of 12 catalogue projects are assessed in this review.
Showing 12 of 12 catalogue projects.
Play
Games you can open today, or pause and keep in the record.
Listen
Music, stations and the shared radio capability.
- LoftwahFMArchitecture
A music platform and the portfolio's shared radio capability
- Astro 7.1
- R2 media
- Analytics Engine
Build
Tools for making, finding and composing things.
- Architecture
- App ComposerArchitecture
Agent-operated app setup and independent app composition
- Astro 7.4
- EmDash 1.4
- Service bindings
Collect
Personal catalogues and public showcases.
Everyday
Software that helps outside a game.
Where the projects actually connect.
Most of this portfolio is independent by design. These are the relationships the source proves. Everything else is a link between pages, not a runtime dependency.
Bubblesuses the radio client fromLoftwahFMtwo-way
Bubbles pins @loftwahfm/radio-client 1.2.0 for station and queue state, and its host audio manager keeps effects, volume and mute. The same client sends anonymous listening-v1 events back to LoftwahFM, which makes this pair two-way without a shared account.
Evidence: Bubbles package.json dependency URL; src/app/music-transport.ts; LoftwahFM packages/radio-client/src/telemetry.ts
Fighteruses the radio client fromLoftwahFMtwo-way
Fighter pins the same client and the pressure-system station profile. The client sends the game's anonymous listening events back to LoftwahFM; Fighter keeps its own audio graph.
Evidence: Fighter package.json; LoftwahFM docs/radio-game-integration.md game profile table
SHOALSHOTuses the radio client fromLoftwahFMtwo-way
SHOALSHOT pins the same client with the low-tide station. Its adapter supplies the game id and origin, and listening-v1 events go back to LoftwahFM so the telemetry distinguishes a real deployment from a test.
Evidence: SHOALSHOT package.json; src/platform/radio.ts; LoftwahFM docs/radio-game-integration.md
Protocol 11uses the radio client fromLoftwahFMtwo-way
Protocol 11's jukebox pins the same client with the cartridge-club station. The client owns station selection and queue state and sends anonymous listening events back to LoftwahFM; the table keeps volume and effects.
Evidence: Protocol 11 package.json; src/client/jukebox.ts; LoftwahFM docs/radio-game-integration.md
Protocol 11reports anonymous play toWoodhouse
The client posts woodhouse.engagement/1 events to Woodhouse without credentials. A failed report cannot block a turn; the game stays playable if the hub is unavailable.
Evidence: Protocol 11 src/client/gameplay-analytics.ts; Woodhouse src/worker.ts /api/engagement; src/data/engagement.ts
SHOALSHOTreports anonymous play toWoodhouse
SHOALSHOT posts the same woodhouse.engagement/1 contract for its dive mode only after consent. The report is fire-and-forget and carries no account.
Evidence: SHOALSHOT src/platform/gameplay-analytics.ts; Woodhouse src/data/engagement.ts
Woodhousereads the published contract fromApp Composer
Woodhouse reads App Composer's approved guestbook items through its own read-only pass-through and falls back to a checked-in snapshot. The Guestbook is a separately deployed app composed by App Composer; it keeps moderation and media, and Woodhouse never reads its rows.
Evidence: Woodhouse src/pages/api/guestbook-items.json.ts; App Composer README.md and wrangler.jsonc service binding
Woodhousereads the public aggregate fromFighter
Woodhouse reads Fighter's /api/portfolio-analytics aggregate instead of collecting the game's events itself. The schema is woodhouse.portfolio-analytics/1.
Evidence: Woodhouse src/data/portfolio-analytics.ts; Fighter worker/portfolio-analytics.ts
Woodhousereads the public aggregate fromBubbles
Woodhouse reads the aggregate Bubbles serves from its cloud Worker at api.bubbles.loftwah.com; the game's cloud profile and score data stay in its own D1 database.
Evidence: Woodhouse src/data/portfolio-analytics.ts; Bubbles src/cloud/routes/portfolio-analytics.ts; wrangler.cloud.jsonc
Woodhousereads the public aggregate fromLoftwahFM
Woodhouse reads LoftwahFM's portfolio-analytics aggregate for listening context, and reads station manifests for the patch-bench exhibit. It does not read the underlying listening events.
Evidence: Woodhouse src/data/portfolio-analytics.ts; src/scripts/exhibits/patch-bench.ts; LoftwahFM API
Woodhousereads the public aggregate fromApp Composer
Woodhouse reads App Composer's public aggregate alongside the guestbook contract. Both are read-only consumer edges.
Evidence: Woodhouse src/data/portfolio-analytics.ts
Four systems, taken apart.
The profiles are not one checklist copied twelve times. These four carry a longer explanation because their engineering is materially different from the rest.
- BubblesRead the deep dive
Two Workers with different jobs, and a save that exists before sign-in — the opposite of an account-first game.
- Protocol 11Read the deep dive
The only project here with live multiplayer state, and a concrete reason for each stateful component.
- MAXRead the deep dive
Software, a device service and a physical prototype: the widest gap between what is hosted and what is claimed.
- LoftwahFMRead the deep dive
A media service with immutable versioned consumers, four schedules and an unusually narrow telemetry contract.
What this atlas can tell you.
A verified value was read from that project's own configuration or source at the review date, or observed from its public deployment. Each profile names the evidence beside the claim.
A relationship is drawn only when the consumer's source or a published consumer contract proves it. A shared colour, a link in a footer or a product idea is not a relationship.
What it cannot tell you.
This is not a live inventory. It does not read private repositories at request time, prove production health, or turn a README ambition into a shipped node. Unknown means nobody has verified it for this review.
Deployment status and product lifecycle are separate: a retired product can still serve a page, and a live page is not evidence of current development. Woodhouse's own architecture explains how this published record is produced.