DWKIM24 maps the whole of Mike in Korean before changing a line

A 461-line architecture reference, written in Korean and reverse-engineered from the codebase, with no code changes attached.

i18nknowledge-management

DWKIM24's only commit so far isn't a feature - it's homework. The fork adds a single long document that walks the entire system in Korean: how the front end, back end, database, file storage, and AI services fit together, how login and permissions work, and how the three core jobs (chat, document versioning, and tabular review) actually move data from end to end. It reads like an accurate map of Mike as it stands today.

Nobody writes that much detail for a quick deployment tweak. It looks like the groundwork for bringing a Korean-speaking team up to speed, or for scoping a bigger set of changes before making them. The catch: the document is pinned to a mid-May baseline and will drift as Mike moves on.

So what Worth a glance if you track which forks are staffing up to diverge - or if you want a proven skeleton for documenting your own legal-AI stack.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

1 commit from DWKIM24/MIKE-PROJECT, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
c8e0b223 docs: add Korean architecture overview DWKIM24 2026-05-12 ↗ GitHub
Mike 프로젝트 전체 구조, 모듈 간 상호작용, 핵심 워크플로(채팅·문서·표 리뷰),
인증/인가, 환경 변수, 레이트리밋을 한국어로 정리.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-442.md from inside the repo you want the changes in.

⬇ Download capture-thread-442.md