Back to tutorials

Getting Started

Create an evidence-backed report

Save a focused investigation with file references and a reusable prompt.

7 min read · allow extra time to follow alongCodex, Claude Code

Before you start

  • A .genome workspace that your agent can read.
  • One question and an answer from your first conversation.

Turn a checked answer into a report you can revisit. Start in the workspace from the setup lesson, with one question you have already explored. This lesson focuses on the saved result.

1. Choose the scope

  • Choose one gene, variant, or research question. Keep that question at the top of the report.
  • Decide which files are relevant using your existing file map. Ask the agent to record the files it could not inspect.
  • Create a reports folder beside your .genome bundle for the output.

2. Create the report

Using our checked answer to [question], create a new Markdown report in reports/ without overwriting existing files. Include: the question and original prompt; the bundle version if available; files and record identifiers inspected; direct file evidence; annotations; external sources actually checked; limitations; and one follow-up question. Label each inference and any synthetic input. Do not modify the .genome bundle.

Your report should contain

# Exploration report

## Question and prompt
The exact question and prompt used.

## Evidence
File path → record identifier → supporting field.

## Interpretation and sources
What the annotations say, and which sources were checked.

## Limits
Missing data, unreadable files, and unverified claims.

## Next question
One specific question to investigate next.
Report outline. Fill it with evidence from the actual run; do not use the outline itself as a finding.

3. Open and check the saved file

  • Open the Markdown report in your workspace or a text editor. Check that the question and input type are correct.
  • Pick one factual claim and follow its file path to the cited record. Confirm that the field supports the claim.
  • Check that external sources are distinguished from bundle annotations. Remove any citation that cannot be verified.

4. Make the next run reproducible

Save the original prompt as a reusable Markdown template beside the report. Replace the topic with a clearly named variable and preserve the evidence, source, and uncertainty requirements. Include instructions to save each new run separately, recording its date and bundle version where available.

Before you continue

Check each item when you can do it.

Next tutorial

Build reusable prompt templates

Save a useful workflow so you can repeat it with a new question.