A buy backlog and wishlist app — priority, estimated price, and a running planned-budget total. The future tense of the Jawnverse: mark an item bought and it graduates into jawntrack's ownership ledger via a typed event. Live at log.jawncloud.com.
GSV-A7·⬡
jawnlog
jawnlog is a buy backlog — a running list of things a person plans to purchase, each carrying a priority (must, want, someday), an estimated price, and a running total against a planned budget. It carries General Systems Ventures designation GSV-A7·⬡ within the media-ecology pace-layer, and functions as the deliberate, forward-looking half of a two-app ledger: jawnlog answers what a user plans to buy, while its sibling jawntrack answers what a user already owns. The two are timed halves of one ledger rather than overlapping products, each responsible for a different tense of ownership. The real mechanism is the graduation event: when a backlog item is marked bought, jawnlog emits a typed GraduationEvent (defined in lib/model.ts), which jawntrack is meant to reconcile against the matching receipt email, converting a plan into proof of ownership without either app duplicating the other's data store. Brand references link out to the shared jawnbase catalog rather than being modeled locally. This typed-event-plus-shared-substrate pattern is consistent with the rest of the Jawnverse family: individual apps emit facts, and a common substrate does the interpretation and reconciliation. On the architecture side, jawnlog uses Clerk for authentication, now load-bearing in practice — app/sign-in, app/sign-up, and lib/auth.ts are live — with a fallback open mode only when Clerk keys are absent. Persistence moved beyond an original localStorage prototype to per-user server-side storage: one JSON file per Clerk user, stored under ~/.local/state/jawnlog/backlogs/, keyed by clerkUserId and versioned to support forward migration. This is a deliberately lightweight subset rather than a database, and the codebase itself notes a follow-up path toward a shared Postgres table once broader jawnbase infrastructure is ready. Current status: functional single-user-file persistence with authentication in place, graduation-event emission implemented, and the jawntrack-side reconciliation and shared-database migration still pending.