XATP Platform

The Challenge

At LedgerDomain, I was part of a startup team that built credentialed web applications for pharmaceutical supply-chain compliance under the Drug Supply Chain Security Act (DSCSA). The product needed secure portals for interoperable product tracing, enhanced verification, and exception management — interfaces that product, engineering, and regulated customers could trust in production. As Front-End Architect & Engineer on that effort, ownership covered architecture and delivery of the web application layer alongside contributions across the wider stack.

XATP supports interoperable, electronic DSCSA workflows across every trading partner — direct and indirect — alongside the stacks manufacturers already run. Every module reads from the same verifiable Address Book, so tracing, verification, and exception handling stay consistent instead of fracturing across disconnected lists and tools.

XATP Address Book

A core surface of XATP is the Address Book — a single system that connects people, organizations, sites, and licenses so DSCSA compliance data does not have to be pieced together by hand. Each trading partner becomes one governed record instead of scattered lists across multiple systems. Workflows are backed by OCI-compliant digital credentials, with manual fallbacks when needed.

Magic Portal

The Magic Portal is the branded DSCSA workspace for manufacturers to reach every trading partner — including those without VRS, credentials, or dedicated integrations. It replaces scattered VRS, email, spreadsheet, and phone workflows with one authenticated path for ATP checks, VRS-first verification with manual fallbacks, and Control Tower–linked trace or exception requests.

Constraints

• Compliance-driven workflows where correctness and auditability matter as much as UX polish
• Interoperable tracing and verification flows spanning secure portals and backend services
• Ongoing production ownership: triage, BAU maintenance, and feature delivery without disrupting availability
• Collaboration across product and engineering so requirements become testable plans and reliable CI/CD

Contributions

1. Owned front-end architecture end to end — led the front-end team on direction, patterns, and repository standards while shipping Vue.js, Vite, TypeScript, and Tailwind CSS against Go services.
2. Contributed to the backend Go API — worked on API surfaces and handlers that power portal workflows, so front-end features landed with matching server support.
3. Built and iterated Address Book experiences — trading-partner records spanning people, organizations, sites, and licenses, with credential-backed workflows and manual fallbacks.
4. Shipped XATP user workflows — authenticated partner access, VRS-first verification with manual fallbacks, and request history tied to Control Tower records.
5. Prototyped to de-risk requirements — built workshop and customer-facing prototypes to gather feedback early, then iterated toward production-ready portals.
6. Treated production as a first-class concern — high-availability support for triage, fixes, and feature work alongside dependency hygiene and CI/CD pipelines.

Outcomes

The portals support interoperable DSCSA workflows — tracing, verification, and exceptions — on a shared Address Book foundation, with Magic Portal and Control Tower–linked request records. I kept front-end repositories current, contributed across the Go API when workflows required it, enforced standards across the team, and provided continuous production support as requirements and regulations evolved.