#Reports

When the answer needs to be read, not just glanced at, Arachne writes it up as an organized document with sections and findings.

#Overview

A report is one of the eight ways Arachne presents what it produces. It is a written, organized document — sections, structure, and clearly stated findings — for work that has a narrative rather than a single number or a grid of values. When you ask a question that deserves a considered, readable answer, this is the format that fits.

Reports are where research and analysis come together into something you can actually read top to bottom. Arachne chooses this format automatically when the work is best understood as prose with structure, and every report it delivers has already been verified before it reaches you.

#What you can do

  • Get a written, sectioned document with findings instead of raw data when the work calls for explanation.
  • Read a clear summary up front, then move into the detail organized into sections.
  • See the references behind the findings gathered into a source pack, so you can check the origin of any claim.
  • Refine the report in plain language — ask for more depth, a tighter summary, a different emphasis, or a change of structure.
  • Ask for a different format when a report is not what you wanted — for example a comparison or a table.
  • Keep the report as an artifact you can reopen, reuse, and export or download later.

#How to use it

  1. Describe the outcome you want as a question or a brief — what you need to understand, and what it is for. Arachne picks the report format when prose with structure fits the work.
  2. Read it the way it is built: start with the summary for the headline, then move into the sections for the supporting detail and findings.
  3. Check the source pack that accompanies the report to verify any specific point against where it came from.
  4. Refine in plain language. Tell Arachne what to change — expand a section, shorten the opening, focus on a particular angle — and it rewrites the report.
  5. Export or download the finished report, or come back to it later as a saved artifact.
Tip

If you want a report rather than a chart or table, say so in your request. Arachne chooses the best fit automatically, but a clear preference up front saves a round of refinement.

#Examples

What you ask:

text
Look into how remote-first teams handle onboarding and write me a short report.

What you see: a written report with a summary at the top, sections covering the main approaches and their findings, and a source pack gathering the references behind it — saved as an artifact you can reopen.

What you ask:

text
That's good, but expand the section on the first week and trim the intro.

What you see: the same report, rewritten — a tighter opening and a fuller section on the first week, with the rest intact.

What you ask:

text
Actually, give me this as a comparison of the three approaches instead.

What you see: the same findings re-presented as a side-by-side comparison of the three approaches against the things you care about.

#Tips

  • Say what the report is for — a decision, a briefing, a quick scan — and Arachne pitches the depth and tone to match.
  • Read the summary first; it carries the headline so you can decide where to dig in.
  • Use the source pack to verify any claim before you act on it.
  • If a report is more than you need, ask for a table or a short answer instead — the format is yours to change.