Flashduty Terminology Glossary
Chinese-English terminology mapping. Maintain consistency during translation.Core Concepts
Incident Management
Alert Processing
Schedule & On-call
Severity Levels
Incident Status
Time & Notifications
Subscription & Plans
Account & Team
UI & Labels
Actions
Third-party Integrations
Technical Terms
Regional
API documentation
Used by theapi-review skill when generating api-reference/openapi.{en,zh}.json. Stay consistent with these terms across operation summaries, descriptions, and field labels so the reference reads uniformly.
Operation verbs (summary prefix)
Reference / structural terms
Permission class names
Permission classes come fromfc-pgy/logic/permission/permission_test.go — use the classEn field there as the authoritative English label. Common ones:
When a permission’s
classEn is set in permission_test.go, trust it over any guess. The Flashduty product team manages those labels and keeps them consistent with the console UI.
Notes for the generator
- Prefer frontend labels over translation. If the frontend console uses a specific English label for a concept (e.g., “Notification template” vs “Message template”), use the frontend label. Check
fc-foundation-app/src/Packages/saas/pages/...i18n files as the source of truth for user-facing labels. - Don’t translate product names. “On-call”, “RUM”, “Monitors”, “Flashduty” stay English in both languages.
- Don’t translate wire values. Enum values like
"enabled","InvalidParameter","updated_at"are wire-format identifiers and must appear identically in both EN and ZH specs. Only their descriptions get localized. - Verb tense — English uses imperative (“Create a template”, “Delete an incident”), Chinese uses short noun phrases (“创建模板”, “删除故障”). Don’t prefix Chinese summaries with verbs like “创建一个” when “创建” alone reads naturally.
Do Not Translate (AI SRE domain)
These terms stay in English even inside Chinese copy. Used by thei18n-review
skill in bootstrap mode to decide which substrings of a hardcoded English
string to preserve verbatim when generating Chinese translations.
Style rule: when a DNT term appears mid-sentence in Chinese, surround it with
a single half-width space on either side (e.g., 管理你的 Routines, not
管理你的Routines). For multi-word terms, keep them together verbatim
(e.g., 创建 A2A Agent).
Translatable companions (do NOT belong in DNT — translate to Chinese):
Intentional Variants (per-context wording)
These Chinese terms intentionally map to more than one English wording depending on UI context. Every listed variant is correct — do not “unify” them. Translators: pick the variant whose context matches.
Plural-pair convention (zh-as-key frontends): a count-bearing Chinese key may
have English
_one / _other splits (e.g. “Ran search” / “Ran
searches”). These pairs are intentional — never merge them into one
English value. The zh locale needs only the base key (Chinese has no plural
inflection); do not add _one / _other entries to zh locale files.
Scope note: the “Incident Status” table above (待处理 → triggered, etc.) applies
to the incident console only. RUM dashboards follow Datadog-style triage wording
(For Review / Reviewed / Occurred At) — do not rewrite RUM strings to match that
table.