ABOUT SORTCEROR
A PRODUCER SHOULD NOT HAVE TO BECOME A PLUGIN LIBRARIAN.
Sortceror began as an attempt to clean one impossible FL Studio Plugin Database, and evolved when identity, evidence, personal preference and safe action proved inseparable. You cannot organise what you have not understood, you cannot personalise what you cannot remember, and you should not move what you cannot restore.
THE ORIGIN, REPLAYED
From folder names to a system that understands.
This is the actual shape of the problem, replayed. One manual folder tree, and the eight layers of understanding that had to be built on top of it, in the order they proved necessary.
A taxonomy of moods: Unsorted, prism stuff, FINAL new. Eight records, three folders named in three different months. It was never going to hold.
Unsorted/
prism stuff/
FINAL new/
All names fictional · the same eight records, physically reorganised at every stage. Deliberately shorter than the Vision chapter.
THE ORIGINAL REFUSAL
NOT ANOTHER WAY TO MANAGE THE SAME WORK.
Most tools in this space give you a nicer place to keep doing the same maintenance. That was refused at the start. If the work comes back every month, the tool has not solved anything, it has redecorated the problem.
GOVERNING PRINCIPLES
Four laws, one instrument.
PRINCIPLE 01
Understanding before movement.
Nothing is proposed, let alone moved, until identity and function are genuinely resolved. Discovery is not intelligence.
PRINCIPLE 02
Personal preference is not universal truth.
Your corrections shape your library. They never silently rewrite what a product is for everyone else.
PRINCIPLE 03
Unknown is an honest result.
When evidence conflicts, the system abstains, visibly. Forced certainty is a defect, not a feature.
PRINCIPLE 04
The producer journey is the proof.
Passing tests is not the standard. A producer completing the real job, safely, on their real machine, is.
THE COMPLEXITY BOUNDARY
THE MACHINERY CAN BE INSANE. THE PRODUCT MUST FEEL EFFORTLESS.
Complexity must earn its place. Every mechanism exists to remove work, reduce uncertainty, or protect the producer. Otherwise it does not belong.
FOUNDER NOTE
I started Sortceror because plugin organisation had become its own recurring job. Every new install, version, format, and vendor naming change brought the same maintenance back again.
I was not looking for a more elaborate way to manage it. I wanted a system that could understand the library, remember useful corrections, act with restraint, and get out of the way.
What began as an attempt to clean up my own FL Studio Plugin Database became a much larger attempt to make plugin libraries progressively easier to live with.
CHASE
Founder and producer · written against the record, August 2026
THE PROJECT RECORD
One hundred and twenty pages of what actually happened.
A factual chronology, a design-history record, and a brutally honest post-mortem of the project's first 112 days. Dead ends included, because they explain the architecture better than the clean checkpoints do.
A BRIEF HISTORYOF ORDERED CHAOS THE COMPLETE DEVELOPMENT RECORD 07 MAY 2026 - 26 AUGUST 2026
CURRENTLY IN PRIVATE DEVELOPMENT
JOIN THE FIRST CIRCLE.
For Windows and FL Studio producers who want to be there when the circle opens: selected previews, material milestones, and the first opportunity to test.
Join Private Early Access