Vietnam-based open-source maintainer building deterministic contract layers for coding agents, repository governance, and reproducible research workflows.
I keep one rule across the portfolio: make the boundary explicit, make the output reproducible, and attach every adoption claim to public evidence.
The projects below are one portfolio, not unrelated demos:
| Project | Purpose | Start here |
|---|---|---|
| PatchGate | Checks whether a GitHub pull request has the policy, evidence, ownership, and human boundaries needed before review | first use · beta release |
| contribkit | Compiles a repository's contribution contract and preflights a local diff before a pull request is opened, with 13 bundled test-runner adapters (pytest, npm, go, phpunit, rspec, cargo, dotnet, ctest, bun, deno, swift, mix, maven) | quickstart · npm |
| agentsmd | Keeps AI-agent instruction files wired to one source of truth, with linting, sync, and scoring | README · npm |
| OpenSheet-AI | Turns typed spreadsheet operations into validated plans, dry-run receipts, and controlled workbook writes | quickstart · npm |
| quant-research | Checks research instruments, recodes, coverage, and measurement specifications before analysis | reproducibility · npm |
- Five original public tools are active; the remaining public repositories are forks, a smoke-test fixture, or profile/supporting material.
- Four packages are published on npm, all explicitly pre-release.
- A 2026-09-06 maintenance pass reviewed and merged the full open review
backlog across the five repositories, including a user-first README
restructure, a replayable governance Case Lab for PatchGate, Prow
OWNERSdiscovery (classification only — it never creates a blocking rule), and adapter-family expansion for contribkit. All merges are recorded maintainer decisions, not independent-review evidence. - Flecto #145 was merged after maintainer review. It added a GitHub Actions policy pack, fixtures, documentation, and a 628-test validation pass; the maintainer recorded me in the contributor list.
- I also have active upstream work in nDspec #116 and OpenSSF Scorecard #5192.
These projects are pre-release. I do not claim external adoption, dependent repositories, 20-contributor community status, or download thresholds unless the repositories or registries make that evidence visible.
- Try PatchGate or contribkit against a disposable repository in their documented non-blocking paths.
- Report the exact command, runtime, and observed output in the relevant issue.
- Review an open issue or pull request, especially the clean-consumer and adapter fixtures linked from each project.
The longer account of the maintainer workflow is in How this repo is built. Tests, clean-room checks, release metadata, and public CI decide what can be claimed; documentation-only work is labeled as such.