Software engineer and Computer Science student focused on building reliable backend systems, modular platforms, and production-ready software.

I specialize in designing software with clear boundaries, deterministic behavior, strong testing, and operational visibility. My work spans backend development, workflow orchestration, event processing, artificial intelligence infrastructure, and business-focused web applications.

I’m building a layered software ecosystem where each system has a focused responsibility:

• A.I.L. — AI Intelligence Layer
  A modular intelligence platform for prompt management, provider selection, memory retrieval, execution reliability, and explainable decision visibility.

• SignalForge
  A detection and alerting platform that evaluates signals, applies rules, manages alert lifecycles, exposes metrics, and triggers downstream automation.

• ChronoFlow
  A workflow orchestration engine for validating, deduplicating, routing, executing, and tracking structured workflows.

• BeaconFlow
  An event-ingestion foundation designed around clean boundaries, reliable processing, and scalable system integration.

• ControlPlane
  An operator-facing dashboard that combines execution, alert, trace, analytics, and decision visibility across the platform.

• ClientForge
  A multi-tenant foundation for identity, users, tenants, authentication, and system boundaries.

Alongside the platform ecosystem, I am also building production-focused applications that solve real business problems.

A mobile-first load, expense, and profitability platform for owner-operators and lease-purchase truck drivers.

Axleledger helps drivers track the numbers that determine whether their trucking business is actually profitable.

Current capabilities include:

• Secure Supabase authentication
• Load creation, tracking, and management
• Operating-expense tracking
• Revenue and profit visibility
• Reporting-period controls
• Recent business activity
• Responsive mobile and desktop workflows
• Production deployment through Vercel

Built with: Next.js, TypeScript, React, Supabase, PostgreSQL, Tailwind CSS, and Vercel

• Artificial intelligence is a dependency, never the core
• Domain logic should not leak across system boundaries
• Detection and orchestration are separate responsibilities
• Build systems, not disconnected scripts
• Prefer deterministic behavior over hidden behavior
• Make important decisions observable and explainable
• Test behavior before expanding complexity
• Evolution is not deviation; it is convergence

My primary areas of focus include:

• Backend services and REST APIs
• Modular monoliths
• Clean Architecture
• Workflow orchestration
• Event-driven systems
• Artificial intelligence infrastructure
• Authentication and multi-tenant systems
• Decision and execution visibility
• Relational database applications
• Automated and integration testing
• Production-focused business software

• C#
• TypeScript
• SQL
• Python
• C++

• .NET 10
• ASP.NET Core
• Minimal APIs
• Next.js
• React
• Tailwind CSS

• PostgreSQL
• Entity Framework Core
• Supabase
• SQLite
• Docker
• Vercel

• Clean Architecture
• Modular Monoliths
• REST APIs
• Event-driven design
• xUnit
• Integration testing
• Contract testing
• GitHub Actions

• Git
• GitHub
• Linux
• Visual Studio Code
• Swagger / OpenAPI
• UTM virtualization
• Nginx

A platform capability that controls how artificial intelligence is used inside larger software systems.

Key capabilities include:

• Prompt registry with versioning and lifecycle management
• Provider registration, selection, and fallback
• Replaceable agent execution layer
• Memory storage, retrieval, filtering, and ranking
• Reliability and execution telemetry
• Decision explanations and trace visibility
• Repository-backed persistence
• Strict separation between intelligence and core business logic

A.I.L. is designed as infrastructure—not as a chatbot wrapper.

A rules-based detection platform supporting:

• Signal evaluation
• Rule lifecycle management
• Alert creation and enrichment
• Acknowledgement, resolution, and reopening
• Alert metrics
• Audit history
• Automation triggers
• Decision visibility

A workflow orchestration platform supporting:

• Control-trigger intake
• Validation and deduplication
• Workflow routing
• Execution-instance tracking
• Execution history
• Correlation and traceability

A modular closeout workflow platform built with ASP.NET Core Minimal APIs, SQLite, Swagger, xUnit, and GitHub Actions.

A production-oriented media workflow product covering assets, clips, advertising, scheduling, publishing intent, analytics visibility, and YouTube publishing workflows.

I use Linux and Windows virtual machines to build hands-on experience with:

• Linux command-line administration
• Users, permissions, files, and services
• Nginx configuration
• Networking and troubleshooting
• SSH and secure file transfer
• Virtualization
• Break/fix exercises
• Cybersecurity fundamentals
• Cloud and systems concepts

I am pursuing a Bachelor of Science in Computer Science with a concentration in Software Engineering at Southern New Hampshire University.

Before moving deeper into software engineering, I built extensive experience in trucking and logistics. That background strengthened my ability to work independently, manage time-sensitive operations, troubleshoot under pressure, document accurately, and understand the real cost of unreliable systems.

I bring that same operational mindset into software development:

Understand the workflow, protect the boundaries, test the behavior, and build systems people can trust.

• Portfolio: loucarron.dev
• Axleledger: www.axleledger.com
• GitHub: github.com/lourosscs50
• Email: louross101@gmail.com

Evolution isn’t deviation. It’s convergence.