Context
The Unified Data Library is a U.S. Space Force data environment. The connector had to move sensor data from U.S. and allied partners into that environment through a production streaming system, under federal contracting and export-control constraints.
My role
I owned the production connector work and supported the full sales-engineering lifecycle: discovery, technical design, stakeholder presentations, implementation, and integration support. I later carried the same connector discipline into Staff-level platform work.
System shape
The connector was built on Conduit, Meroxa's open-source Go streaming framework. The implementation followed patterns that external developers could extend rather than burying integration logic in one customer-specific path.
At the Staff level, I also built an HL7-to-FHIR processor and connector patterns for healthcare, maritime AIS, Oracle, S3, and tactical-data sources. The common problem was reliable movement between systems with different schemas, protocols, and operating constraints.
Results
What the work demonstrates
- Production Go in a real streaming platform.
- Requirements work with federal stakeholders before implementation.
- Reference patterns other developers could integrate against.
- Delivery across technical, compliance, and commercial constraints.
- Staff-level reuse of connector architecture beyond one program.
Evidence boundary
The AFRL award and contract-vehicle ceiling are public procurement facts. The $9.925M attribution comes from internal employment records and is labeled accordingly. Sensor schemas, partner data, private source code, and restricted architecture details are excluded.