# Emilista - the one that is still a question

Emilista is 214 commits of working Rails application in search of a sharp enough problem. It is the most honest entry in this portfolio because it is the one that has not worked yet, and knowing when to stop pushing something forward is a decision Corey now has to make on real projects.

These case studies are first-party. Corey is built by Kristian Papadakis for Presso Network, and every business covered is one of ours - not a client, not a commissioned case study.

## The facts
- Venture: Emilista - A Rails application built to explore a problem that has not been pinned down yet.
- Status: Exploratory
- Started: 27/02/2026
- Commits: 214
- Who did what: Built by Kristian Papadakis. Predates Corey. Currently paused rather than shipping.
- Built with: Rails, Hotwire, Tailwind

## What we decided
- Stop, rather than launch something unclear: There is a working application here. The decision was not to push it out anyway. Launching a product whose problem statement is still fuzzy converts a cheap open question into an expensive public commitment, along with the users, support load and sunk pride that come with it.
- Get the question right before the answer: The stage is problem definition, not build. That is uncomfortable to sit in when there is already a codebase, and it is the correct place to be. Better to hold an unanswered question than ship an answer that does not hold.
- Do not let it quietly consume attention: The real risk of an unresolved project is not that it fails. It is that it keeps taking small amounts of time indefinitely while never being finished or stopped. Parking it explicitly costs less than leaving it ambiguous.

## What got built
- A Rails and Hotwire application at 214 commits, built between February and May 2026.
- Enough working product to test the idea properly, which is what produced the honest answer.

## What Corey runs now
- Keeping it visible while parked: A paused project still appears in the portfolio view with its actual status, so it is a deliberate decision rather than something quietly forgotten.
- No maintenance theatre: Nothing is scheduled against it. Recurring work on a project that is not moving is just a way of feeling productive about it.

## What this became
Emilista taught the least comfortable lesson in the portfolio, which is that an operator has to be willing to say a thing is not working. It is the reason Corey reports honest status rather than optimistic status, and why "early" and "exploratory" are values it will actually use about your projects. An operating system that only ever tells you things are going well is not an operator. It is a cheerleader, and you can get those for free.

Full page: https://getcorey.ai/case-studies/emilista