MFR is free to study. The complete setup exists for the part that usually costs the most: implementation time. Read the public work on GitHub ↗
Model · Formula · Reflector

Build around ownership.
Not screen count.

MFR is a feature-oriented reactive architecture for applications with shared, interconnected state across multiple screens and complex workflows.

Who actually owns this feature?

The question that eventually became the architecture.

FluxDeck owns.

Feature-lived state stays with the feature.

Formula derives.

Don't manually synchronize what can be derived.

why mfr exists

The problems get louder as the feature gets bigger.

MFR moves the ownership boundary above individual screens and makes state derivation a declarative relationship.

01 / GOD-CLASS VIEWMODELS

One screen becomes the entire feature.

Persistent state, derived state, operations, events and UI concerns pile into one class.

02 / FRAGMENTED OWNERSHIP

The feature gets split between screens.

Shared state is duplicated, re-fetched or passed around just because navigation changed.

03 / MANUAL SYNCHRONIZATION

Derived state starts drifting.

Multiple mutable values need imperative updates to keep different representations in agreement.

the architecture

Three core roles. Supporting pieces around them.

MFR is Model · Formula · Reflector. The supporting architecture keeps operations, events and data concerns separated around those three roles.

UI
↓
Reflector
↕
Formula
↕
FluxDeck

Model. Formula. Reflector.

Model — FluxDeck: owns feature-lived state and acts as the source of truth.

Formula: declaratively derives state from existing state.

Reflector: reflects feature state to the UI and owns genuinely screen-specific ephemeral state.

supporting architecture
01

FeatureCoordinator

Coordinates operations and UseCases without turning the state owners into operation hubs.

02

StateReflector

Supporting result-handling infrastructure for standardized results and transient events.

03

Events

Keeps one-time UI effects separate from persistent feature state.

04

UseCase · Repository · DataSource

Define the operation and data boundaries around the feature.

DataSource → Repository → UseCase → FeatureCoordinator → FluxDeck / Reflector
the continuum

Navigation changes the screen. It doesn't have to reset the feature.

The Continuum is the feature's continuous memory.

Screen A → Screen B → Screen C

Destroy state. Recreate state. Fetch again. Pass context around. That's what fragmented ownership tends to create.

Feature → FluxDeck → Reflectors

The feature keeps its state for the workflow's lifetime while each screen reflects what it needs.

from the story to the setup

It started with one question: who actually owns this feature?

the short versionModel owns.
Formula derives.
Reflector reflects.

If you've read Solutions come from surviving, you already know the origin: a real Android project, a ViewModel that quietly became a God Class, and the repeated question of who should own the feature.

No paywall on the ideas — read the public work on GitHub ↗
a few honest answers

No mystery. No magic.

What exactly am I paying for?

The prepared setup: the structure template, AI implementation resources, migration resources and supporting checklists that save time from assembling them yourself.

Can I implement MFR without buying it?

Yes. That is intentional. The public documentation explains MFR so you can learn it and implement it yourself.

Should I let an AI agent build everything?

No. AI can accelerate implementation, but you should monitor it, check its architectural decisions and make sure it follows the MFR guidelines.

How should I migrate an existing project?

Make a copy of the project first, migrate and verify there, then apply the validated changes to your main project.

Portrait of Vedant R.J. Chourey
About the author

I build software.
I also build stories.

I'm Vedant R.J. Chourey, an Android Developer working with Kotlin and Jetpack Compose. I enjoy building products, thinking about architecture, and figuring out how software behaves when a project grows beyond the simple version we started with.

MFR came from real-world Android development — a ViewModel that quietly became a God Class, and the question I kept asking: “Who actually owns this feature?”

Outside software, I'm also a writer. I've written a fiction saga and published my novels through Amazon Kindle.

MFR is a result of sleepless nights and many trials and errors. The core understanding and implementation are available for everyone. If you've received a free copy, learn from it, experiment with it or use it for education — just don't sell or redistribute it as your own. And if MFR ever helps you, send me a message at vedantchourey99@gmail.com. I don't need a coffee. Knowing it helped you is enough.