# Content Analysis — SyncBridge Partner Integration API Specification

## Domain
Enterprise SaaS data synchronization platform. Technical API reference documentation for integration partners.

## Source Language
English (written by Taiwan-based team in formal technical English)

## Target Language
Simplified Chinese (zh-CN) for mainland China engineering audience

## Tone & Register
- **Formal technical documentation**: prescriptive, authoritative, structured
- **Audience**: Backend engineers and integration architects
- **Voice**: Third-person imperative ("Partners must implement...", "All endpoints enforce...")
- Consistent use of RFC-style requirement levels ("must", "should", "may")

## Content Structure
1. Overview & versioning (sections 1)
2. Authentication/authorization (section 2)
3. Core data endpoints with JSON examples (section 3)
4. Event system / webhooks (section 4)
5. Rate limiting (section 5)
6. Error handling (section 6)
7. Monitoring & observability (section 7)
8. Data format specs (section 8)
9. Testing & sandbox (section 9)
10. Deployment & go-live (section 10)
11. Security requirements (section 11)
12. Appendices: changelog & glossary

## Key Terminology Decisions

### Keep in English (no translation)
- Product names: SyncBridge, OAuth, JWT, HMAC-SHA256, Prometheus, Redis
- Protocols/standards: REST, HTTP, TLS, SSL, mTLS, HSTS, E.164, ISO 8601
- Technical identifiers: JSON, UUID, API, SDK, SLA, RBAC, WAF, DDoS, PII, GDPR, CCPA
- Code elements: all code blocks, JSON payloads, HTTP methods (GET/POST/PUT/PATCH), headers (X-SyncBridge-*), error codes (RATE_LIMITED, VALIDATION_FAILED, etc.), URL paths, query parameter names
- Metric names: syncbridge_entities_received_total, etc.

### Translate with annotation (first occurrence)
- Dead-Letter Queue → 死信队列（Dead-Letter Queue）
- Shadow Mode → 影子模式（Shadow Mode）
- Schema Registry → Schema 注册中心
- Optimistic Concurrency Control → 乐观并发控制
- PII → PII（个人身份信息）

### Translate consistently (all occurrences)
- Entity → 实体
- Batch → 批次
- Endpoint → 端点
- Webhook → Webhook (keep English)
- Token → 令牌
- Credential → 凭证
- Payload → 载荷
- Pagination → 分页
- Cursor → 游标
- Idempotency Key → 幂等键
- Rate Limiting → 速率限制
- Field Mapping → 字段映射
- Grace Period → 宽限期
- Upstream/Downstream → 上游/下游
- Push/Pull → 推送/拉取
- Partner → 合作伙伴
- Onboarding → 接入

## Translation Challenges

1. **RFC-style modals**: "must", "should", "may" need consistent mapping → 必须、应该/建议、可以
2. **Mixed prose/code**: Sections interleave explanatory text with code blocks and JSON — must preserve all code verbatim while translating surrounding prose
3. **Table-heavy content**: Multiple tables with technical terms in cells — translate description columns, keep identifier/code columns in English
4. **Checklist format**: Section 10.1 uses markdown checkbox syntax `- [ ]` — preserve formatting
5. **Consistent cross-references**: Terms like "entity", "batch", "cursor" appear hundreds of times — must be 100% consistent
6. **Parenthetical explanations**: Source uses patterns like "SyncBridge → Partner" — keep arrow notation
7. **Python code block**: Section 4.1.3 has a Python snippet — keep entirely in English
8. **Version/date references**: Keep all version numbers and dates as-is