jawncloud
The reusable catalog, wardrobe, and marketplace substrate for the Jawnverse: canonical brand/SKU/measurement data, owned/wanted item tracking, and a peer-to-peer resale marketplace. Also becoming the shared identity provider for its sibling apps.
jawncloud (GSV-D4·⬡) is the reusable style, catalog, and wardrobe substrate underneath the Jawnverse, and — per its architectural direction — is becoming the shared identity provider for that whole portfolio. It owns the primitives an outfit or resale app shouldn't have to reinvent: canonical brands and SKUs, materials, colorways, seasons, and measurements; owned/wanted wardrobe tracking with size, condition, and sale state; fit media and reference boards; and a peer-to-peer marketplace with reputation and payments. The guiding framing is a division of labor: jawncloud remembers the clothes, while applications like Vibecology interpret style on top of that memory. The repository is mid-migration on two fronts simultaneously. Its database layer is moving from Supabase-adjacent assumptions to Neon Postgres via Prisma. Its auth layer is moving from a working Supabase OAuth path (Discord, Google, a real callback route) to Clerk, reviving a `clerkUserId` schema field that existed from the start but was never wired up. Catalog and measurement browsing remain public by design; wardrobe state stays private by default. The larger architectural decision is that jawncloud becomes the single identity provider for the entire Jawnverse: rather than each sibling app (jawnfit, jawntrack, jawnlog) owning independent auth and improvising its own behavior when credentials are missing, they verify sessions issued by one shared Clerk instance via satellite domains, gated behind an explicit allowlist during closed beta — centralizing an identity discipline the same way jawnbase centralizes catalog-trust discipline. Related GSV projects include jawnbase (the catalog engine jawncloud serves as backend for), jawndex and jawntrack (which jawncloud's catalog and instance data feed), jawnfit, and Vibecology, the styling-layer application built atop this substrate. Status: both the Postgres/Prisma migration and the Clerk identity migration are actively in progress, not yet complete, alongside a working legacy Supabase auth path still in place.