Ask anything about your project. Get the answer with its evidence.
Spectrum builds one context layer from code, documents, and issues that you can query. Every answer links to its original source.
Sound familiar?
Your project's knowledge is spread across tools, and none of them can be trusted on its own.
Meet Spectrum
One context layer from code, documents, and issues. Ask a question, get the answer with its evidence.
Connect repositories, docs, and trackers
Spectrum reads them and extracts specific facts into one context layer
The context layer updates as sources change
Ask from anywhere
Same context layer, same evidence, every role. Available in web interface and in your AI chat.
Which services call the pricing API, and do any of them cache the response?
Three services call the [Pricing API]. Only one of them caches the response, and _billing-worker keeps prices for 10 minutes_^1 before refreshing. - checkout-service: _calls the API on every cart update, no caching_^2 - billing-worker: fetches prices when generating invoices, cached in memory - admin-portal: _reads prices for the price editor, no caching_^3 For details, see [Pricing: Architecture] and [Billing worker].
Do we already limit password reset attempts? Where is that enforced?
Yes. _Password reset is limited to 5 requests per email per hour_^1. The limit is enforced in auth-service, not in the web app, so it also applies to the mobile clients. It was added after _a support escalation about reset-email spam_^2. The design doc still mentions 10 attempts, but _the code is current_^3. For details, see [Authentication: Rate limits].
A customer's invoice shows a discount that is not in their plan. What could have applied it?
Two things can add a discount outside the plan. The most common is a promo code: _promo discounts stay on the account for 3 billing cycles_^1, even after a plan change. - Promo code: applied at checkout, visible in the account's promo history - Manual credit: _added by an account manager in the admin portal_^2 Check the promo history first: _this explains most cases_^3. For details, see [Billing: Discounts].
Spectrum answers from facts it has already extracted, not from a fresh search of your sources. Each answer cites its origin.
Living documentation
Articles are generated from the context layer, and each statement links to its facts. When code or documents are updated, the affected articles are updated too.
It's an encyclopedia of your system, created using your code, documentation, and issues. Each article explains a topic to whoever needs it, be they a developer, product manager, or support engineer.