Selected proof projects

Projects that show how I turn messy business workflows into systems.

These are the fastest project surfaces for evaluating my current direction: backend-owned AI workflows, platform foundations, integration boundaries, DevOps/release discipline, CI, docs, and recovery paths.

Open DriveDesk proof route Open verification pack

Flagship direction

DriveDesk AI Operator / AI Sales & Support Workflow Platform

I build the backend-owned layer where documents, transcripts, call audio, CRM leads, and knowledge-base records become RAG-backed analysis, lead scoring, follow-up drafts, Telegram approvals, CRM actions, audit logs, retries, and runbooks.

FastAPI PostgreSQL / pgvector RAG Telegram approvals CRM adapters Backend-owned state

Ownership

  • State, audit, retries, idempotency, adapter contracts, and approval boundaries live in the backend.
  • n8n is used as orchestration, not as the source of truth.
  • AI tooling accelerates implementation while verification and shipped quality stay my responsibility.

Proof

Platform foundation

DriveDesk Core - Operations & Integration Platform

I use DriveDesk Core to show the foundation behind real operations software: tenants, RBAC, audit/outbox, workers, workflow rules, adapters, OpenAPI, SDK output, Docker, tests, CI, docs, and a public demo route.

FastAPI PostgreSQL RBAC Audit / outbox OpenAPI Public demo

Ownership

  • Public-safe platform proof for CRM/ERP-style operations workflows.
  • Integration and workflow behavior is documented through review routes, demos, and evidence files.
  • The goal is operable business software, not isolated scripts.

Proof

Runtime AI proof

AI Ops Workflow Kit - RAG, Transcript Analysis, Approval & CRM Handoff

I built this as the public runtime proof for AI workflow automation: document intake, transcript analysis, scoring, approval queues, Telegram callback handling, outbox processing, CRM dry-run handoff, smoke checks, and CI evidence.

RAG ingestion Transcript analysis Approvals Outbox worker Docker Live smoke

Ownership

  • Provider boundaries, reviewer acceptance, live proof, and public status are documented.
  • External CRM writes stay behind dry-run and approval boundaries until integration is intentionally enabled.
  • Evidence focuses on runtime behavior: API, worker state, callbacks, CI, and smoke checks.

Proof

DevOps product proof

DeployMate - Self-hosted Docker Deployment Control Panel

I use DeployMate to show DevOps and platform discipline around self-hosted deployments: FastAPI, Next.js, PostgreSQL, SSH runtime tooling, health/log views, admin workflows, release gates, evidence bundles, review packet export, and public-review gate.

FastAPI Next.js PostgreSQL Docker Compose SSH runtime Release gates

Ownership

  • Deployment, runtime review, admin surfaces, release safety, evidence packets, review packet export, and operational docs.
  • Public review path stays available even when custom-domain or staging conditions change.
  • Recent CI, production-contract, and public-review gates prove the default branch is not just static documentation.

Proof