I build the integrations, internal tools, and automation that connect how a business runs. Ten years inside my family's PR firm in Dallas as the only engineer: CRM, billing, six vendor APIs, and lately AI pipelines with a person holding the release button. Python and TypeScript.
Site: dallascrilley.com · Email: dallas@dallascrilley.com
- throughline-connector-kit: the four-method connector contract and sync engine behind six production vendor integrations, sanitized
- reconciler: billing discrepancy detection with a required human approval before any invoice changes, on synthetic data; a synthetic rebuild inspired by private Meter billing-audit work
- vouch: human review as an API, with offline end-to-end harnesses that use simulated reviewers
- shipwright: approved issue to reviewable pull request, with tests on the handoff between agent output and human review
- holdfast: append-only decision ledger and a human publish gate, rebuilt around a synthetic domain
The production systems these came from (Meter, Throughline, CoHost AI Studio) are private. The site tells each story, including which numbers are self-reported.
Most of this catalog was published in one pass while I assembled the portfolio, so a repo's first commit date is not its development timeline. Where the scaffold-versus-hand-written split matters, the repo says so (see Winnow's docs/receipts.md).
Agents commit under this login and I own the merge. Each repository's verification command has to pass before I merge, CI runs where it exists, and a person makes every irreversible call. Open any repo's history and the split is visible: agent commits carry implementation, my commits set direction, resolve review findings, and cut releases.