Notebook session ended
This session ended after eight hours.
Sign in again to continue from where you left off.
Notebook gate offline
The sign-in service is not responding right now.
Wait a minute and try again, or read what is already public from the hub.
Foundational walk through the smo1 project. Read top to bottom if you're new; no prior context assumed.
More about this project on the Smo1 hub.
Use when: onboarding a new developer to the SMO1 codebase; explaining the architecture to a non-technical stakeholder; understanding the relationship between the six projects
Use when: debugging why a slug returns 404 instead of redirecting; understanding how the edge worker decides between redirect, proxy, and landing; explaining the request path to an infrastructure engineer
Use when: adding a new feature to purr-api; tracing a bug through the call stack; explaining the Go project structure to a new backend engineer
Use when: designing a new feature that touches users, links, or achievements; understanding the API response shape for the dashboard; debugging why a link shows the wrong status or score
Use when: debugging 401 errors across different clients; adding a new auth mechanism to purr-api; auditing the security surface of the API
Use when: debugging login loops or session expiry; understanding how meow-web authenticates without its own user database; implementing SSO with Airlock in another project
Use when: debugging why a slug does not redirect; understanding the edge worker's internal flow; optimising redirect latency
Use when: investigating inflated click counts; adding a new bot pattern to the edge worker; understanding how unique visitors are counted
Use when: debugging missing or duplicate click counts; understanding how analytics data flows from edge to warehouse; explaining the async tracking design to a product manager
Use when: deciding whether a stale redirect is a cache problem; planning to turn on the edge KV cache; explaining why redirect latency depends on purr-api
Use when: implementing password-protected links; debugging why a protected link shows a prompt instead of redirecting; understanding the edge vs. API split for protection
Use when: debugging 429 errors for specific users; adjusting rate limits for a new subscription tier; deciding whether a public purr-api route is protected from abuse
Use when: explaining link health scores to a user; debugging why a link's pawprintz dropped suddenly; designing new gamification mechanics
Use when: designing new achievement rewards; understanding why a user is level 7 instead of level 8; explaining the progression curve to a product designer
Use when: debugging why a user's tier did not update after payment; someone asks whether smo1 bills through Polar or TOLL; touching any billing route, the Polar webhook, or users.tier
Use when: planning to enable the Cloudflare KV edge cache; seeing 'KV sync service configured' in purr-api logs and wondering what it does; reviewing a change to link create, update or delete
Use when: implementing a white-label short link; debugging why a proxied page shows broken assets; understanding path rewriting at the edge
Use when: writing a migration or a production SQL check; deciding whether data belongs in Postgres, Redis or the click store; explaining which tables the TOLL switch leaves dormant
Use when: finding where a smo1 component runs and how it deploys; debugging a landing page that loops or 404s through the Worker; asking why a PR shows no checks in smo1 repos
Use when: adding a new UI label that needs both cat and professional versions; understanding why the dashboard uses words like 'Pawprintz'; explaining the dual-mode design to a designer
Use when: writing the smo1.io tagline or homepage hero; answering 'what category is smo1 in?' in one sentence
Use when: deciding which audience a campaign or page speaks to; writing copy that has to land for more than one segment at once
Use when: drafting the homepage hero or first-time visitor flow; writing an empty state, a decay message, or an error
Use when: writing a launch post or status update for smo1 V1-ALPHA; explaining what 'live' actually means for smo1
Use when: reviewing a smo1 design comp or marketing draft for drift; explaining why smo1 looks different from other shorteners
Use when: working on POST /api/links or anything in internal/x402; a paid caller reports being charged without getting a link; reviewing why the x402-anon user can never be logged in as
Use when: implementing or reviewing the purr-api TOLL sell-through; reasoning about when a smo1 tier change becomes visible; a paid user was downgraded or not upgraded and you need the intended rule
Use when: a dashboard call to purr-api returns 401, 500 server_misconfigured or 502 bad_gateway; rotating SERVICE_JWT_SECRET; adding a new dashboard page that needs purr-api data
Use when: provisioning or debugging petrova.smo1.io links; adding another custom domain to smo1; a custom-domain link resolves to the wrong destination or 404s
Use when: asking what still blocks smo1 from taking money; adding, discharging or re-targeting a launch gate; resetting the demo account before a support or sales call