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
[docs](i18n): interim Indonesian review of factor & option content
Acting as interim Translator (charter Section 14.2; no professional translator
appointed yet), reviewed the bilingual content for accuracy and terminology
consistency. Findings: the Indonesian reads naturally and uses "konsistensi /
konsistensi eventual" and the QA vocabulary consistently; the only defect was
one stray English token.
- Fixed: microservices "When to use" ID — "observability" -> "observabilitas".
- Added an "Indonesian terminology" note to the Option Content Sheet: QA names
follow the Model Data Sheet Section 2.1 vocabulary, and the kept architecture
loanwords (monolith, microservices, event-driven, deploy/rilis, throughput,
eventual, schema, cache, saga, outbox) are listed so usage stays consistent.
- Status refreshed: Option Content Sheet v0.2, Model Data Sheet v0.9, factor
content Section 2.1 — "interim ID-reviewed; professional Translator review
still welcome". No numeric change; both guards pass.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
| 0.6 | 2026-06-13 | Calibration-stability review: widened the e-commerce and IoT D4 targets to Hexagonal / Clean (exact tie whenever the interoperability weight is 0); target margins are now measured by the verification script, with the four sensitive targets documented in the [Scoring Algorithm Specification](scoring-algorithm.md) Section 9.4 |
26
26
| 0.7 | 2026-06-13 | Factor-content consistency (Section 2.1): made the Indonesian QA names uniform across all help texts (no more mixed EN/ID tokens) and established the baseline ID QA vocabulary; fixed two English level labels so they are truly verbatim from Build Spec Section 4 (lifespan "prototype", dataVolume "big data") |
27
27
| 0.8 | 2026-06-13 | Interim ratification: D4/D5 `qaFit` ([ADR-0001](../adr/0001-ratify-d4-d5-qafit.md)) and preset calibration ([ADR-0002](../adr/0002-ratify-preset-calibration.md)) accepted as v1.0 defaults by the Owner (interim Domain-Advisor role, charter D12); values remain editable, pending independent review and the v3.0 empirical study |
28
+
| 0.9 | 2026-06-13 | Interim Indonesian review of the factor content (Section 2.1): terminology confirmed against the baseline ID QA vocabulary; status updated (professional Translator review still welcome) |
28
29
29
30
---
30
31
@@ -105,8 +106,8 @@ used by the preset table in Section 6.
105
106
106
107
The user-facing copy for all 14 factors, in both product languages. Each help text states *what
107
108
the factor means* and *why it shifts the priorities* (Build Spec Section 4). English is the
108
-
authoring language; the Indonesian copy follows the product's plain-language register and awaits
109
-
Translator review (Charter Section 14.2).
109
+
authoring language; the Indonesian copy follows the product's plain-language register; it has had an **interim ID
110
+
review** (2026-06-13) and a professional Translator review is still welcome (Charter Section 14.2).
110
111
111
112
|`id`| Label & levels (EN · *ID*) | Help (EN) | Help (ID) |
|`devops`| DevOps / platform maturity · *Kematangan DevOps / platform*<br>0 Low · *Rendah*<br>1 Medium · *Sedang*<br>2 Mature (CI/CD, monitoring) · *Matang (CI/CD, pemantauan)*| How strong the team's automation and operations are. Mature platforms can safely run more independently deployed parts (deployability, observability). | Seberapa kuat otomasi dan operasional tim. Platform yang matang dapat menjalankan lebih banyak bagian yang dirilis mandiri secara aman (kemudahan rilis, observabilitas). |
127
128
128
129
> English level labels are verbatim from Build Spec Section 4 (🔒); the Indonesian labels and both
129
-
> help texts are 🧪 baseline copy pending Translator review. At build time this table maps 1:1 to
130
+
> help texts are 🧪 baseline copy, interim ID-reviewed (professional Translator review welcome). At build time this table maps 1:1 to
130
131
> `config/factors.ts` (`label`, `levels[0..2]`, `help` — each `{ en, id }`). The Indonesian
131
132
> quality-attribute names used in the help (skalabilitas, performa, ketersediaan, keamanan,
| 0.1 | 2026-06-13 | Authored the full bilingual educational metadata for all 21 options (definition, pros/cons, when to use/avoid, real-world pattern, common mistakes, risks + mitigations, learn-more links), the 7 anti-pattern messages, and the 12 fitness-function templates |
21
+
| 0.2 | 2026-06-13 | Interim Indonesian review (Owner/assistant): fixed one stray English token (observability → observabilitas), confirmed QA terminology matches the Model Data Sheet Section 2.1 vocabulary, and documented the loanword policy; professional Translator review still welcome |
21
22
22
23
---
23
24
@@ -34,6 +35,14 @@ this sheet carries only words. Lists use `·` separators; each maps to one array
34
35
both languages — hence the `—` in its ID column). Risks are written `(likelihood/impact) risk →
35
36
mitigation`.
36
37
38
+
**Indonesian terminology.** Quality-attribute names follow the baseline vocabulary in
39
+
[Model Data Sheet Section 2.1](model-data-sheet.md) (skalabilitas, performa, ketersediaan, keamanan,
interoperabilitas, efisiensi biaya, waktu rilis). Established architecture loanwords are kept in
42
+
English by design (monolith, microservices, serverless, event-driven, CQRS, event sourcing,
43
+
deploy/rilis, schema, cache, throughput, eventual, saga, outbox), consistent with Indonesian
44
+
software-writing practice.
45
+
37
46
---
38
47
39
48
## 1. D1 — Deployment Granularity
@@ -87,7 +96,7 @@ mitigation`.
87
96
| Definition | Many small, independently deployable services, each owning its own data, communicating over the network. Optimizes team autonomy, release independence, and scaling — at a high operational price. | Banyak layanan kecil yang dirilis secara independen, masing-masing memiliki datanya sendiri, dan berkomunikasi lewat jaringan. Mengoptimalkan otonomi tim, kebebasan rilis, dan skala — dengan harga operasional yang tinggi. |
88
97
| Pros | Independent deploys and scaling per service · clear team ownership · fault isolation between services | Rilis dan skala independen per layanan · kepemilikan tim yang jelas · isolasi kegagalan antarlayanan |
89
98
| Cons | Distributed-system complexity: latency, partial failure · eventual consistency between services · a much heavier platform and operations bill | Kompleksitas sistem terdistribusi: latensi, kegagalan parsial · konsistensi eventual antarlayanan · beban platform dan operasional yang jauh lebih berat |
90
-
| When to use | Many teams shipping in parallel · high or spiky scale · mature CI/CD and observability | Banyak tim rilis paralel · skala tinggi atau melonjak · CI/CD dan observability yang matang |
99
+
| When to use | Many teams shipping in parallel · high or spiky scale · mature CI/CD and observability | Banyak tim rilis paralel · skala tinggi atau melonjak · CI/CD dan observabilitas yang matang |
91
100
| When to avoid | A small team or low DevOps maturity · strong cross-entity consistency requirements · MVPs | Tim kecil atau kematangan DevOps rendah · kebutuhan konsistensi kuat lintas entitas · MVP |
92
101
| Real-world pattern | Large consumer platforms with dozens of independent teams. | Platform konsumen besar dengan puluhan tim independen. |
93
102
| Common mistakes | Splitting by nouns instead of bounded contexts · sharing one database (a distributed monolith) · long synchronous call chains · skipping the platform investment | Memecah berdasarkan kata benda alih-alih bounded context · berbagi satu database (distributed monolith) · rantai panggilan sinkron yang panjang · melewatkan investasi platform |
0 commit comments