Research prototype

EvoBotany Lab

A deterministic interactive prototype for exploring how rule changes influence simulated plant traits across repeatable runs.

Learners and researchers exploring evolutionary systemsActive research prototype · July 2026Evidence reviewed July 28, 2026

Interface evidence

A real frame from the documented system

Each image is an optimized public-safe capture. Captions state the fixture, data, and verification boundary represented in the frame.

EvoBotany Lab simulation showing generated plant-like organisms, ecology metrics, selection settings, and body economics.

Deterministic simulation capture showing generated organisms and inspectable experiment parameters. It contains no real organism data and makes no biological prediction claim.

ProvenanceExisting Playwright capture of the EvoBotany desktop simulation, supported by deterministic engine and genome tests.

Problem

The costly workflow

Educational simulations become difficult to reason about when every run changes unpredictably or the rules are hidden behind the visual result.

Role

What Devin owned

Defined the deterministic model, interactive experiment controls, and explanatory presentation for the research prototype.

System design

Architecture and data flow

The public description stays at a useful system level without exposing private records, credentials, or machine-specific implementation details.

Architecture

  • Seeded deterministic simulation
  • Explicit trait and environment rules
  • Interactive parameter controls
  • Repeatable run comparison

Data flow

  1. A seed and parameter set define the experiment.
  2. The same rules advance each simulated generation.
  3. Trait changes are recorded across the run.
  4. The interface compares repeatable outcomes as parameters change.

Constraints

  • Equivalent inputs must produce repeatable outputs.
  • Simulation rules and simplifications must remain visible.
  • The experience is educational and exploratory, not a biological prediction engine.

System-flow diagram

How information moves through the verified slice

This is a public-safe architecture diagram, not a product screenshot. It shows responsibilities and handoffs without exposing private data or implementation paths.

Flow step 01

A seed and parameter set define the experiment.

Flow step 02

The same rules advance each simulated generation.

Flow step 03

Trait changes are recorded across the run.

Flow step 04

The interface compares repeatable outcomes as parameters change.

Evidence references

The artifacts behind the verification

Each reference names the implementation, test, documentation, or public demonstration that supports the claims on this page.

Automated test

Seeded random-number contract

Dedicated deterministic-RNG tests verify that equivalent seed and input sequences reproduce the same values.

Automated test

Evolution engine and genome suites

Engine, genome, obstacle, viewport, and checkpoint-oriented tests exercise the implemented simulation substrate.

Documentation

EvoBotany architecture and research dossier

The research notes separate implemented developmental behavior from biological claims that still require causal experiments.

Verified behavior

What the evidence supports

  • Identical seeds and parameters reproduce the same simulated run.
  • The prototype exposes its controls and simplified assumptions.
  • The public framing avoids claims about real-world biological prediction.

The prototype makes an abstract evolutionary system inspectable: visitors can change one factor, replay the run, and reason about the resulting pattern.

Boundaries

What this case study does not claim

  • The model is intentionally simplified for exploration.
  • Outputs are simulated and do not predict real organisms.
  • The current scope prioritizes determinism and explanation over biological breadth.

Proof-safety review

Public package checks

Confirmed for the material rendered on this case-study page and its linked public evidence.

Implementation vocabulary

Deterministic simulationInteractive UIData visualizationRule systems