Projects and notebook

The project pages explain the research questions, my contribution, what I built, and the available evidence. The notebook retains the detail: experiment setups, failed approaches, observations, and unresolved decisions.

Project summaries link to the relevant notebook entries, evidence, and limitations.

Experiment records

Each entry records:

  1. The question and the decision the experiment should inform.
  2. The setup: data provenance, methods, model identities, code revision, configuration, and execution conditions.
  3. Observations, including failed and invalid runs.
  4. Interpretation, uncertainty, and what the result does not establish.
  5. Links to code and artifacts, with their availability stated accurately.
  6. The next decision or experiment.

Dates distinguish a new experiment from a retrospective account. A later correction links back to the earlier entry and explains what changed. Failed and inconclusive approaches remain part of the research record.

Evidence and availability

A linked source should support the specific claim beside it. A reported local observation, a public code snapshot, and a released run bundle offer different levels of inspectability. I label those differences instead of implying that every result is independently reproducible.

Software tests and synthetic smoke runs can establish that specific mechanisms work. They do not establish biological validity or model superiority. Model-based verification and judging also need their own evaluation.

Drafting and review

Raw notes and private drafts stay outside this public site’s repository. I can ask Codex to draft an entry from selected notes, code changes, and run artifacts, then review the evidence, wording, and attribution before publication.

Only curated material belongs in the public record. Drafting assistance is not scientific review, and publication is a separate decision.

Responsibility

I own the research questions, decisions, and public interpretation. Coding agents assist with implementation, tests, source audits, and drafts. Project pages describe that assistance alongside my contribution and the work’s limitations.