Reports & Charts

This is the canonical page for reading Spinosa output. Use it to understand what a report contains, how verification changes its status, and what the dashboard-style charts are telling you.

Every substantial answer comes back as a markdown report in agent_reports/. A report is not just a summary. It is the package Spinosa uses to show:

• the answer,
• the evidence behind it,
• the interpretation layered on top,
• the limitations,
• and whether verification passed.

A typical report includes these sections:

The shortest direct response Spinosa can give to your question.

Quoted passages with source paths and confidence labels. This is the part you read when you need to know exactly what the corpus supports.

Interpretation built from the evidence. Analysis should be useful, but it should never pretend to be the source itself.

What is missing, ambiguous, weakly supported, or still out of scope.

The file paths used to ground the answer.

The verification outcome after the Verifier checks the report against the source files.

• ○ pending: the draft exists, but verification has not finished yet.
• ✓ verified: the checked claims and quotes passed source review.
• ⚠ corrections: the report needed minor fixes during verification but is still usable.
• ✗ failed: important claims could not be supported reliably. Review before relying on it. If you only remember one rule, make it this one: trust reports by reading the status and the evidence together.

Many reports open with a compact dashboard like this:

┌─ Corpus Navigation ──────────────────────────────────────────────┐
│ Maps   ▓▓▓▓▓▓░░░░░░░░░░  6 consulted                            │
│ Raw    ▓▓▓▓▓▓▓▓▓▓░░░░░░  45 scanned · 12 read                   │
│ Source ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓  18 cited                               │
│ Status ✓ verified                                               │
└─────────────────────────────────────────────────────────────────┘

How to read it:

• Maps tells you how broadly the system ranged across navigation maps.
• Raw tells you how many files were scanned versus opened in more depth.
• Source tells you how many sources made it into the final answer.
• Status tells you whether verification is still pending, passed, corrected, or failed.

Spinosa uses simple Unicode charts so progress and health stay readable in plain text.

• Read the Answer first, then test it against the Evidence.
• Use Limitations to decide whether to ask a narrower or broader follow-up.
• Open the cited files in raw/ when a claim matters and you want the surrounding context.
• Treat a failed or pending status as a reason to pause, not as a cosmetic warning.

• Tour for the first-report walkthrough
• Agents & Pipeline for how reports are assembled and verified
• Corpus Structure for where reports and source files live
• FAQ for troubleshooting pending, failed, or confusing reports