Development plan
Mahlis Roadmap
A public view of what Mahlis is researching, building and testing, with clear boundaries between an idea, a prototype and a production-ready product.
Dates will be published only when the work, people and resources required for a milestone are sufficiently understood. The stages below describe the order of work, not a promise of immediate availability.
Development stages
-
Problem definition
Describe the operating problem, affected people, current alternatives and assumptions that require evidence.
-
Research and case study
Review technical, clinical, accessibility, privacy, security and regulatory considerations.
-
Focused prototype
Build a limited system that tests one defined mechanism without presenting it as a completed product.
-
Controlled evaluation
Test the prototype with appropriate participants under documented safety, consent and data boundaries.
-
Minimum viable product
Combine validated functions into a usable product with support, recovery and operational documentation.
-
Controlled pilot
Operate with a limited group, defined success measures and a process for responding to incidents and feedback.
-
Production review
Complete the required technical, security, legal, regulatory and operational reviews before wider use.
Vitalis OS
Current stage: Architecture and focused prototype development
Current work
- Define the responsibility of the Vitalis Kernel.
- Design offline identity, permissions and audit boundaries.
- Document authenticated package and update verification.
- Define backup, restore and safe recovery behaviour.
- Prepare a controlled hardware prototype environment.
Next milestone
Demonstrate a limited offline environment that can identify an authorized user, apply defined permissions, record local audit events and recover from a deliberately introduced failure.
Evidence required to advance
- Repeatable installation and recovery instructions.
- Documented threat model and security test results.
- Verified behaviour when network access is unavailable.
- Review of hardware and workflow assumptions.
Vitalis Drug Planner
Current stage: Problem definition and prototype planning
Current work
- Document representative medicine-planning scenarios.
- Define quantity, frequency and duration calculations.
- Identify incomplete or conflicting instruction conditions.
- Define clinical and privacy boundaries.
- Prepare fictional data for safe prototype testing.
Next milestone
Build a test-only planner that converts a documented medicine instruction into a reviewable schedule and supply projection while refusing incomplete inputs.
Evidence required to advance
- Verified calculations across representative scenarios.
- Visible handling of missing and conflicting information.
- Usability findings from appropriate participants.
- Clinical, privacy and regulatory assessment.
Atari Eyes
Current stage: Research and early prototype design
Current work
- Define one controlled non-visual navigation scenario.
- Compare sensing options for nearby obstacles and paths.
- Explore understandable audio and vibration cue patterns.
- Define how uncertainty and sensor failure are communicated.
- Prepare participant and physical safety boundaries.
Next milestone
Demonstrate a controlled test rig that detects a nearby obstacle and communicates its relative direction with measured delay and confidence.
Evidence required to advance
- False-detection and missed-detection measurements.
- Communication delay measurements.
- Controlled usability findings.
- Documented failure and emergency-stop behaviour.
Staffing direction
Mahlis is currently founder-led. Hiring should follow validated work rather than adding roles before their responsibilities and expected results are clear.
Management
Coordinate priorities, funding, partnerships, risk and evidence-based milestone decisions.
Engineering and product
Build and test focused prototypes, document architecture and maintain understandable technical boundaries.
Clinical and accessibility review
Review assumptions, safety boundaries, user workflows and the evidence required before controlled testing.
Security and quality
Define testing, audit, recovery, incident response and controlled-release requirements.
Finance and administration
Maintain clear accounting, contracts, payroll planning, records and responsible use of funding.
Support and operations
Prepare documentation, training, feedback handling and dependable support for future pilots.
Mahlis intends to remain remote-first where a role permits it and to plan compensation around fair, liveable work. Staffing levels will grow gradually as prototypes, funding and operational duties are validated.
How progress will be reported
Public updates will describe completed work, current work, blockers, evidence and the next milestone. Internal version labels remain part of release management and will not replace clear public product language.