Cloud-native backends, Kubernetes-shaped systems, and patches that last.
I like backend work that gets close to real infrastructure: Kubernetes resources, auth boundaries, storage, networking, CI, and the quiet glue that turns a feature into something maintainers can actually merge.
- Platform backends: APIs that manage real cluster resources, not just rows in a database.
- Kubernetes edges: Services, Ingress, cert-manager, RBAC, StatefulSets, storage, pod logs, and exec paths.
- Open-source maintenance: small fixes with a reproduction, a reason, and tests when behavior can regress.
- Agent infrastructure: memory, retrieval, tool calls, and the backend paths agents need when they leave the demo.
- I read the surrounding code before touching the line that looks guilty.
- I prefer boring patches in the best sense: narrow, explainable, and easy to review.
- I enjoy the part where a vague bug becomes a concrete failing path.
- I tend to build bigger ideas in a fork first, then upstream the pieces that have earned their shape.
- I care about the last 20%: names, error paths, tests, and whether the next maintainer can follow the trail.
| Repository | Why it is here |
|---|---|
| casosorg/casos | Upstream patches around Kubernetes resource management, RBAC, Services, StatefulSet storage, node deployment, and backend E2E coverage. |
| bugkeep/casos | A working fork for larger platform ideas: HTTPS via cert-manager, role binding UI, quota pages, web pod exec, log search, and execution history. |
| TencentDB Agent Memory | Notes and issue-practice work around layered memory, hybrid retrieval, and agent memory as backend infrastructure. |
| casdoor/casdoor | Auth, OIDC, and identity-system code I keep close because platform backends eventually meet permissions. |
| apache/casbin-pycasbin | Policy-engine reading ground for RBAC details and permission-model thinking. |
- casosorg/casos#86 - fix: add Playwright UI smoke and worker-node deploy/repair regression tests (merged 2026-06-30)
- casosorg/casos#84 - feat: add backend e2e ui tests (merged 2026-06-26)
- casosorg/casos#74 - feat: add automatic worker node deployment (merged 2026-06-24)
- casosorg/casos#72 - fix: restore local access for NodePort services (merged 2026-06-21)
- casosorg/casos#73 - feat: add PVC mount support for StatefulSets (merged 2026-06-21)
- casosorg/casos#71 - fix: support ExternalName services in service management (merged 2026-06-20)
- casosorg/casos#70 - fix: reject invalid roleRef kind for cluster role bindings (merged 2026-06-19)
- casosorg/casos#69 - fix: require sign in for protected API endpoints (merged 2026-06-19)
- MoonshotAI/kimi-cli#2132 - fix(acp): replay session history on load (merged 2026-05-28)
- web3infra-foundation/libra#364 - feat(clean): add -d, -x, -X, --exclude flags (merged 2026-05-08)
I keep this profile less like a CV and more like a workbench. The interesting part is not a label; it is the trail of small decisions that make a system less mysterious than it was yesterday.
