What is Florentin One?

Florentin One is how I, heyFlorentin, combine everything I work with — strategy consulting through WeMake, large language models, and Model Context Protocol (MCP) development — into a single place to build and research human-centered systems.

The question I keep returning to: how do we build AI that amplifies people instead of replacing them? Automation substitutes human effort. Augmentation multiplies human capacity. I build for the second one, and I try to make it available to everyone, not just organizations that can afford it.

Systems that reduce cognitive load rather than redistributing it. Most tools add another surface to manage; I'm interested in the ones that recede into the background and hand people back their attention. That means starting from the real problem — cognitive overload — not from a solution looking for a use case.

Everything here is built in coherence with the EU AI Act and grounded in WeMake's ethics guidelines: human and environment before profit, equal opportunity, transparency, and responsibility that shows up operationally — in code, contracts, and support — not just on paper.

• Problem first — Start with the real problem (cognitive overload), not with solutions.
• Augmentation over automation — Technology should amplify people, not replace them.
• Systems over tools — More tools are rarely the answer.
• Open process — Public, traceable, contributions welcome.
• Outcome over output — Impact beats delivery.
• Responsibility is operational — Visible in code, contracts, and support.

Systems thinking and complexity, antifragile organizations, ethics in technology, cognitive science and human-computer interaction. Practices from open-source communities (governance, reviews, contribution culture), security and cloud pioneers (Zero Trust, resilience), and teams that treat documentation like a product. Research on cognitive load and productivity from Microsoft, McKinsey, and UC Irvine.

I work in the open: RFCs, design docs, postmortems, and decision journals — because public process is both a quality filter and a way to teach.

The future of work isn't more tools. It's better systems. That's what I'm working on.