How to use Agent Oracle

Open with the symptom and the timeframe: 'close rate fell from a third to a fifth over two quarters, headcount unchanged'. That single sentence lets the assistant skip ten clarifying questions and start testing explanations against each other.

Expect to be asked what else moved. Most business symptoms have a boring shared cause upstream, and the fastest route to it is a short interrogation rather than a long answer.

Push back. Saying 'that assumes our cycle is short and it is not' is the single most productive thing you can type, because the reasoning is conditional and the conditions are yours to correct.

When a conclusion matters, ask for the calculation rather than the verdict. A number you can rerun next quarter is worth more than a recommendation you cannot audit.

Experience accrues for completing tracks, passing knowledge checks, contributing accepted corrections and returning across multiple days. Streaks reward consistency rather than volume, so a short daily session outranks one long monthly one.

The leaderboard reflects the same totals, recalculated server-side. Contributions that are later reversed — a correction that turns out to be wrong — are removed from the total, which keeps the ranking meaningful.

Install the site as an app if you want one-tap access and full-screen voice mode; it works from a phone during a commute as well as it does from a desk. Voice is genuinely faster for the diagnostic phase, where you are mostly answering questions.

The habit that pays is using it before the decision meeting rather than after it. The value is in arriving with the assumptions written down, and that only works if the session happens first.