Skip to content
View davidnichols-ops's full-sized avatar
  • 13:07 (UTC -06:00)

Block or report davidnichols-ops

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
davidnichols-ops/README.md

David Nichols

I work on computer vision, inference reliability, and tools for inspecting and controlling what AI agents do.

I'm especially interested in the parts around the model: preserving data through a workflow, understanding runtime failures, and making decisions traceable to code and policy. Most of my work is in Python, with JavaScript for MCP tooling and a particular interest in Apple Silicon.

Projects

  • trustcard — tooling for inspecting MCP servers, signing capability manifests, detecting changes, and enforcing which tool calls are allowed. Available as mcp-trustcard.
  • Apple Quality Recognition Engine — an apple-grading prototype that separates visual observations from a versioned grading policy. The current work centers on annotation, case review, and human-approved training data. It does not yet include a trained apple checkpoint or a validated commercial grading system.

Selected upstream contributions

These are merged contributions to projects maintained by their respective teams.

Project Contribution
Roboflow Inference Reuse a run-scoped thread pool for workflow execution
Roboflow Inference Preserve image metadata on empty Template Matching results
Roboflow Python SDK Return upload results to callers
TensorFlow Fix XLA DenseBincount negative-input validation for runtime tensors
Ultralytics Exclude Sigmoid from TensorRT INT8 quantization

More merged contributions

How I work

I like understanding a system well enough to explain why it failed. I'm building that judgment through debugging, code review, and maintaining my own tools.

  • Start with a reproducible failure and keep fixes focused.
  • Add regression coverage and report exactly what was tested.
  • Keep model outputs, policy decisions, and human approval separate where the application calls for it.

Older repositories include experiments and archived work. Their READMEs describe their status; the two projects above are my current focus.

Pinned Loading

  1. apple-quality-recognition-engine apple-quality-recognition-engine Public

    Edge-first apple quality recognition engine. YOLO26 detection + deterministic grading policy engine, CoreML FP16 on Apple Neural Engine (M4). Detection identifies, algorithms decide.

    Python 2

  2. trustcard trustcard Public

    Cryptographic trust infrastructure for MCP servers — signed manifests, TOFU pinning, two-gate enforcement, and the "npm audit" scanner.

    JavaScript 4