For researchers & academics
A collaborator, not a vendor
I work with research groups as a methods collaborator — systems modeling, network analysis, geospatial and data work, and a published method for turning a literature into source-traceable causal models — on work meant to survive peer review. I'm most useful when the methodological question is genuinely open and you'd rather think it through with someone than hand it off. If what you need is a defined deliverable on a fixed timeline, a vendor may serve you better, and I'll say so.
The shape of it
How this tends to work
How I work with researchers
Co-authorship where the intellectual contribution warrants it, not as a default — I'd rather earn a spot on the paper than assume one. The artifacts I build are reproducible and open-source, so a reviewer or a future student can rerun them without me in the room. And I try to be honest about uncertainty in the method itself: where a modeling choice is defensible, where it's a judgment call, and where the result would change if we chose differently.
The record
16 published works, and the method behind the provenance discipline is published rather than an in-house tool. I'll keep the proof light here because it overlaps the method lane and the publications — the record lives on ResearchGate ↗, and the publications page collects the papers with links.
If the real question is verification
If your question is really about making an analysis or a model checkable — reproducible, source-traceable, defensible under scrutiny — the method & verification lane is the sharper fit, and the method and the AI angle are laid out there in full.
Other lanes: enterprise & compliance · foundations & nonprofits · method & verification.