justinwhite.work

Primitive-Driven Design in Sherbet

Most enterprise work tools rot from the schema outward. Sherbet collapses customer support, feedback, and issue tracking into a small set of composable backend primitives.

by Justin White6 min read
Vol. I, No. ThreeReleased November 2026

What starts as a simple issue tracker in most organizations gradually accretes separate tables, bespoke APIs, and incompatible permission models for customer tickets, internal notes, feature requests, and project docs. Moving information from a frontline support inbox into an engineering sprint soon requires brittle glue scripts and webhook synchronization.

When we designed Sherbet as our first product at Koda, we anchored the architecture on a strict rule: every product surface must be a projection of a small, orthogonal set of primitives. Whether you use Sherbet through its first-party apps or as a headless backend-as-a-service API, the entire platform operates on uniform building blocks.

Unifying Discourse into a Single Message Primitive

In early iterations of our schema, we followed the conventional path with separate tables for internal issue notes, customer support messages, and team conversation replies.

We quickly realized these were not three different data structures. They were the exact same discourse primitive viewed through three different access lenses. Consolidating them into a single unified message primitive simplified the entire stack:

  • Polymorphic Thread Ownership: Every message belongs to a parent thread (an issue, support thread, or internal conversation), inheriting its tenancy and row-level security boundary automatically.
  • Unified Discourse Stream: Rather than splitting tables by who spoke, a simple origin type distinguishes internal team notes, customer replies, external webhooks, and automated state transitions inside one chronological stream.
  • Live Thread Rollups: Whenever a new message is appended to a support thread or conversation, Sherbet recomputes the parent thread's
    Glyph
    search signature from its message history, keeping the thread's context fingerprint continuously up to date.

Attachments as Connective Tissue

In traditional trackers, linking a customer ticket to an engineering bug is an afterthought bolted onto a single table. In Sherbet, relationships between entities are governed by a dedicated attachment primitive.

Any threaded entity can attach customer feedback, sibling issues, support threads, or internal conversations as chronological timeline events. Treating relationships as a first-class primitive unlocks two core workflows:

  • Hydrated Timelines: Querying a thread's timeline interleaves discussion messages, status changes, and attached customer signals into a single chronological narrative.
  • One-Click Promotion and Closed-Loop Resolution: Any support thread or feedback report can be promoted into an engineering issue in a single action that creates the ticket and binds the source signal. When an engineer marks that issue complete, Sherbet traverses the attachment graph in reverse to resolve linked support threads and notify affected customers.

Stateless Action-Dispatched Routing

Rather than maintaining dozens of sprawling REST paths, every primitive in Sherbet is served by a stateless edge router that dispatches against a uniform vocabulary of actions:

  • Core Lifecycle: Standard create, read, update, and remove operations with automatic fingerprinting on write.
  • Containment Queries: Fast contains lookups that hydrate all projects in an organization or all issues and assignees inside a project in a single round-trip.
  • Workflow and Discovery: Built-in transition, promote, attach, timeline, and
    related
    actions shared across every domain.

Scaling Surfaces Without Schema Sprawl

The payoff of primitive-driven design became clear when we introduced structured documentation and block-level editing. Because fingerprinting, tag indexing, role permissions, and action routing were already standardized at the primitive layer, documents plugged directly into the ecosystem, immediately searchable and linkable alongside issues, feedback, and customer conversations.