Build · architecture profile

App Composer

Agent-operated app setup and independent app composition. An Astro and EmDash app on Cloudflare with service bindings for guestbook and showcase workloads.

LiveArchitecture reviewed 7 November 2026Dossier reviewed 12 November 2026

How it is built.

App Composer is a builder product with several runtimes behind one host. The main Worker serves the site and EmDash content, and calls separate guestbook and showcase services through bindings. Operator surfaces sit behind Cloudflare Access. The guestbook publishes an approved-items contract that Woodhouse reads.

Stack
Astro 7.4, React 19.3, EmDash 1.4, TanStack Router, Tailwind 4Evidence: package.json
Runtime
Worker `app-composer` with service bindings GUESTBOOK, SHOWCASE and GUESTBOOK_MEMBERS, an every-minute cron and Cloudflare AccessEvidence: wrangler.jsonc
Storage
D1 `app-composer-emdash`, R2 `app-composer-media`, KV `SESSION`; guestbook state belongs to its own serviceEvidence: wrangler.jsonc
Identity
Public read; /_emdash administration is guarded by a verified Cloudflare Access JWT with subject binding. No public user login lives in the main Worker. Guest contributions are moderated by the guestbook service.Evidence: src/lib/access-boundary.mjs; src/worker.ts; README.md
Delivery
Cloudflare custom domain composer.loftwah.com; the deploy script requires a clean pushed main and verifies the live originEvidence: wrangler.jsonc routes; scripts/deploy.mjs
Integrations
Resend for invited-recipient email; service bindings to the composed Guestbook and Showcase Workers; publishes the guestbook contract at guestbook.loftwah.com; exposes /api/portfolio-analytics to WoodhouseEvidence: wrangler.jsonc services; src/lib/resend-delivery.mjs; README.md; Woodhouse src/pages/api/guestbook-items.json.ts

The shape of the system.

  1. Main siteAstro pages and EmDash records describe the builder and its documented flows.Evidence: src/pages
  2. WorkerRoutes API requests, owns the cron and binds the companion services.Evidence: wrangler.jsonc; src/worker.ts
  3. Guestbook serviceA separately pinned Worker owns contribution, moderation and the published contract.Evidence: wrangler.jsonc services; README.md
  4. Showcase serviceA second binding serves showcase workloads without sharing the guestbook's state.Evidence: wrangler.jsonc services
  5. Access boundaryCloudflare Access protects operator surfaces instead of inventing a second login inside the app.Evidence: wrangler.jsonc vars CF_ACCESS_TEAM_DOMAIN

Engineering decisions worth knowing.

  • Services behind bindings, not more public APIs

    The guestbook and showcase workers are reached through service bindings, so the main app does not need a public network hop or a shared secret to call them.

  • Consumers read one approved contract

    Woodhouse does not read guestbook rows. It reads the published, approved-items contract, which keeps moderation and privacy in the owning service.

What it connects to.

  • WoodhouseApp Composerguestbook contract

    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

  • WoodhouseApp Composerportfolio analytics

    Woodhouse reads App Composer's public aggregate alongside the guestbook contract. Both are read-only consumer edges.

    Evidence: Woodhouse src/data/portfolio-analytics.ts

Authoritative public sources

What this review does not know.

  • The Guestbook and Showcase services are separately pinned Workers with their own upstream repositories; this review read their published contract and bindings, not their private source.
  • The every-minute cron's work was not observed directly in this review.
  • No contribution or moderation journey was completed for this profile.
  • The Access tenant and its subject binding were verified from configuration, not by signing in.