#Researching a topic

Ask Arachne a real question and it reads across multiple live sources, synthesizes what it finds, and hands you a trustworthy answer with the sources gathered behind it.

#Overview

When you need an answer grounded in the real web — not a guess, and not a single page — you ask Arachne to research it. Arachne goes out across multiple genuine sources, reads them, weighs what they say, and returns a synthesized answer you can actually rely on. Every claim comes with its origin gathered into a source pack, so you can check where any point came from.

This is the difference between a quick reply and a researched one. A researched answer is built from real material that Arachne has read and reconciled, and it is verified before it reaches you. You bring the question; Arachne brings the reading, the synthesis, and the receipts.

#What you can do

  • Ask a question and get a synthesized answer. Arachne gathers information from several real sources, reads them, and gives you one coherent answer rather than a pile of links.
  • See the sources behind every claim. The references Arachne used are gathered into a source pack, so you can trace any statement back to where it came from.
  • Trust what comes back. Everything Arachne produces is verified before it is reported, so a researched answer reflects what the sources actually say.
  • Go deeper when the question is bigger. For larger questions, Arachne can run a deeper, multi-source dive and organize what it finds into a structured result. See Deep multi-source dives.
  • Get the answer in the format that fits. A research result can arrive as a written report, a comparison of options, a table of findings, or another of the eight formats — whichever suits the question.
  • Keep the result. A research answer is saved as an artifact you can reopen, reuse, and export later. See Artifacts & where they go.

#How to use it

  1. Open Arachne and state your question in plain language. Describe the answer you want, not the steps to find it.
  2. Be specific about scope. Say what you care about, how current the information needs to be, and any boundaries — a region, a timeframe, a set of options to weigh.
  3. Hand over anything you already have. If you know good links, a starting source, or constraints, include them. Arachne will fold them in rather than rediscover them.
  4. Choose a permission level that fits. For pure research, Look only or Plan first keeps Arachne reading and reporting without taking other actions. See Permissions & control.
  5. Watch the first run if the topic is unfamiliar, so you can steer early. You can adjust your question or the level at any moment.
  6. Read the answer and open the source pack to verify the points that matter to you. Ask for a different format, more depth, or a narrower focus in plain language, and Arachne refines from there.
Tip

A good research question names the decision behind it. "Which of these three options is best for a small team on a tight budget" gives Arachne the criteria to compare against; "tell me about these options" leaves it guessing what matters to you.

#Examples

What you ask:

text
Research the main approaches to backing up a small business's files, and tell me which fits a team of five with limited time.

What you see: A written report comparing the approaches, with a clear recommendation for a small team, and a source pack gathering the references behind each point so you can check them.

What you ask:

text
Find out what's changed recently in the rules for short-term rentals in my city, and summarize what actually affects a single-property owner.

What you see: A focused summary of the relevant changes, organized around what matters to a single-property owner, with the sources Arachne read gathered so you can confirm any detail.

What you ask:

text
Compare these four tools for the things I care about — price, ease of setup, and support — and show me which wins on each.

What you see: A comparison laid out side by side against your three criteria, drawn from real sources, with the references gathered into a source pack.

#Tips

  • Describe the outcome, not the search. Tell Arachne the answer you need and why; let it find the path to it. Listing steps narrows it before it starts.
  • State your criteria up front. When you want a recommendation or a comparison, name the things you'll judge by — budget, time, audience, region — so the synthesis is built around your decision.
  • Say how current it must be. If recency matters, ask for it explicitly so Arachne weights fresh sources appropriately.
  • Open the source pack before you act on the answer. It is there so you can verify; for anything consequential, trace the key claims back to their origin.