Keep findings with their sources, then search them again by meaning.

Give a research question a persistent home. Later, ask a plain-language question to retrieve related passages with their source and evidence grade where present.

Findings, source trails, and retrieved passages.

Findings and raw research are kept as files beside a local search index.

  1. Research record

    Keep each finding beside its sources.

    Outputs can include a subject index, individual findings, raw research artifacts, and lists of claims to check.

  2. Retrieval

    Bring back related passages.

    A result can include the passage, source, similarity value, and evidence grade where one is present.

Available by demo; not yet publicly installable.

This preview offers no public install path or request form.

  1. Choose a question Name the subject and what a useful answer would need to establish.
  2. Review retrieved passages Check the source link and evidence grade where one is present.
  3. Read the underlying source Read the underlying source before citing it.

View the workflow

Research findings and retrieval

  • One persistent home per question

  • Findings stay with sources

  • Sources stay available for review

Give research a home and retrieve it later.

The workflow stores a question, findings, raw research, and indexes so later questions can find related passages.

  • Create a subject folder

    Give a research question a persistent home and add the question as a seed.

  • Run a research pass

    Research runs when you ask for it.

  • Check the evidence trail

    Findings can carry source links and evidence grades. A lint can fail a Strong claim if its source was not retrieved.

  • Index and retrieve

    Ask a plain-language question and filter retrieved passages by subject, grade, or source.

Similarity helps retrieve; it does not prove a claim.

Read the cited source before using a retrieved passage to support a claim.

  1. Retrieval score

    Similarity

    Relatedness only

    It sorts passages that use related language near the top of a result list.

  2. Source lint

    Strong claim, source not retrieved

    Lint fails

    The lint rejects a Strong claim when its own source table says the primary source was not retrieved.

Use the research environment and dispatch each pass.

Runs in your Claude Code environment. No broader privacy, retention, or data-processing terms are supplied.

  • Persistent files

    Keep findings and raw research together.

    The findings and source notes are stored as files; retrieval vectors are held in SQLite.

  • Human direction

    Start each research pass deliberately.

    A person sets the question and dispatches a research run, then checks its source trail.