The knowledge inside Polaris

An AI producer is only as good as what it knows about the music. Polaris ships with 244 written technique packs and 67 machine-readable maps — and its agents are made to read the relevant ones before they are allowed to plan anything.

Written for this music

The library is not general music theory. It is electronic dance music and its bass-driven family, written at the level a working producer argues at: house, tech house, bass house, breakbeat, dubstep and 140, drum and bass and neuro.

It covers the things that actually decide whether a track works — how a kick and a sub share the low end, where a break earns its silence, what makes a drop land rather than merely arrive, how a groove is built and how it is ruined.

Two forms, on purpose

• 244 written packs. Prose an agent reads and reasons from, the same way you would read a good production article.
• 67 machine maps. The same craft as structured data — tempo ranges, drum signatures, arrangement shapes — so a claim can be checked rather than remembered.

The two are held against each other. A number in the prose that contradicts the map is a build failure, not a difference of opinion, and that check runs every time Polaris is built.

Reading is not optional

Polaris will not let an agent plan a full track without first studying the packs that job needs. The requirement is enforced in the software, not suggested in a prompt: no reading, no plan.

Each specialist gets the reading for its own job. The Drummer studies drums. The Bass Architect studies low end. The Genre Stylist studies the genre. And every instrument ships with its own reference guide, so the agents know how to play Nova, Infall and the Drum Machine specifically — not synthesis in the abstract.

It grows

The shipped library is the floor, not the ceiling. Polaris learns new technique from pages and videos you point it at, and keeps each new note with its source and a confidence rank. Your library and the factory library stay separate, so nothing you add can quietly overwrite what shipped.

The team that reads it

Fifteen agents, each with its own reading and its own tools: Drummer, Percussionist, Bass Architect, Sound Designer, Composer, Hook / Topline, Arranger, Automation Director, Mixing Engineer, Mastering, Genre Stylist, DJ / Crowd Flow, Reference Match, Producer’s Review, and the Producer that runs them all.

Two of those are auditors rather than makers. Producer’s Review checks the work against the brief before it reaches you. Reference Match takes a track you love and measures yours against it.