Product and architecture reference.
Product and technical documentation for artists, developers, investors, and evaluators: Casset's thesis, architecture reality, native App platform, roadmap posture, and diligence-level system references.
Core docs for first-pass diligence.
Read these first for the product story, architecture posture, generative-era trust thesis, roadmap, and investor-facing technical proof.
Product thesis
Generative-era positioning, artist homes, identity primitives, and agent-readable permissions.
Architecture
Stack overview, request lifecycle, release manifests, realtime layer, data model, and boundaries.
System reality
Source ownership, route posture, release infrastructure, peripheral systems, and claim verification.
Roadmap
Active priorities, parked bets, generative-era trust, and longer-term product direction.
Investor brief
Investor-facing narrative: artist identity, technical proof, readiness, and strategy.
Authored release objects, before and after circulation.
This is the deeper systems layer beneath Casset's public experience: how a cinematic release world stays contextual, permission-aware, attributable, and interpretable as it travels.
A casset keeps the song, visuals, credits, room energy, and permissions together before distribution turns the work into inventory.
Artists define how a release can be heard, referenced, remixed, interpreted, and carried into other surfaces.
Discovery can happen without losing source, attribution, atmosphere, or the routes that let value return to the artist.
Product primitives.
These terms define how product, engineering, roadmap, and investor documents refer to the same human experience and underlying release infrastructure.
Profile World
The artist home.A public music identity surface with atmosphere, Hook Objects, room state, provenance, release context, and social memory.
Hook Object
The media unit.A short audio window plus timing, lyrics/caption, visual world, waveform state, provenance, and share/reply affordances.
Release Ritual
The social launch layer.Presaves, rooms, fan clips, co-cassets, support, unlocks, and memory around a release moment.
Listening Room
Presence around sound.Conversation, comments, members, activity, and return energy around a profile, hook, casset, or release.
Profile dock: Music, Media, Moments, Room.
The mobile profile should lead with the core Casset loop instead of surfacing parked experiments. Samples remains available for desktop and legacy instrument workflows, but the public mobile dock now gives release Moments a first-class position.
Hooks and tracks
The default mode: hear a hook, browse the artist's songs, and keep the player anchored to sound.
Visual atmosphere
The cinematic surface for cover media, hook visuals, timed lyrics, and the authored world around playback.
Release memory
Fan-captured stills and clips tied to a release ritual, replacing the parked mobile Samples surface.
Presence and context
The conversation and archive-aware listening layer around the artist, release, and active hook.
Coverage map.
A compact index of the system areas covered by the public documentation.
Recommended reading paths.
Use these paths to reach the right level of product, technical, or strategic context quickly.
For investors
Start with thesis and system reality, then read the roadmap and investor brief.
For technical diligence
Trace architecture, Headless contracts, failure behavior, and secure audio delivery.
For product review
Review creator surfaces, hook behavior, living music video direction, theming, and commerce in context.
For Casset Apps
Start with the native App model, then trace host-owned runtime, playback, and current source truth.
For external developers
Choose Headless, run the local starter, then verify errors, retries, and availability before integrating.
Active public documentation.
Protocol, market, and creator-coin narratives are intentionally absent from this index. Quiet release infrastructure should support the artist identity thesis, not replace it.
The shortest path to thesis, architecture reality, roadmap, and diligence narrative.
Product thesis
canonicalGenerative-era positioning, artist homes, identity primitives, and agent-readable permissions.
Architecture
Stack overview, request lifecycle, release manifests, realtime layer, data model, and boundaries.
System reality
governanceSource ownership, route posture, release infrastructure, peripheral systems, and claim verification.
Roadmap
Active priorities, parked bets, generative-era trust, and longer-term product direction.
Investor brief
Investor-facing narrative: artist identity, technical proof, readiness, and strategy.
Long-form technical material for depth beyond the first architecture pass.
Casset Apps, APIs, playback, audio, commerce, and operational contracts.
Casset Apps
developer toolkitRepository-local SDK, three runnable starters, host contracts, permissions, lifecycle, and distribution truth.
Headless API
deployed · unsupported alphaVersioned public Artist and Catalog reads, SDKs, errors, retries, local sandbox, and exact availability.
Audiovisual playback
Playback clock, lyric timeline, visual environments, reactivity, and rendered artifacts.
Audio pipeline
Upload, blob storage, signed playback, preview enforcement, loop/fade behavior, and streaming.
Commerce
Support, unlocks, Apple Pay, Stripe Connect, rewards, refunds, disputes, and payouts.
Base anchoring
Quiet release-proof infrastructure for manifest hashes, provenance, receipts, and future licensing routes.
Creator-facing mechanics that explain how the product is authored and experienced.
How hooks work
Audio window, timing, atmosphere, provenance, room context, and sharing behavior.
Music video outsourcing
active conceptLiving music video system: distributed cinematography, fragment capture, beat-aware sequencing, and artist curation.
Theming
Cover-derived atmosphere, colors, profile textures, footer themes, and player skins.
Creator guide
Account setup, Profile World creation, hooks, atmosphere, support, and release flow.
Definitions and naming conventions for the rest of the documentation set.
Documentation standard
Describe what exists, name primitives consistently, keep experiments secondary, separate human experience from machine infrastructure, and verify roadmap or system claims against source files.