You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Repo language is inconsistent: every shipped artifact (README, code, commits, CHANGELOG, all PR bodies authored by Sangguen, all release notes) is in English, but 23 GitHub issues authored by the auditor agent (#58–#80) shipped in Korean. This creates a bilingual archive that breaks searchability, accessibility for non-Korean reviewers, and visual parity in the issue list.
This issue formalizes the language policy and tracks retroactive cleanup.
Root cause
A stale instruction in the auditor agent's persistent memory file hackathon_advisory_stance.md (dated 2026-04-22):
Korean communication: respond in Korean unless the user switches languages (CLAUDE.md is in Korean; user communicates in Korean).
This rule was inferred from a single signal — the user typed prompts in Korean — and was over-generalized into "all output, including GitHub issue bodies, in Korean." The agent's memory index MEMORY.md reinforced the rule with the hook line "Korean by default", which is auto-loaded at every session start. As a result, even when the agent observed English-only artifacts (PRs #81–#99, README, commits), the memory rule overrode the visible signal.
There is no repo-level CLAUDE.md or CONTRIBUTING.md clause documenting language policy, so the agent had no project-side guardrail to override the user-scoped memory rule.
Affected artifacts (target scope)
Primary — issue bodies in Korean (23 issues, all CLOSED)
Issue titles are bilingual (English tier label + Korean description); issue bodies are predominantly Korean prose with English file paths and code snippets. None of these are PRs or commit messages, so the git history itself is unaffected.
Secondary — auditor chat reports
Mixed Korean/English progress reports delivered to the user in-session. Not persisted to the repo.
The auditor agent's memory file has been hard-locked to English-only:
hackathon_advisory_stance.md — language rule rewritten as HARD LOCK: every output (chat + every artifact) must be English; Korean prompts are not a switch signal; only an explicit user directive overrides for a single turn.
MEMORY.md — index hook updated so the constraint is visible at every session-start auto-load, preventing regression.
Why-trail in the memory body records all three escalations (original Korean default → English baseline → hard lock) so a future session cannot silently re-introduce the original rule.
Proposed for this repo (subject of this issue)
Add a one-paragraph language policy to CONTRIBUTING.md so the standard is repo-discoverable and not just agent-memory-only. Suggested wording:
Language: All issues, PRs, commits, code, and documentation in this repo are written in English. This keeps the artifact archive uniform and accessible to non-Korean reviewers.
Original tier label and ID prefix (🔴 C-1, 🟡 I-1, 🟢 N-1, 📋, etc.)
Original file paths, line numbers, code snippets, evidence
Acceptance-criteria checkboxes (already English)
Cross-references between issues
Original close timestamps (issue body edits do not alter close metadata)
All 23 issues are CLOSED; no triage or labels need re-evaluation. Edits are body-only and reversible via issue history.
Title cleanup (optional) — current titles are bilingual (e.g., 🔴 C-1: 실제 end-to-end run 증거 부재 — clean-room 검증 필요). Decide whether to rewrite to fully English or leave as-is for archive fidelity. Recommendation: rewrite for searchability since titles are the most-indexed surface.
Will NOT be done
No git history rewrite. Commits, PR bodies, and merged content stay as-shipped.
No relabeling or re-triage of closed issues. Cleanup is text-only.
No edits to N-1..N-5 acceptance criteria during translation — only Korean prose translated.
Acceptance criteria
CONTRIBUTING.md contains a "Language" section stating English-only.
Summary
Repo language is inconsistent: every shipped artifact (README, code, commits, CHANGELOG, all PR bodies authored by Sangguen, all release notes) is in English, but 23 GitHub issues authored by the auditor agent (#58–#80) shipped in Korean. This creates a bilingual archive that breaks searchability, accessibility for non-Korean reviewers, and visual parity in the issue list.
This issue formalizes the language policy and tracks retroactive cleanup.
Root cause
A stale instruction in the auditor agent's persistent memory file
hackathon_advisory_stance.md(dated 2026-04-22):This rule was inferred from a single signal — the user typed prompts in Korean — and was over-generalized into "all output, including GitHub issue bodies, in Korean." The agent's memory index
MEMORY.mdreinforced the rule with the hook line"Korean by default", which is auto-loaded at every session start. As a result, even when the agent observed English-only artifacts (PRs #81–#99, README, commits), the memory rule overrode the visible signal.There is no repo-level
CLAUDE.mdorCONTRIBUTING.mdclause documenting language policy, so the agent had no project-side guardrail to override the user-scoped memory rule.Affected artifacts (target scope)
Primary — issue bodies in Korean (23 issues, all CLOSED)
v1.12-backloglabelIssue titles are bilingual (English tier label + Korean description); issue bodies are predominantly Korean prose with English file paths and code snippets. None of these are PRs or commit messages, so the git history itself is unaffected.
Secondary — auditor chat reports
Mixed Korean/English progress reports delivered to the user in-session. Not persisted to the repo.
Unaffected
Resolution
Already applied (2026-04-25)
The auditor agent's memory file has been hard-locked to English-only:
hackathon_advisory_stance.md— language rule rewritten as HARD LOCK: every output (chat + every artifact) must be English; Korean prompts are not a switch signal; only an explicit user directive overrides for a single turn.MEMORY.md— index hook updated so the constraint is visible at every session-start auto-load, preventing regression.Proposed for this repo (subject of this issue)
Add a one-paragraph language policy to
CONTRIBUTING.mdso the standard is repo-discoverable and not just agent-memory-only. Suggested wording:Retroactive cleanup of issue bodies 🔴 C-1: no end-to-end run evidence — clean-room verification needed #58–📋 v1.11.0 5×3 Review — 22-issue master index (#58~#79) #80 — rewrite each body in English while preserving:
All 23 issues are CLOSED; no triage or labels need re-evaluation. Edits are body-only and reversible via issue history.
Title cleanup (optional) — current titles are bilingual (e.g.,
🔴 C-1: 실제 end-to-end run 증거 부재 — clean-room 검증 필요). Decide whether to rewrite to fully English or leave as-is for archive fidelity. Recommendation: rewrite for searchability since titles are the most-indexed surface.Will NOT be done
Acceptance criteria
CONTRIBUTING.mdcontains a "Language" section stating English-only.hackathon_advisory_stance.mdhard lock remains in place.References
~/.claude/projects/-Users-kimsejun-Documents-GitHub-PreviewForgeForClaudeCode/memory/hackathon_advisory_stance.md~/.claude/projects/-Users-kimsejun-Documents-GitHub-PreviewForgeForClaudeCode/memory/MEMORY.md