ConFuse

    Getting Started

    This guide takes you from signing in to your first grounded answer. Most people get through it in under ten minutes.

    1. Sign in

    Open ConFuse and choose Sign In. If your organisation has arranged access, you will land on your workspace dashboard.

    If you cannot sign in, see FAQ and Troubleshooting.

    2. Connect a source

    A source is anything ConFuse can read and index — a repository, a set of documents, or a set of web links.

    Go to Sources and connect one. Good first choices:

    • The repository your team works in most.
    • The document that explains how the project fits together.

    Start small. One or two focused sources produce much better answers than ten vague ones. You can always add more later.

    See Connecting Sources for the detail.

    3. Let it index

    After connecting, ConFuse reads the material and prepares it for search. This takes a little while the first time, and longer for large sources.

    You do not need to do anything here. Come back when the source shows as ready.

    4. Ask a question

    Ask the way you would ask a colleague:

    How does authentication work in this project?

    What was decided about rate limiting, and why?

    Where is the upload size limit configured?

    Specific questions get better answers than broad ones. "What is this project?" is hard to answer well. "How does this project handle retries?" is much easier.

    5. Read the answer — and the sources

    An answer in ConFuse has three parts worth reading:

    1. The answer itself. A direct response to what you asked.
    2. The sources. Where the answer came from. Open the ones that matter to you.
    3. Gaps and caveats. Anything the sources did not cover, or where they disagreed.

    If an answer says the material is not covered by connected sources, that is a real answer. It means your question reaches beyond what is currently connected — not that the system failed.

    6. Make it better

    Answers improve with better inputs:

    If the answer is…Try…
    Vague or genericNarrow the question: name the module, feature or document.
    Missing something you know existsAdd the source that contains it.
    Partially rightAsk a follow-up about the part that was wrong.
    "Not covered"Rephrase with different words, or connect a broader source.

    Where to go next