Owner & Identity foundation
Authentication/session handling, Handle claim, Basic Identity Working persistence, starter composition, profile media foundation, and Identity connections are implemented.
←All WorkProject 01 / 2026
Spall Spill.
Product DesignProduct StrategyWeb Development
Spall Spill is a creator- and owner-centric identity and structured discovery platform in active production implementation, with authentication, onboarding, Working-state persistence, Product/Resource draft foundations, publication foundations, URL safety, media sanitization, and security/testing infrastructure already integrated.
Technical Overview
Year2026
Period2026 / Active Development
Role
Full-Stack DeveloperProduct Designer
StatusIn Development
Stack
Next.jsReactTypeScriptPostgreSQLSupabaseCloudflare R2VitestPlaywright
Database
PostgreSQLSupabase
Testing
VitestPlaywright
Engineering Highlights
- Tested PostgreSQL RLS and authenticated server-side mutation boundaries
- Draft-to-preview-to-publish workflow with staged first-publication transactions
- Stale-write protection for concurrent editing
- Destination-safety scanning and dedicated media sanitization services
- CI gates with Vitest, Playwright, pgTAP, type checks, and security scanning
Current Implementation
Active production implementation is underway..
Spall Spill has moved beyond product definition into active implementation. The current codebase already includes authentication and session foundations, Handle claiming, Basic Identity Working persistence, profile media foundations, Identity connections, Product and Resource draft foundations, stable Spill references, private preview, staged publication foundations, public-reader foundations, a dedicated URL safety scanner, a media sanitizer service, and automated CI/security gates.
The product remains In Development because the final first-publication wiring, remaining public/click/media transport, Product publication preparation, universal workspace handoff, browser/journey verification, live-provider verification, and release hardening are still being completed.
What Spall Spill Is
Identity for presence. Spill for structured discovery.
Every owner can publish a public Identity that works on its own: a personal or business presence built from structured profile, social, link, contact, media, text, and Spill CTA capabilities.
A Spill is the owner-scoped discovery layer behind that Identity. It can contain structured Product and Resource entities, each with its own persistent reference, lifecycle, public detail, and destination behavior.
Product represents a recognizable recommendation connected to one or more marketplace destinations. Resource represents structured material such as a menu, price list, catalog, portfolio, media kit, document, or external website. The entity remains stable even when the destination changes.
Core Product Principle
One owner. One Identity. One Spill. Multiple structured ways to be discovered.
Universal Capability Model
The product adapts to intent without turning intent into a permanent account type.
Onboarding can begin from Personal, Affiliate / Product Recommendations, Business / UMKM, Creator, or Other. That choice changes guidance, starter composition, and workspace emphasis — not permission.
A Personal user can later add Products. A Business owner can later publish Resources or Products. A Creator can begin with Identity only and expand into Spill when it becomes useful. Capability expansion is additive, so users do not need account migration or full re-onboarding when their needs change.
The same principle continues after onboarding: actual usage, navigation exposure, and authorization remain separate concepts.
Implementation Progress
Core product foundations are already built into the active codebase.
The project is now measured by implemented system boundaries and verified engineering foundations, not only by product-definition scope.
Spill data foundation
Product and Resource draft foundations, stable non-reused Spill references, private preview, and staged publication foundations are present in the active repository.
Safety & verification
URL safety scanning, media sanitization, PostgreSQL security tests, CI, SAST, secret scanning, and dependency scanning are integrated while final public transport and live-provider verification remain open.
Behavior Before Interface
The hard part is not drawing screens. It is defining what every state means.
Spall Spill separates Draft, Working, Saved, Published, Hidden, and Archived behavior so editing never silently changes the public state. Autosave protects work, while publication remains explicit.
Persistent Spill references are stable and never recycled. Exact reference lookup such as #27 has priority over fuzzy search, while normal keyword discovery remains forgiving and scoped to the current owner's Spill.
Identity, Product, and Resource are treated as durable product entities rather than temporary collections of links. Authentication is kept separate from authorization, owner preview is excluded from normal audience analytics, and marketplace clicks are recorded as outbound actions rather than assumed purchases.
Current Frontier
From product definition into active production implementation.
The clean production codebase is already carrying the core owner, identity, draft, preview, safety, and publication foundations. The next work is focused on final first-publication wiring, public/click/media transport, Product publication preparation, universal workspace handoff, remaining browser/journey verification, live-provider verification where available, and release hardening.
View source code↗Next Project
02 / 055AM Vision
Brand IdentityArt DirectionDigital Design