An application over an agent API
The data platform enforces what each user can access. The agent works within those permissions.
Conceptual view
An AI assistant for technical service teams
Service teams needed to find information spread across technical manuals, parts catalogs, and operational systems. The assistant had to respect source permissions and handle uncertain results.
My work
I built the Blazor frontend on .NET, designed authorization, and designed and implemented the infrastructure and CI/CD flow. My role grew from API support into technical leadership and some project coordination, with ongoing responsibility for backlog preparation, planning, code review, and developer support.
Separate domain behavior from presentation
I worked on the integration contracts and separated shared instructions about how the company organizes and presents its data from application-specific presentation instructions for our custom frontend components. The endpoint and contract were designed with future application reuse in mind, including access to the same data and tools.
Enforce access in the data platform
I designed the access approach around the client’s custom OIDC provider, a token exchange with Azure Databricks, and on-behalf-of access. Unity Catalog applies data permissions for each user, so access is enforced by the data platform rather than decided by the AI agent.
Define infrastructure and delivery in code
I designed and implemented the infrastructure and CI/CD flow across the solution. Bicep defines the Azure infrastructure, Terraform manages Databricks access policies, and Azure DevOps Pipelines handles the CI/CD flow.
Where things stand
The team delivered the application through pilot in a production environment. A limited-user release is planned for November 2026.
Jul 2025–present