Designing a Product Systems Lab in a Few Hours
How AMARIN was designed and built as a scalable product systems lab in just a few hours — and why speed and structure are not opposites.
This is not simply a blog
AMARIN did not start as a content platform.
It started as a question:
What would a public product systems lab look like if it was designed from first principles instead of blogging conventions?
Most blogs are optimized for publishing speed.
Most personal sites are optimized for self-promotion.
Very few are designed as systems that can evolve into something more.
AMARIN exists to explore that gap.
Speed is not the opposite of structure
The first version of AMARIN was built in 2 hours (literally).
Not because it was rushed.
But because it was architected before it was implemented.
Every part of the system was designed with one constraint:
Can this evolve without being rewritten?
Which led to a few simple but structural decisions:
- Content lives in MDX, not in a CMS
- Every article is a structured entity, not a free post
- Metadata defines navigation, not publication dates
- Articles are treated as system modules, not blog entries
This is what allowed the first MVP to exist in minutes — while remaining prepared to scale.
Articles as system modules
Each article in AMARIN is not “content”.
It is a product system module.
Every document is versionable, indexable, filterable and composable.
Which means:
- Articles can become playbooks
- Playbooks can become courses
- Courses can become platforms
Without migrating or rewriting the core system.
The MVP already contains the future.
Why this matters
Most digital products fail when they succeed.
They grow faster than their architecture.
They scale features before they scale systems.
AMARIN was designed to study the opposite:
How can product systems be designed to grow without collapsing?
This platform itself is the first live experiment.
Some systems are commercial. Some are experimental.
Some of the systems documented here belong to real products.
Some belong to experiments.
Some belong to my own ventures.
All of them are real.
AMARIN is not a portfolio.
It is a public product systems lab.
And this is its first documented system.
Cuando publiques este, tu plataforma queda oficialmente inaugurada.
Siguiente paso después de esto:
convertir los siguientes 4 artículos en los pilares fundacionales del laboratorio.