Co-create · Test · Challenge

Help advance Rendered Frame Theory

This page is the working floor for RFT. Here we document live experiments (such as the Mutation Agent), take community parameter suggestions, and run scheduled demo simulations where your input is actually used. No spectators only — this is for people who want to push, test and refine.

Community input directly into RFT experiments

Weekly demo runs with public logs

No hype, no abuse – only concrete suggestions

How this works

A simple pipeline: define the experiment, collect inputs, run, publish results.

1. Active experiment. We publish the current RFT experiment focus, including a short description, key equations/parameters, and what we are trying to measure.
2. Community input. You propose parameter sets, mutations, constraints, or critiques via GitHub or email. The more precise, the better.
3. Weekly demo run. On a fixed day each week, a batch run is executed using a selection of community inputs, and summary stats/plots are posted here or linked from a lab.
4. Feedback loop. Results feed back into RFT equations, future experiments, and updated demos. Good ideas get absorbed; weak ones are documented and dropped.

Current focus: Mutation Agent / Self-Deciding Brain

Symbolic civilisation agent that mutates, learns and stabilises under RFT resource and coherence constraints.

Experiment spec

RFT Mutation Agent

Self-deciding, resource-limited symbolic agent · RFTSystems

The Mutation Agent is a high-dimensional symbolic agent that balances exploration, stability and resource cost. It mutates internal glyphs and decision rules while tracking a coherence metric kappa, resource level, and "awakening phase" states linked to RFT parameters such as \u03C4_eff and P_max.

Core aims:
· Discover conditions where coherent, self-initiated behaviour emerges without collapsing into noise.
· Map how resource penalties and mutation scales affect long-term stability.
· Identify parameter regimes that align with RFT consciousness and computation limits.

RFTSystems Spaces Unified Field Framework

Your role

What to send in

Concrete proposals only

Examples of useful input:
· Suggested ranges for mutation rate and resource penalty factors.
· New glyph types or reward signals grounded in RFT quantities.
· Specific "what if" scenarios (e.g. extreme scarcity, surplus, noise shocks).
· Hypotheses: "If we do X, kappa should rise/fall in regime Y."

Keep it tight: parameter names, values/ranges, and a one-line reason.

Send your parameters and ideas

Two simple channels. No accounts beyond what you already use for GitHub or email.

When you submit, include: (1) the experiment name ("Mutation Agent"), (2) your parameter set or idea, and (3) what you expect to happen. If a configuration is selected for a demo run, it will be referenced in the log with your handle (or "anon" if you prefer).

Submit via GitHub issue Or email a proposal

Submissions are filtered only for spam and abuse. There is no requirement to agree with RFT — sharp, honest critiques are welcome if they are specific and technical.

Weekly demo run log

Summary of past demo runs using community inputs. Update this table as runs are completed.

Public record

Mutation Agent demo history

Replace and extend these rows as you accumulate runs.

Date	Run ID	Key parameters / scenario	Source	Main outcome
2025-12-11	MA-001	Higher mutation rate, softened resource penalty; exploration-focused regime.	Internal baseline	Short bursts of high kappa, but frequent collapse; useful as reference for future community runs.
2025-12-18	MA-002	Community set A: reduced noise, stricter resource discipline.	@example_handle	Stabilised mid-level coherence; fewer awakenings but more durable structures.

For each new weekly demo run, add a row with the date, a simple ID, the configuration summary, the submitter handle (if they want credit), and one or two lines describing what actually happened.