AMC
How can a telemetry pipeline change its vector format without losing the relationships an AI model needs?
From describing music to studying the geometry of data.
Research provenance
My research took shape through engineering work at NASA, where I developed AMC, AMC-Edge, Gemini Drift, SRCV, USAspending / IDAS, AURORA and DEMETER. Much of my foundational work in mathematics and manifolds grew from that same experience.
Gemini Drift became SCJ. I pursued the later SCJ security research and KRAKEN at IBM. My work with Mach Industries includes ICARUS, developed in collaboration with Dr. Ryan Rapetti, and FAL-CORE, the flight-control blog that grew into The Geometry of Flight.
My CrowdStrike work includes The Geometry of War and Psychohistory. I collaborated with Dr. Paolo Di Prodi to refine the Psychohistory analysis tool. I developed BRIDGE and the remaining areas of my research independently.
I am an engineer and independent researcher studying how the structure of a measured system can be carried into computation. My path began in machine learning at Pandora in 2009 and took shape through engineering work at NASA. It took nearly fifteen years to put a mathematical question to a lesson I had learned early: how we describe data determines what we can learn from it.
01 / Origins
I joined Pandora as an early engineer working on its machine-learning platform. The Music Genome Project’s carefully curated musical descriptions offered a lesson that stayed with me: useful computation begins with deciding which relationships to record.
Trained musicians described music through its characteristics. Those descriptions helped make similarity something a machine could work with. I came to see curation as a way of giving data a useful shape—a choice about which distinctions mattered before any prediction was made.
My own work included audience modeling, contextual prediction, ad automation and streaming analytics. Across the engineering roles that followed, I kept returning to that curatorial approach.
02 / The turning point
Principal Software Engineer
Via MRI Technologies / Navteca
In 2024, I was embedded with the Project Luna engineering team at NASA’s Johnson Space Center. Luna was a shared environment for research, simulations, digital assets and collaboration. Roughly two terabytes of telemetry were arriving each day, and I was tasked with making that data usable by AI. Before a model could help us decipher it, I had to decide how to represent it.
I reached back to what I had learned at Pandora: useful machine learning begins with how we describe the data. I needed to turn the telemetry into vectors, but I did not want to force every observation into the same fixed format. I developed Adaptive Multi-Vector Correlation (AMC), an approach that adapted the encoding to the data and tracked the relationships between its different representations.
Then something shifted. As I worked with those vectors and watched their patterns change over time, I began to see the topology of the data—its shape, its connections, and the relationships that persisted through change. What had started as a practical task of preparing telemetry for AI became a different question: could those relationships guide the computation itself?
That was the turning point in my research. AMC gave me a concrete engineering problem from which to develop the mathematics of representation: what should remain the same when a description changes, and how can we tell a change in the system from a change introduced by its encoding? The intuition came from working with the data; the work that followed was to give it definitions, tests and mathematical conditions.
Katherine Johnson and Dorothy Vaughan were sources of inspiration. I wanted to contribute something useful to the mission through the quality and inventiveness of my engineering. I had not set out to begin a research program. I was trying to understand the data in front of me.
NASA / Foundational papers & engineering records
Five records connect adaptive representations with edge inference, software analysis, build integrity and investigative data provenance.
How can a telemetry pipeline change its vector format without losing the relationships an AI model needs?
When can an edge inference system reduce numerical precision without exceeding its timing or detection-error budgets?
When a patch fixes one function, where else might the same missing safeguard remain?
Does the software running on a science platform correspond to the build that was approved?
Can an analyst trace a suspicious spending-data pattern back to trustworthy records and the exact checks that flagged it?
A colleague’s perspective / Project Luna
“Bee’s work on Luna made a real impact, from designing threat models to shaping safer coding practices and frameworks the whole team could rely on.”
“Bee is generous with her knowledge and has a knack for explaining complex concepts in a way that sticks.”
Developed Adaptive Multi-Vector Correlation to prepare high-volume telemetry for AI through adaptive vector formats and cross-format translation.
Developed precision-adaptation work around execution-time bounds, fault guards and deterministic rollback.
Developed software inventory/runtime concordance verification for James Webb Space Telescope ground and data infrastructure, producing differential analysis for review.
Developed semantic analysis of patched flight software to identify related code patterns for investigation. This work became SCJ.
Specified pipeline-integrity checks, schema governance and traceable evidence bundles for human review of spending-data patterns.
Principal Engineer · Via Navteca
Earlier NASA work included modernizing AWS and Kubernetes environments, policy-as-code baselines, container approval workflows, GPU guardrails and platform-integrity evidence flows.
03 / A research program
What began as a lesson in describing music became a research program about representation. I began investigating related questions across domains: which descriptions preserve a system’s structure, which identify distinct states as equivalent, and what is lost when we translate between them?
I have built a fiber-bundle database and computational tools to explore these questions. My aim is to connect the translations engineers implement with the geometry they preserve—or fail to preserve—and derive usable bounds on the resulting error. Each application needs its own assumptions, comparisons and evidence.
Working independently has taught me to return to earlier results. When I find an error in a test or proposed proof, the work is to correct the method, revise the conclusion, or retract the claim. That responsibility is part of the research itself.
I am seeking a research home that will mentor me, challenge my arguments and hold the work to demanding standards. I bring experience building systems, a willingness to make testable predictions, and a commitment to following the evidence when it changes my mind.
04 / Education
Independent study in differential geometry, spectral theory, category theory and gauge theory complements my formal education and engineering practice.
Principal Adversarial Intelligence Engineer · 2024–2025
VIVID adversarial analytics, LLM-assisted investigation workflows and semantic code analysis.
Humana · Aetion · Eaze
Security engineering, privacy, encrypted data pipelines and incident response.
Head of Machine Learning & Security Engineering · 2012–2016
Machine-learning and anomaly-detection platforms connecting data infrastructure with security analysis.