Fractal Observatory
Fractal Observatory explores mathematical scenes through explicit visual parameters. The case study connects the interaction design with rendering budgets, reproducible scene state, and a proposed local creative assistant.
Delivery status is not specified in this case study.
A real-time visual system has an enormous number of possible parameter combinations. Blind randomization can create ugly frames, performance spikes, or scenes that cannot be reproduced. The challenge is to preserve surprise while keeping motion smooth and every meaningful result understandable.
What makes it useful: Randomized visualizers can produce one striking frame but cannot explain or reproduce it. Fractal Observatory explores parameter paths under explicit performance and coherence limits, rejects combinations that would stutter, and remembers how each scene was reached.
The project explores how mathematical graphics can become an inviting visual instrument. Responsive interaction and reproducible scenes are the goals; smoothness must be measured on the device running the renderer.
Edge AI is imagined here as a local creative companion that studies user movement, remembers preferred visual motifs, and proposes new render parameters in real time without shipping the exploration history to a cloud service.
Choose a scene and inspect the parameters that define its shape and appearance.
Adjust the view or parameters within the renderer’s available budget.
Retain the scene state to revisit a result and compare its visual and performance behavior.
I built Fractal Observatory as a performance-conscious interactive rendering system. It connects user movement to bounded parameter changes, watches frame and memory budgets, preserves important scene state, and creates room for local pattern recognition to suggest new directions without taking control of the rendering truth.
I designed scene parameters and interaction around a rendering budget. Keeping the parameter state explicit makes a visual result easier to revisit; a local assistant that proposes new paths remains an extension to evaluate.
The OverLift method turns rendering choices, user input, frame-time limits, memory limits, and visual goals into explicit state. It can compare several parameter paths, reject combinations that break the performance budget, and preserve the sequence that produced a scene so exploration remains creative without becoming random or irreproducible.
The method is reusable. Each product supplies its own facts, rules, execution, and validation. These tiers describe the shared architecture; the project scope above records which capabilities are implemented here.
Why determinism matters here: A visual experience cannot be tuned or revisited when every scene is a random accident. Determinism preserves the parameters, performance budget, and path that created the result.
Define the authoritative result before adding acceleration, semantics, or agents.
Instrument state, latency, quality, and failure so improvement is observable.
Move expensive or high-frequency work behind clear worker and memory boundaries.
Version messages, snapshots, identities, deadlines, and replay inputs.
Let local retrieval and models propose meaning only inside admitted evidence.
Compare several allowed next actions with explicit risk, cost, fit, and uncertainty.
Challenge the production route without giving the challenger authority.
Promote only measured, replayable paths with fallback and operational receipts.
Run advanced evaluators in shadow, compare them with the control, and graduate only repeatable gains.
CATS chooses a qualified execution tier for the evidence, device, latency, permissions, and failure conditions of the task.
The Semantic Bridge maps a goal to explicit entities, evidence, uncertainty, tools, and permissions. Missing or contradictory information remains visible.
Models may retrieve, compare, or propose. Exact software checks facts, permissions, state changes, and execution, then records what happened.
The portfolio provides a system overview of scene parameters, performance budgets, and replay. It explains the design rather than running an interactive renderer here. It does not establish a frame-rate guarantee or a measured benefit from AI-generated parameters.
