FinCredit Copilot
Next.js · FastAPI · RAG

AI application and Agent engineer turning real-world workflows into AI systems people can actually use.
Coding with Jorlin. I build intelligent agents, knowledge retrieval, workflow automation, and reliable human-in-the-loop experiences.
Three end-to-end systems built around code security, sales operations, and financial decision support.
A compact record of the problems I owned, the systems I built, and the evidence that the work held up.
Apr 2026 — Present
Owned the path from problem framing and architecture to interface design, evaluation, and reproducible delivery across three public AI systems.
Jul 2025 — Jan 2026
Translated engineering requirements into executable models and validation workflows, building the systems mindset now applied to reliable AI products.
Master’s in Electronic Information
B.Sc. in Electronic Information Science and Technology
Graduate Academic Scholarship · Second Class
China Undergraduate Mathematical Contest in Modeling
Team captain
1 EI-indexed first-author paper · 1 invention patent application (second inventor)
Model APIs · prompting · structured output · tool calling
LangGraph · runtime harness · state · checkpoints · human approval
BGE-M3 · BM25 · RRF · chunking · grounded generation
Python · FastAPI · Pydantic · REST workflows
PostgreSQL · SQLite · Redis Streams · conversation memory
n8n · CRM / Notion sync · webhooks · idempotency
pytest · retrieval metrics · eval sets · Ruff · mypy
OpenTelemetry · Prometheus · logs · traces · failure analysis
TypeScript · React · Next.js · bilingual interaction design
Docker · CI checks · reproducible local and public demos
A practical architecture for long-running agents: explicit state, token and time budgets, idempotent tools, checkpoints, retries, and validation gates. The key question is not whether an agent can finish once, but whether a failed run can be explained, resumed, and evaluated without repeating completed work.
Why dense vectors and BM25 fail in different ways, how reciprocal rank fusion combines them without pretending their scores are comparable, and how Hit@k, MRR, nDCG, citation coverage, and answer faithfulness reveal different failure modes in a small production-minded RAG system.
A conversation is not a single request. This note separates conversation IDs, message IDs, and idempotency keys; models a PostgreSQL-backed event history; controls context windows; and uses a transactional handoff so CRM or Notion writes remain replayable instead of becoming hidden side effects.
An engineering boundary for financial AI: use retrieval for policy evidence and language models for explanation, but keep DTI / LTV calculations, policy versions, approval permissions, and final decisions in deterministic and auditable components with explicit human checkpoints.
Have a role, a project, or an awkward workflow that might benefit from AI? Send me a note.