Help and resources.

Whitepapers 7 whitepapers, one per surface — Excel, Cursor, VS Code, Claude Code, any editor over MCP, vibe coding, the router. Each argues when convening a panel is worth the wait there, with worked jobs and the exhibits. Free, no form, no email. Setup guides Connect Quorum to the editor or spreadsheet you already use. Each config was verified against the vendor’s own current documentation rather than written from memory. Concepts What the moving parts are and what each one decides. Each page is the single owner of the facts it states — every other page that mentions them links there rather than restating them. Reference Look-up material rather than reading material. Every error code, the ceilings you hit first, and the machine-readable specification — read out of the handler source, so if the API returns something these pages do not list, that is a bug on our side. Evidence Nothing is published here at the moment. FAQ The questions people actually ask, answered short. It also carries the address for reaching a person, which is the faster route whenever the answer is not already on a page. Status Is it up right now, and what happened if it was not — from probes we run rather than from a badge we set by hand. Worth reading before you assume a slow answer was something you did.

Where to start

If you are new, the library’s quickstart is the shortest path from nothing to a first answer. If something looks broken, read Status first — it settles in seconds whether the problem is ours. If you are still deciding whether a panel suits your problem at all, the concept pages are written for exactly that, including the cases where the answer is no.

What is not here

Plan terms and how a call is actually billed live in the library, on one page that owns those facts so that nothing else has to restate them and drift. What a plan costs is on pricing, deliberately kept top-level: it is a page people need to reach without navigating first. Developer documentation has its own door at the API.