u/ElCptain

First time posting here. I studied economics and management science at master's level but I'm not a working economist, and I built this as a side project, so I'd rather have it picked apart than upvoted.

I tried to map, as honestly as I could, why the social democratic answer keeps getting harder to pull off. It's a causal graph where every link has a stated mechanism, a confidence level and a sign, so you can disagree with one specific arrow instead of the whole mood.

The core claim is simple and uncomfortable. The future probably isn't short on wealth. Automation and technology keep throwing off a large surplus. Everything hinges on one question: does that surplus get shared broadly, or captured by a few? Shared, and people feel secure and cohesion holds. Captured, and you get abundance without security, which feeds radicalization, renationalization and power politics. The dark outcome isn't scarcity. It's wealth that never reaches people.

Here's the part that worries me as someone sympathetic to redistribution. The obvious answer, just tax and share, keeps getting locked. Rising public debt eats fiscal room, and global tax and location competition means any country that redistributes hard on its own risks capital and talent leaving. So the redistribution exit looks bolted shut from several directions at once, and I can't cleanly model a way around it that survives the global race.

That's my actual ask. I want the social democratic case for how the surplus actually gets shared in a world of mobile capital and tight budgets. Supranational coordination? A global minimum tax that really holds? Taxing the surplus at the source instead of taxing labour? Predistribution? Draw me the path that breaks the lock, and break my pessimism at a specific node.

It's interactive and sourced, click any node or link for the mechanism. 👉 https://3lc4pt41n.github.io/quo-vadimus/quo-vadimus.html

TL;DR: I modelled why shared abundance keeps losing to debt and global competition, and I want the social democratic answer that survives the race.

https://preview.redd.it/75tsqbonpu3h1.png?width=3008&format=png&auto=webp&s=fce4601d5580ab4ca5e4d4ef92fc92a18fa8458d

I have a bad habit as a solo builder:

I get products close to launch, polish the landing page, tighten the flows, and then somehow move on before really putting them out into the world.

FloraScout is my attempt to break that pattern.

It is an AI plant app I built solo that combines:
- plant ID
- a plant dex
- health checks
- care tasks
- and chat

Landing page: https://florascout.app  
Repo: https://github.com/3lC4pt41n/Mein-Gaertner-App

I had the core idea more than 10 years ago: an app that recognizes plants.

At the time it felt useful, but too big to seriously tackle as a side project.

With the current AI stack, it finally became realistic enough to build.

Current stack:
- React Native + Expo
- Supabase
- PlantNet
- GPT-5.5
- GitHub Actions

What surprised me is that the hardest part was not the AI.

The hard part was turning “recognize a plant” into a product loop someone might actually come back to:

scan -> save -> discover -> health check -> care task -> return

That loop was the real work.

Because I am doing this solo while also working a full-time management job at a German SME, I have to be very deliberate about how I build.

My process now looks roughly like this:
- define Vision first
- define Architecture second
- challenge both with a second model
- generate implementation work orders
- implement locally
- review and audit in loops
- automate testing and deployment early

The biggest lesson for me is that solo building with AI still needs structure.

Without a clear product direction and architecture, the models drift too easily.
And without discipline around review and iteration, it is very easy to create something that looks impressive for five minutes but does not hold together as a product.

So for me the challenge is no longer:
“Can AI help me build this?”

The real challenge is:
“Can I actually ship it, learn from real users, and not hide behind endless iteration?”

That is what FloraScout is for me right now.
Not just a product, but also an attempt to stop being the guy who always has something almost ready.

Would love feedback on:
- whether the product loop makes sense
- whether the landing page communicates enough
- whether this feels like a real solo-founder product or still too much like a tech demo
- and how other solo founders force themselves to launch instead of polishing forever