Portfolio / Creative Tech
TableMatch RPG Marketplace
A public, fit-first tabletop RPG marketplace pilot built around session discovery, private-group matching, approval-gated GM workflows, and fail-closed booking architecture.
The Challenge
Keeping session rules, capacity, booking intent, and payment recovery consistent under retries and partial failures without opening real-money flows before the platform and GM gates are proven.
System Architecture
A React and TypeScript client backed by Supabase Auth and Postgres. Row-level access, immutable booking contracts, signed-event verification, and idempotent recovery form the safety boundary; production remains behind the currently deployed migration set.
Marketplace Trust & Booking Flow
SPEC ID: TABLEMATCH-SYS-01
PHASE 01
DiscoveryFit-first Search
Surfaces schedule, tone, safety, material, and platform fit.→
PHASE 02
Session ContractRules Snapshot
Freezes the selected session rules for a booking attempt.→
PHASE 03
Booking BoundaryFail-closed Attempt
Rechecks capacity and payment state before completion.→
PHASE 04
RecoverySigned-event Reconcile
Uses verified, idempotent events to repair partial attempts.Implementation Notes
- The public pilot emphasizes schedule, tone, safety, material, and platform fit for recurring campaigns and private groups.
- Accepted source work adds immutable selected-session rules snapshots and private, exact-session Table Guides for booked players, with GM authoring and read-only admin moderation.
- Conflict-safe listing editing, governed catalog choices, payment recovery, capacity checks, and webhook handling are hardened in source; the newer guide, catalog, and payment migrations are not deployed to the public pilot.
Screenshots & Walkthrough

TableMatch RPG Marketplace
Lisbon Studio / 2026
Project Snapshot
- Role
- Forward-deployed product engineer
- Medium
- Marketplace prototype
- Format
- Web app case study
- Status
- Public pilot; real-money bookings remain gated
- Outcome
- Demonstrates fit-first discovery and trust architecture while keeping unproven payment, account, and production-data paths closed.
Project Metadata
- Location
- Lisbon Studio
- Year
- 2026
Keep looking


