White labelhosaka fleet · pressing 001

Every service you listen on. One map.

A person’s listening is scattered across a dozen services in a dozen formats. taste cuts it to one plate: every artist resolved to one identity (a cluster_id) on the hosaka map, feeding a dashboard, recommendations, and a module apps can press in.

MATRIX · HSK-TASTE-A1 · RESOLVED IN pe-norm-v1 · ⌁ born on hosaka.fm
How it works

Three steps from scattered to mapped.

The same pipeline serves a listener checking their own taste and a product pressing music-taste in.

Step 1

Connect your sources

Link Last.fm scrobbles or a Discogs public collection by username — or drop in a screenshot from any service. taste reads the image in memory and discards it.

Step 2

Resolve to cluster_id

Every artist and release is matched against the hosaka map via crate’s public resolver. Unmatched items are labelled and shown — never padded into results.

Step 3

Your map: dashboard and recs

A timeline, collection, cluster view, and coverage dial — plus recommendations drawn from the same graph you resolved into.

How the resolver works →
Two sides · one pressing

For builders and for listeners.

The same cut serves a product that wants music-taste and a person who wants to see their own.

A-SIDE · FOR BUILDERS Live

Music-taste, drop-in

Your users link their services; you read their resolved cluster_id profile in the browser with their own bearer token. Your servers never hold their PII. One hosted connect-and-consent flow. One frozen, catalogue-numbered contract.

B-SIDE · FOR LISTENERS Dashboard Recs live

See your own taste, mapped

Your play timeline, your collection, your artist clusters, and how much resolved clean — plus graph-grounded recommendations with scene chips showing where each artist plays.

Etched in the run-out

The careful one.

taste is the hosaka fleet’s only PII-bearing service — isolated by design, not policy.

Isolated

Own encrypted stack, own keys — a taste incident structurally cannot reach the rest of the fleet (and vice versa). The no-PII fence is a CI gate, not a convention.

Reversible

Export everything, or delete everything, on demand. DELETE /api/v1/me erases your data in one structural cascade, rehearsed in CI on every change.

Discarded

Screenshots are read in memory — OCR runs, the image is thrown away. It is never written to disk. A zero-write test asserts this on every change.

MATRIX · PRESSING STATE

RECOMMENDATIONS LIVE · JULY 2026  ·  FIRST CONSUMER NINSEI  ·  CONTRACT V1, FROZEN: /contracts/v1  ·  FREE WHILE IN DUB-PLATE