Curious Minds / Projects

Ideas. Built.
Systems That Think, Adapt, and Create.

I build and document original projects at the intersection of artificial intelligence, embedded systems, scientific data, design, and real-world problem solving. Some begin as questions, some become working prototypes, and others remain research directions until there is a useful way to test them.

A visual overview of Fluxed projects, experiments, and research

Research Direction

Related concepts and extensions

These entries make the relationship between working projects, broader practices, and developing research visible without presenting them as equally mature.

QCGU

A speculative quantum extension of CGU asking whether decoherence, error behavior, or changing hardware reliability could become meaningful internal-state information for a classical monitoring and response system.

View project →

Instinct Engine

The behavior and regulation layer associated with CGU. CGU senses and interprets internal state; the Instinct Engine explores how that state can influence priorities, visible responses, and bounded behavior.

CGU branch — documentation in progress

Scientific Visualization

A broader practice of entering unfamiliar datasets, building repeatable processing paths, and communicating what the data reveals without confusing visual enhancement with new measurement. PUNCH is the first fully documented example.

Project family — represented by PUNCH

Spreadsheet Automation

Practical systems for turning repetitive data preparation, naming, validation, and packaging work into repeatable workflows.

Documentation in progress

Organic Music

Creative audio experiments exploring responsive sound, biological pattern, environment, and generative structure.

Documentation in progress

Physical Experiments

Mechanisms, product concepts, sensor systems, and other ideas tested through physical form and engineering logic.

Archive being reviewed

How I Work

Human direction, AI acceleration

I use AI as part of the process, but the projects begin and end with my decisions.

My role

I originate the questions, decide what is worth building, define the constraints, assemble or operate the systems, run revisions, evaluate the results, and set the boundary between what worked and what remains an idea.

These pages focus on what I built, why I built it, and what I learned. I show selected code and evidence when they help explain the work; additional source files are available for technical review on request.
CuriosityBegin with a question worth testing.
ConstructionTurn the idea into something observable: a prototype, workflow, system, or durable record.
EvidenceSeparate what worked from what was proposed, inferred, or left unresolved.
IterationUse each result to define the next useful step rather than forcing every idea into a finished-product claim.