Evolvix 1-Page Forecast Manual — Compiling Fox and Rabbit Ecology

A dense modeling panorama showing 8 steps from biological observation to simulation — and how treating individuals as indivisible reveals surprise extinctions.

Download the original document (PDF)

Fox-Rabbit Forecast Manual — PDF (6.2 MB) — 1 page (letter format, very dense), Jonah License with CC0 Public Domain

Filename: evx-1page-forecast-manual-fox-rabbit-pop-crash-iv_llol_qqv10r0p2_2018m07d19-letter.pdf

WebP preview (536 KB)

Warning

This is a 6.2 MB PDF. The document is extremely information-dense (a full scientific poster compressed to letter format). Readable in ~25 min or twice (as tested by the authors).

— Overview AI-generated by dv_ClaOp46Max_ExhH_2026m04d16 —Start—

Abstract

“Compiling a Model to Forecast Fox and Rabbit Ecology with Evolvix” by Laurence Loewe and Seth Keel (Wisconsin Institute for Discovery, University of Wisconsin-Madison) is the most scientifically detailed document in the STa1-EVX collection. Despite being a single letter-sized page, it contains a complete scientific poster’s worth of content.

The scenario: A rare fox breed is to be saved on big grassy islands with rabbits as food. Yet foxes keep going extinct. The big question: Why? Can a model predict fox survival from initial counts (40 foxes, 500 rabbits)?

The 8-step modeling cycle (Fig. 1):

1. Reality — too much to fully grasp; so we must model to cope

2. Model building — simplify; focus on one Big Question

3. Modeling toolkit — Parts, Actions, Rates framework

4. Encoding — write the model in Evolvix’s user-friendly syntax (working code for Evolvix.org prototype 0.3.1 is shown)

5. Compiling — the compiler re-encodes into two formalisms: (5s) stochastic individual-based CTMC, and (5d) deterministic ODE

6. Simulating — run both formalisms to produce time series

7. Storing — decide what matters about data and results

8. Concluding — learn how to improve models

The key discovery: Deterministic (ODE) simulations predict eternal oscillation — foxes and rabbits cycle forever, because the math treats ¼ of a fox as alive. Stochastic (CTMC) simulations show that populations crash and foxes go extinct, because each individual is treated as indivisible. This difference in computational assumptions is mission-critical in biology.

Working Evolvix code is shown directly in the figure — a simple Quest model with 4 Actions (Rabbit breeds, Fox breeds, Fox dies, Fox feeds) that can be entered as plain text into the Evolvix prototype.

The document also contains extensive fine-print discussing: the DesignFlip method for language design, the three foundational hallmarks of Evolvix (backwards compatibility, user-friendly clarity, growing extensibility), TabFS data format, VBIRs (Versioned Biological Information Resources), and detailed explanations of CTMC rates and exponential distributions.

Key Concepts at a Glance

Parts, Actions, Rates	Evolvix’s core modeling framework: define what exists (Parts), what happens (Actions), and how fast (Rates)
CTMC vs ODE	Two mathematical formalisms the compiler targets: Continuous-Time Markov Chain (stochastic, individuals indivisible) vs Ordinary Differential Equations (deterministic, individuals divisible)
Surprise extinction	The stochastic model reveals extinctions invisible to the deterministic model — a concrete example of why modeling formalism choice matters
DesignFlip	LLoL’s Flipped Programming Language Design method: design and review syntax/semantics before implementation
Three OLT hallmarks	(1) Full backwards compatibility, (2) user-friendly clarity, (3) growing extensibility — in that priority order

Broader Significance (Claude’s Assessment)

This is arguably the strongest document in the STa1-EVX collection for a scientific audience. It demonstrates that Evolvix is not merely a vision document but has a working prototype that produces verifiable results matching published models (Otto & Day 2007). The fox-rabbit example is simple enough to serve as a “hello world” yet complex enough to reveal a genuine scientific insight (stochastic extinction).

The fine-print sections contain a serious discussion of language design philosophy that would be recognizable to any compiler engineer: the tension between user-friendliness and formal rigor, the need for stable syntax, and the argument that biology needs its own domain-specific language rather than ad hoc scripts. The reference to the red blood cell metabolism model (Ehlert & Loewe 2014 J. Chem. Phys.) as a more complex test case adds credibility.

Document Information

Document ID	EVX Forecast Manual — Fox-Rabbit (Flying Scroll, transwarpkey/sta1-evx/)
Authors	Laurence Loewe and Seth Keel, Wisconsin Institute for Discovery, UW-Madison
Date	2018m07d19
Version	iv_LLoL_QQv10r0p2_2018m07d19
Format	Single-page letter (poster-density scientific document)
License	Jonah License with CC0 Public Domain
Part of	Good News Pack MMv3, Flying Scroll / Transwarp Key / STa1-EVX
PDF size	6.2 MB
WebP size	536 KB

Related documents:

• STa1-EVX stadium overview (parent page with all 30 documents)

• SD1 — RiskyMAD (the nuclear killer app referenced as Evolvix prototype application)

• Simplicity in Lasting Standards (the philosophical foundation for Evolvix’s design priorities)

— Overview AI-generated by dv_ClaOp46Max_ExhH_2026m04d16 —End—

Collapse all Expand all

Notes

Content stability — Content is variant dv_ClaOp46Max_ExhH_2026m04d16 (see StayVS). Rebuilt 2026-05-18.

Expert Review Needed: Help Assess This Research and Its AI Overview

This page makes accessible one document from LLoL’s 6+ year wid-e research marathon on existential risk and ResearchCity. The PDF linked above is the original work; this page provides an overview.

The original research needs expert review. Download the PDF and bring your expertise to bear — whether you are a scientist, policy maker, theologian, peace activist, or concerned citizen. This research aims to find gentle kind reasonable ways to solve existential problems. Your perspective matters for assessing whether it succeeds.

The AI overview (see the markers) may need correction. AI may have blindly twisted the original message by emphasizing other aspects than the author would have. Important nuances may thus be missed or misrepresented. If you spot errors, missing context, or misplaced emphasis, your corrections help every future reader.

Despite all potential shortcomings of AI, AI was still used here because not saying anything about this document would have been even worse. A race against existential risks is not nuanced. Neither can be the determination to do the right thing - and get the word out to get help.

LLoL is determined to ask for such help. Hence this website to give the world a fair chance at exploring and reviewing LLoL’s ideas.

Use the FeedbackFlow link below to send your review — whether it concerns the original PDF, the AI overview, or both.

LLoL may drown for a while in the FF invited, but if people are indeed interested in making this work and avert accidental nuclear winter, then LLoL predicts that enough people will be happy to pay the about $8/year/person it will take to start scaling up ResearchCity, in order to help with the proper review of such wid-e research proposals for global decision-support like this one.

Hence, please consider that your buy-in with about $8/year will help to shift the global game from a so-called prisoner’s dilemma to an assurance game with the help of mathematical theology.

This work requires global support to avoid capture by special interests. Refining complex posters, engaging scholars across traditions, and running formal consistency checks all require sustained effort — as does scaling up a ResearchCity for global FeedbackFlows.

Let’s hope it’s not too late to fund this work!

FF FeedbackFlow to improve this page: How you can contribute

For the full guide on providing feedback — including how it is handled, licensing, and what to expect — see How to use FeedbackFlow.

Please check if See also on Balospe.com above already addresses your idea. Feedback works best when it targets the most specific page. If none of those pages help, you may have a good case for sending FF here.

To submit your FeedbackFlow:

1. Click anywhere on the email preview below to open a pre-filled email.

2. Replace the placeholder text with your feedback.

3. Send.

To: [email protected] CC: [email protected] Subject: FF k2 s2 AIMS for [mmv3-twk-sta1-evx-forecast-manual] Replace_by_OneLineSummary Body: To make this page [mmv3-twk-sta1-evx-forecast-manual] more gentle kind reasonable for beginners, producers, andOr experts with a background in xyz: Please consider improving this: -- By sending this email, I agree that its content may be published under the Jonah License (balospe.com/en/license/joli/) unless I state otherwise above. MailForm=OOv2r0p0

The email subject contains k2 and s2 — default codes for impact and urgency. Most contributors can leave these unchanged. To adjust each as independently as they are:

• Importance of impact: above average k3, average default k2, below average k1.

• Urgency of speedup: above average s3, average default s2, below average s1.

This allows plotting importance over urgency to help triage FF. For more details see FF System Design.