FluxFrame builds what the old frame couldn’t. Software, systems, and research.
The work starts before implementation: with the question of whether the problem has been framed correctly in the first place.
A changed model can expose capabilities that are difficult—or impossible—to reach by optimizing inside the old one. FluxFrame turns those reframings into working systems.
Deployment, provenance, versioning, storage, automation, data flows, and publishing architecture designed as one system instead of accumulated as glue.
Architecture papers, experimental protocols, benchmarks, and postmortems that turn intuition into something inspectable, falsifiable, and reproducible.
Flux separates artifact identity, location, context, and presentation—then compiles the resulting semantic graph into ordinary HTML, CSS, assets, and optional runtime behavior. The browser still sees the web. Flux sees the system underneath it.
The benchmark is evidence, not decoration. The full run includes correctness checks, deterministic hashes, environment capture, raw results, and reproduction code.
Inspect G001 →Each project changes a different assumption: what a website is, what content is, how knowledge should be searched, how local data should be understood, or how a self-improving system should explain its own changes.
Content is not a finished format. It is a source artifact that can manifest as an article, audio, video, thread, carousel, timeline, or graph without losing provenance.
Manifesting as article
Cognitive Cartography Compiler. Search and inspection built around conceptual relationships, evidence, people, time, and scope rather than a folder tree.
Continuous indexing and deduplication for macOS with inspectable progress and explicit filesystem state.
A theory and experimental protocol for testing whether causally valid self-provenance changes the behavior of an editable meta-improvement operator.
A Flux optimization moved directory creation out of render workers, passed correctness, and made the build slower. It was measured, documented, and reverted.
The point of changing the frame is not to produce a clever description. It is to produce a better system—and enough evidence for someone else to determine whether it actually is.
For technical review, systems work, research collaboration, or a problem that may need a different frame, get in touch.