Founder & Builder of Synapedia
Florian Lux
A question became a system.
Synapedia makes Florian’s way of building visible: fragmented knowledge becomes structure, and structure becomes comparisons, tools, and connections. Content grew into a platform whose parts build on one another.
Each solved problem exposed the structure for the next.
The starting point was an information problem: knowledge was scattered, difficult to compare, and rarely connected. The response did not stop at articles. Research became structure; structure enabled comparison; relationships led to tools, a graph, and community.
The trajectory shows compounding rather than a longer feature list: data models, navigation, trust, and discovery share the same entities and relationships.
The build log shows content becoming infrastructure.
Eight confirmed milestones show questions being translated into comparison, relationships, access, and trust. The record documents product development, not personal biography.
- Commit 4e53b18c5
Repository history begins
The repository history begins.
- Commit e711ac142
Interaction Checker
Interactions become a dedicated, risk-oriented product area.
- Commit 30f872bfc
Substance comparison
Structured profiles can be assessed side by side.
- Commit 7ae6d726e
Knowledge Graph
An interactive interface visualizes nodes and relationships in the Knowledge Graph.
- Commit 8716a5d9d
Search-first explorer
Navigation through substance knowledge shifts toward search and exploration.
- Commit eb937fd77
English homepage
Multilingual access becomes visible on the central entry page.
- Commit c3e9f1e6d
Community context
Comments, votes, discussions, and community routes are introduced.
- Commit 782579412
Mission & trust
The platform explicitly documents its principles, boundaries, and approach to quality.
The parts became more useful when they began to connect.
Research, product, design, engineering, data, harm reduction, community, and open knowledge form Synapedia’s shared infrastructure. The map claims neither personal qualification nor final scientific authority.
- Research: Assess sources, evidence quality, and uncertainty.
- Product: Translate complex questions into clear paths.
- Design: Make information density readable and accessible.
- Engineering: Turn knowledge structures into resilient products.
- Data: Model entities, relationships, and provenance.
- Harm Reduction: Keep safety-relevant information accessible.
- Community: Treat experiential knowledge as context, not proof.
- Open Knowledge: Make traceable information publicly accessible.
Research
Assess sources, evidence quality, and uncertainty.
Product
Translate complex questions into clear paths.
Design
Make information density readable and accessible.
Engineering
Turn knowledge structures into resilient products.
Data
Model entities, relationships, and provenance.
Harm Reduction
Keep safety-relevant information accessible.
Community
Treat experiential knowledge as context, not proof.
Open Knowledge
Make traceable information publicly accessible.
The way of working is visible in repeated decisions.
Not only in visible features: sources, data models, review status, and boundaries are treated as part of the product. Personal motives are not invented from them.
Sources before certainty
Claims should remain traceable to their provenance and evidence quality.
Context before simplification
Effects, risks, and experiences are not collapsed into one type of evidence.
Safety through clarity
Limits, warning signals, and uncertainty belong in the primary user journey.
Systems that remain inspectable
Methodology and review status should be visible instead of merely asserting authority.
Synapedia lets the work speak for itself.
Comparison, the Interaction Checker, graph, methodology, and community show different layers of the same product. These surfaces are the evidence—without invented case studies, employers, or audience metrics.
Knowledge system
Knowledge Graph
A visual layer for relationships among substances, receptors, and effects.
Open graphRisk context
Interaction Checker
Combinations are presented with risk levels, mechanisms, and uncertainty.
Check interactionsStructured comparison
Compare substances
Shared data fields expose differences and missing information.
Open comparisonTrust layer
Methodology
Source types, quality signals, and editorial boundaries are documented transparently.
Read methodologyPublic purpose
Mission & trust
The platform describes what it stands for, what it is not, and how collaboration is approached.
Read the missionPublic profile
GitHub
The already published developer profile of Florian Lux.
GitHub profileOne solved problem became the foundation for the next.
The repository history begins with one file. Content then becomes comparable, relationships become tools and search, and community and trust become infrastructure. The pattern is visible: one solved problem becomes the foundation for the next.
The Founder profile documents product and system development. Subject-matter claims should stand separately on evidence, sources, and visible uncertainty—not on personal authority.
Trust needs inspectable paths and clear boundaries.
Methodology, mission, privacy, and legal information remain directly accessible. Feedback about errors, sources, or collaboration is welcome.
Founder identity and scientific authority remain separate
The Founder profile documents product development and system decisions. Scientific claims are assessed independently through evidence, sources, and uncertainty; the content does not replace medical advice.
An open door for expert feedback
Source notes, corrections, and responsible collaboration proposals can be sent directly to Synapedia.
flo@synapedia.comNew connections make the whole more useful.
Synapedia is not built as a collection of isolated pages. Content, relationships, sources, languages, and tools work together so each new layer can build on existing structure.