What I help with Where it fits Proof How I think Start Use case builder Work with me
Human-centered AI, systems that survive reality

Hi, I'm Nova. I can turn your data into useful and private technology.

Twenty years shipping software inside higher education, now doing frontier-AI build work. I make capable AI run on private institutional data without that data ever leaving the building.

move your cursor, the knowledge graph is listening

scroll
What I can be useful for

Pick what sounds like your hurdles.

Every card is a conversation starter. They are ordered by how hard the skill is to find, not just how trendy it may sound. Tap "good to know" on any card for the candid technology read: where it is strong, and where it is not.

Filter:
Rarehigher-ed native

Private AI platforms inside real institutions

Ship a real AI application behind the single sign-on, the privacy law, and the procurement, not a demo.

The live system is PATHS Engine, built at the University of Delaware: a multi-region AWS platform with a Neo4j knowledge graph, SAML single sign-on, SageMaker embeddings, and Bedrock generation. Tens of thousands of graph nodes, running in production behind a campus login.

Where it is strong, where it is not

Most AI engineers have never shipped inside FERPA, campus networking, and institutional procurement. That is what makes this my rarest skill. Transparency: I invented PATHS Engine. The University of Delaware holds the IP. I surface it here not to represent it as my own product, but because it is the clearest proof of what I can build inside an institution. If your institution is interested in PATHS Engine, reach out and I will connect you with the right people at UD. This kind of engagement works best as an ongoing collaboration, not a single project.

Rare

On-prem and model-agnostic AI, where the data never leaves

Run useful AI entirely on hardware you control, and swap the model without rewriting the app.

A containerized workspace points at a local model, a machine on the LAN, or a frontier API behind a single config switch, with read-only model mounts and an optional strict-network mode. The same rule holds across projects: the full model never leaves, only tiny adapters move.

Where it is strong, where it is not

Regulated sectors increasingly want AI that does not ship data to a vendor, and model-agnostic design hedges against lock-in and sudden price changes. The competing pitch, "your data stays in your own cloud tenant," is easier to buy than to self-host, so I have to defend why local beats a private endpoint, and how currently local-model quality has a real ceiling. Best where sovereignty is a hard requirement, and finding the right balance of frontier-AI and local-model quality is a challenge.

Rarehigher-ed native

Federated learning across institutions

Train one shared model across several organizations while each one's data stays home.

A real Flower setup co-trains a small open model across simulated campuses, sharing only a couple of megabytes of LoRA adapters per round, with IID and non-IID data splits. A Delaware pilot backs it with a partner overview and a human scoring rubric.

Where it is strong, where it is not

When privacy law blocks organizations from pooling data, federated learning is the standard technical answer. The candid read: Task specific ai models are a better fit for most institutions. But they are new and not yet widely adopted. If you are interested in federated learning, I can help you get started with a small pilot.

Rare

Fine-tuning small open models on private data

Make a small open model good enough at one institution-specific job, on commodity hardware.

Instruction-tuning on flashcard data with an Apple-Silicon training loop and ROUGE evaluation; a small LoRA classifier with real adapter checkpoints; and a full chain from a curriculum graph to generation to human-scored export to a fine-tuned model.

Where it is strong, where it is not

Clients with private data and limited budgets want a model they own that runs cheaply. The honest part: fine-tuning is frequently the wrong answer, and good prompting plus retrieval on a strong base model often wins. I lead with "do you even need to fine-tune," then deliver if the answer is yes.

In demand

Retrieval and knowledge-graph grounding

Answers tied to their sources, using vectors, a graph, or both, with hallucinations engineered out.

A Neo4j knowledge graph combined with embeddings and topic extraction into structured learning objects, plus a strict rule in one project that every extracted claim must be a verbatim substring of its source.

Where it is strong, where it is not

"Chat with our documents" is the default ask, and grounding is exactly where most implementations fall down. Basic retrieval is commoditizing fast, so the technology alone will not command a premium. My edge is the grounding discipline and the graph modeling, which clients tend to underrate until a bad answer costs them something.

In demand

Honest AI evaluation and measurement

Prove whether an AI change actually helped, using graders that do not flatter the model.

A capability-lift harness with a deterministic grader contract, verbatim-grounding validation after each model call, and human scoring rubrics for educational content rated on usefulness, correctness, source grounding, and pedagogical value.

Where it is strong, where it is not

Many teams have shipped AI features and cannot tell whether they work, so honest measurement stands out against vendors who grade their own homework. The candid read: my own eval tooling is early and the field has funded players. I sell the discipline and the deterministic-grader rigor, and I am upfront that the tooling itself is young.

In demand

Human-in-the-loop data pipelines

Turn raw institutional content into reviewed, scored, model-ready training data.

A pipeline that generates case studies, routes them through a review-and-scoring interface, and exports the approved ones as training data, orchestrated for concurrency, with state-machine review agents that put a human in the loop.

Where it is strong, where it is not

Good fine-tuning and good evaluation both die without good data, and most organizations have no pipeline for producing it. The honest limit: the value depends on the client supplying subject-matter reviewers, which is usually the real bottleneck, and the output quality at scale is not yet shown. It needs careful framing, because it is the highest-leverage step even when it reads as unglamorous.

In demand

Agentic systems and reusable tooling

Agents that hold state, hand off to humans, and reuse documented skills instead of starting cold.

State-machine dialogue agents with shared cloud and graph utilities, plus a command-line tool that catalogs, searches, and lints the reusable "skills" agents read, treating skills as a compounding multiplier across projects.

Where it is strong, where it is not

Agentic workflows are the dominant theme of the moment, and tooling that manages prompts and skills as versioned assets is underserved. This is also the most crowded space here, every framework is fighting for it, and my agent code is personal-scale rather than a hardened product. I sell the patterns and the discipline, not the specific tools.

Foundation

Full-stack application engineering

Ship the whole thing: backend, database, frontend, and the streaming interface on top.

Flask and PHP backends, a substantial scheduling app with a full database schema and calendar integration, server-sent-event token streaming, and a React-and-D3 front end for graph visualization.

Where it is strong, where it is not

Every AI project still needs a working application wrapped around the model, and building that myself means no handoff and one person who understands the whole path. This is table stakes, though. It will not win a bid on its own. It matters as evidence that I can deliver end to end.

Foundationhigher-ed native

Accessibility and multimodal engineering

Real-time media features for learning, from audio-described lectures to perception in a room.

A browser extension for lecture audio description with scene-change detection, silence-gated speech, and live and replay modes, plus a camera-feed prototype with gesture detection and vision-model recognition.

Where it is strong, where it is not

Accessibility compliance is a standing budget line in education and government, and AI-assisted accessibility is an underserved niche. Be careful here: the description endpoint is currently a mock and the camera work is an early proof of concept, so the AI parts are designed more than shipped. I sell the client-side engineering and the accessibility framing honestly, without implying a finished product exists.

Foundationhigher-ed native

Twenty years of shipping, with higher-ed fluency

A long record of shipping, plus knowing how a university actually works.

The whole portfolio, and specifically the higher-ed-native choices: single sign-on, FERPA-shaped design, university deployments, and faculty-facing documentation that real instructors use.

Where it is strong, where it is not

Domain fluency shortens every engagement and de-risks delivery, and a twenty-year record of shipping is a trust signal that hype cannot fake. The honest framing: experience is a multiplier on the skills above, not a product I can invoice for on its own. It gets me in the room and keeps me there.

Where this can help you

Different worlds, concrete entry points.

Switch the view to see where I tend to fit. The goal is to help friends, family, colleagues, and project leads recognize where a real collaboration could begin.

Faculty and student support

Tools that help instructors and students work with course content more intelligently.

  • Transcript-to-study-aid workflows
  • Faculty review dashboards
  • AI-generated case studies with human scoring
  • Course knowledge graphs and topic maps

Institutional AI pilots

Pilots that do not collapse under privacy, governance, or evaluation questions.

  • Use-case selection and scoping
  • Data boundary planning
  • Reviewer rubrics and escalation logic
  • Federated collaboration across campuses

Mission-centered knowledge systems

Help organize the knowledge already living in documents, meetings, and people's heads.

  • Resource and program knowledge bases
  • Community intake workflows
  • Private AI assistants for internal use
  • Grant and reporting knowledge maps

Ethical automation

Automate the boring parts without automating away care, consent, or community trust.

  • Volunteer coordination
  • Case notes and summaries
  • Donor and program reporting
  • Human review before any outreach

Operations cleanup

Make the invisible work visible, then automate the parts that are safe and useful.

  • Calendars, forms, and spreadsheet cleanup
  • AI-assisted document routing
  • Internal dashboards
  • Custom lightweight apps

AI without the circus

Separate hype from practical value, then build a small thing that proves the point.

  • AI workflow audit
  • A retrieval prototype on your own data
  • Staff training in plain language
  • Prototype-to-production planning
Proof that I ship

Durable systems, not clever demos.

These are the patterns behind the pitch. Real things, running for real, drawn from a survey of seventeen project directories.

Lecture capture at campus scale 200+ rooms / 15+ yrs / 300+ classes a semester

Built and deployed end to end: Mac Minis running Zoom on the backend, Google Calendar scheduling, and connections into Kaltura and Canvas. That kind of long-running infrastructure is not theoretical.

A production AI platform behind university login ~30,000 graph nodes

PATHS Engine transforms unstructured academic content into structured, institution-scale knowledge. A multi-region platform hosted on AWS or on PREM: Neo4j knowledge graph, SAML single sign-on, SageMaker embeddings, Bedrock generation. We are currently integrating use of local models! Live in production at the University of Delaware. I am a co-inventor of this system. The university holds the IP. If your institution is interested in what PATHS Engine does, I can connect you to our team.

AI learning systems with human review

Workflows that transform course transcripts into topics, study aids, case studies, flashcards, and reviewable learning objects, with faculty validation before anything reaches a student.

Federated learning across campuses

A multi-institution pilot where universities collaborate on educational AI models while every institution's data stays local. Only tiny model adapters cross the wire.

How I think about AI

These are not disclaimers. They are design principles.

They shape architecture, workflow, evaluation, and who gets a voice in the room.

Privacy is architecture

It cannot be sprinkled on after launch. It shapes where data lives, which models run, who sees outputs, and what leaves the organization.

Humans stay in the loop

AI can draft, summarize, and suggest. People still review, judge, contextualize, approve, and challenge.

Evaluation is care

If a system touches learning, resources, or trust, it needs rubrics, samples, and thresholds. "Looks good" is not enough.

Impact before novelty

The best project is not the flashiest one. It is the one that helps real people and survives after the demo glow fades.

Local knowledge matters

Institutions already hold wisdom. The work is to structure, protect, and activate it, not replace it with generic answers.

Build with people, not at them

Good systems include the people affected by them: faculty, staff, students, reviewers, and the folks doing the daily work.

How to think of me for a project

Bring me in when an idea needs to become a real system.

If a project has valuable knowledge, messy workflows, privacy concerns, human-review needs, or an AI idea that needs grounding, I can help scope it, design it, build a prototype, evaluate it, document it, or translate it for the people who need to understand it. That holds whether you are one person turning an idea over or a business weighing a bigger move. Sometimes the most useful thing is a single good conversation, sometimes it is a system that runs for years.

Best-fit work: higher education, nonprofits, community organizations, learning and knowledge systems, privacy-aware AI, local-model workflows, and small teams that need senior technical judgment.

Good ways to start a conversation