SYSTEMS
Existing Is Not the Same as Solved
An existing workflow can still be unsolved when the underlying experience or model remains weak.
Read note →AdityaDimri
Technical Founder
Software Engineer
Founder & CTO
SIFAKA LABS
Current work
TravelnFlex
B2B2C travel platform moving booking and coordination logic into an end-to-end system.
Role: Founder & CTO
Period: 2024–present
Booking
Identity
Payments
Platform
Under the product
Systems
Selected engineering layers currently exercised through TravelnFlex.
- Identity & Authorization
Authentication and authorization boundaries for stable identity, role ownership, and administrative access.
- Authentication boundaries
- Authorization
- Role ownership
- Admin identity binding
TravelnFlex
Inspect system → - Booking Lifecycle
Booking state and coordination boundaries across traveler, agency, and package workflows.
- Booking state
- Traveler / agency coordination
- Package logic
- Workflow transitions
TravelnFlex
Inspect system → - Payments & Refunds
Payment lifecycle boundaries covering gateway integration, webhook handling, and refund state.
- Payment lifecycle
- Gateway integration
- Webhook handling
- Refund state
TravelnFlex
Inspect system → - Platform & Production Architecture
Application boundaries and production concerns across traveler, agency, and administrative surfaces.
- Application boundaries
- Traveler / agency / admin surfaces
- Environment separation
- Production hardening
TravelnFlex
Inspect system →
Questions in public
Notes
Short observations on systems, product judgment, and the questions left after building.
Email is a contact attribute, not the whole identity model.
IDENTITY / Aug 2026
Rebuilding is justified when the constraint is structural and the desired behavior is understood.
ARCHITECTURE / Aug 2026
Current direction
Keep moving toward harder problems.
Build what the problem still needs. Test the model. Follow the evidence.