week 3: thekitty took 2nd, an add-to-sofia capture flow, and a studio site
third log. one result landed, one feature got interesting, and i took a detour into pure design.
what i shipped
thekitty finished 2nd overall in the gnosis circles hackathon. official, on the garage leaderboard. the weekly grind (2nd in week 2, then re-entering every week) actually paid off at the finale. not 1st, but i'll take it.
sofia got an "add to sofia" flow: right-click anything on the web, it drops into a cart with atom search, and any missing context atoms get auto-minted at submit. shipped extension v1.2, plus an explorer onboarding tour, hover-to-redeem chips, and optimistic adds that survive indexer lag. the real work was the taxonomy underneath: a canonical context-atom payload plus a hybrid resolver, so capturing everything doesn't drown the graph in near-duplicates.
ourglass grew a proper biller / redeem console. the part i care about is an error mapper that turns reverts, RPC failures and wallet rejections into messages a human can act on, instead of a hex blob. also a live-ticking claim amount, a one-click network switch, and subscription cap semantics (end date + total budget, proportional).
a hard left turn: OddWave Studio
i'm also building a design-led site for a mastering and sound-design studio (tied to Sleeping Tracks Records). wired 47 releases to their spotify covers with an embedded player, a "retour vidéo" scrollytelling section that reveals text over an IPFS feedback video, a sound-design reel. it's the most design i've done in a while, and a good reminder that i don't only do crypto.
what i learned
the add-to-sofia feature forced a real taxonomy decision. letting users capture anything is easy; not flooding the graph with near-duplicate atoms is the hard part. the canonical payload + resolver is what makes it safe, and that one constraint shaped the whole feature.
ourglass taught me that in a self-custody flow the UX is the error handling. no support team, no undo: a legible revert message is the product. i'd underinvested there, and it showed.
what's next
- sofia: get add-to-sofia in front of real users and watch what they actually capture.
- oddwave: ship the studio site.
- arp: still nailing the ontology on the atlas before the code. it's the foundation, so i want it right.