Curating the knowledge base

The catalogue is curated by hand, and it gets better when you tell us what's wrong or what's missing. There are two in-app ways to do that — no email, no contact form:

• Flag a library you own when its metadata is wrong.
• Request a library that isn't in the knowledge base yet.

Both go to the same review queue and notify the DawForge librarians directly.

Flag a library for review

When a library you own has wrong articulations, missing patches, or broken metadata, flag it so a librarian can fix it.

1. Open /search and find the library.
2. Expand the library card and look at the footer — there's a Flag button in the bottom-right.
3. Click it. A dialog opens: "Flag library for review." It asks you to "Tell admins what's wrong" with the specific library.
4. Describe the problem in the box — be specific: wrong articulations, a missing patch, broken metadata, an incorrect default MIDI rule. The more precise you are, the faster it's fixed. (Up to 500 characters.)
5. Hit Flag library.

The button then reads Flagged and stays disabled — you don't need to flag the same library twice. A librarian is notified immediately.

You can only flag libraries you own. The Flag button is disabled on libraries that aren't in your library, with the tooltip "You can only flag libraries that you own" — flagging is a signal that you've actually loaded the patches and hit the problem first-hand.

Request a library that isn't in the catalogue

When the DawForge Assistant scans your machine and one of your installed libraries has no match in the knowledge base, you can ask for it to be added.

1. Run a scan, then open the assistant's review page (/settings/assistant/review/…). It lists every library found on your machine alongside the best-matching KB entry.
2. For a scanned library that has no match, use the per-row flag button. Its tooltip reads "Request this library be added to the KB."
3. Click it. The request is sent with what the scan already knows — the vendor, the library name, and where it was found — so there's nothing to type.

The button switches to Requested — pending librarian review and stays disabled. As with flagging, repeat requests for the same library are folded into the existing one, so you can't spam the queue by accident.

What happens next

Every flag and request lands in the same librarian queue and fans out to the DawForge curators (email + an in-app notification). From there:

• Flags are triaged against the canonical tag families — length, technique, style, pattern, dynamic. See Tags and families.
• Requests for a new library are curated from the vendor's documentation (or by sniffing the library directly), then added to the next catalogue snapshot — typically within a week.

You don't need to do anything after submitting. The fix or the new library appears on your next visit, because /search refreshes its offline copy in the background.

Bulk or proactive contributions

Flagging and requesting cover the everyday cases. If you want to contribute a whole library's patch list, articulations, and MIDI rules up front — or you're a vendor who'd like your catalogue curated proactively — see Contributing instruments.

Next

→ Contributing instruments