How Mahlis Builds a Dependable Product Foundation
Mahlis begins product development by defining purpose and boundaries before expanding features.
This discipline helps prevent new ideas from continuously entering the same release and makes it possible to test whether a specific body of work is complete.
A small, understandable technical foundation
The Mahlis website uses Python, Flask, SQLite, Jinja templates, HTML, CSS, minimal JavaScript and controlled Markdown.
Dependencies are kept limited and pinned to tested versions so the architecture remains easier to understand, inspect and maintain.
Markdown as the source of truth
Public pages and articles begin as Markdown files. Controlled metadata records identity, publication status, descriptions, dates and search instructions without exposing those internal fields to ordinary visitors.
The publication flow validates metadata, sanitizes rendered content, records important publication events and preserves earlier versions through version control.
Security boundaries
The public application separates public content from protected administrative information. It uses allowlisted routes, environment-based configuration, server-side sessions, request protection, rate limiting, database migrations and security headers.
The public website does not store patient records or provide clinical decisions.
Evidence before expansion
Each Mahlis product moves through definition, prototype, simulation, controlled testing and release gates. A date can organize work, but it cannot prove safety or usefulness.
The same principle guides Vitalis OS, Vitalis Drug Planner and Atari Eyes: make the problem understandable, build the smallest useful test and allow evidence to determine what happens next.