tomtan/EverOS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
b243018affb554e401636b0dc8389f263e9f7e77
EverOS/.claude/rules/language-policy.md
Elliot Chen 518b8eca85 chore: initialize EverOS 1.0.0 
md-first memory extraction framework for AI agents.

Markdown is the single source of truth; SQLite holds state and LanceDB
provides the rebuildable vector + BM25 + scalar index. The codebase follows
a single-direction DDD layering (entrypoints -> service -> memory -> infra,
with component / core / config cross-cutting) enforced by import-linter.

Engineering surface:
- Coding conventions in .claude/rules/ (path-scoped) and workflows in
  .claude/skills/ (/commit, /new-branch, /pr).
- GitHub Actions CI runs make lint + test + integration; pre-commit mirrors
  the gates locally (ruff, hygiene hooks, gitlint commit-msg).
- Commit messages follow Conventional Commits, enforced by gitlint.
- make lint also enforces datetime two-zone discipline and OpenAPI drift.
2026-06-06 07:33:17 +08:00

569 B
Raw Blame History

Language policy rule (always loaded)

The project targets a global audience and is English-first.

  • Code, comments, docstrings, docs, commit messages, identifiers: English only.
  • CJK characters are allowed only in:
    • test fixtures under tests/ and data/ (multilingual input is the point), and
    • locale-suffixed mirror files (e.g. *_zh.json).
  • Do not introduce CJK into src/, docs/, or config.

Enforcement: make check-cjk scans for stray CJK outside the allowlist (advisory). Keep user-facing strings and error messages in English.