wdi-method 0.4.5 → 0.5.0

package/kit-overlay/repo-guide.md

@@ -1,97 +1,112 @@
----
-status: Accepted
----
-
-# Repo Guide
-
-**Loaded when:** adding a file that is neither code nor corpus, or unsure whether something may be
-kept in this repo
-
-Every other guide answers *where in the corpus does this go*. This one answers the question that
-comes before it: **does it belong in this repository at all?**
-
-## What this repository is
-
-One product, built for one owner. It holds what is needed to build and run that product, and
-nothing that merely relates to it commercially or organisationally.
-
-| MAY be here | MUST NOT be here |
-|---|---|
-| Application code, configuration, migrations, tests | Proposals, contracts, meeting notes with the client |
-| The corpus — `.constitution/` `.control/` `.what/` `.how/` | Contract values, pricing strategy, margins, rate cards |
-| Technical documentation, ADR, diagrams | Real customer data, production credentials, tokens |
-| Synthetic seed data | Anything whose leak would harm a bargaining position |
-| Built deliverables | An archive of commercial documents |
-
-The test is not "is it secret". It is **what changes when this file changes** — a commitment, or how
-the thing is built. Only the second belongs here.
-
-## Two failure modes, and why the second is worse
-
-The obvious one is a credential in a commit. It is loud, it is caught, and it has a known remedy.
-
-The quiet one is a **commercial fact restated as a technical one** — a limit that exists because of
-what was negotiated, written into an ADR as though it were an engineering constraint. It survives
-every scan, it is never noticed as a leak, and it teaches the next reader that the boundary is
-soft.
-
-When a technical decision genuinely follows from a commercial one, the ADR MUST state the technical
-fact and MUST NOT state the commercial one. *"Retention is 90 days"* is a technical fact.
-*"Retention is 90 days because the client would not pay for more"* is a commercial one wearing a
-technical coat.
-
-## `.work/` — scratch that is committed
-
-`.work/` holds work in progress that has no home yet: notes while reading an unfamiliar system,
-drafts, exploratory output, a working paper for a change spanning several sessions.
-
-It is **committed**, so that a session picked up on another machine finds it, and so a reviewer can
-see what a change was actually reasoning about.
-
-It is **ephemeral**, and the two together are what make its rules matter:
-
-- Any durable outcome MUST be moved out before the task closes — to the corpus if it is truth, to
-  `_bmad-output/` if it is a run's byproduct.
-- Obsolete scratch MUST be deleted when its task closes. `.work/` that only grows stops being
-  scratch and becomes a second, unindexed corpus that nobody trusts and nobody deletes.
-- Secrets and commercial figures MUST NOT be written here. Being scratch is not an exemption; it is
-  the reason people assume it is one.
-- Nothing MUST be read from `.work/` as authority. If something there is right, it belongs
-  somewhere with an owner.
-
-`.work/` MUST NOT be confused with `_bmad-output/`. That folder holds the output of skill runs, is
-never curated, and is cited by path. `.work/` holds what a human or agent wrote by hand while
-working, and is meant to empty out.
-
-## Referring to things outside this repository
-
-Engagement context — who the client is, what was agreed, what is due — lives elsewhere. This repo
-MUST work without it. An agent MUST be able to act on the rules stated here without opening any
-other repository.
-
-When an artifact genuinely needs external context:
-
-- MUST state the technical fact locally, in full.
-- MAY name the external source by **repository and path**, as provenance.
-- MUST NOT paste the external content in, and MUST NOT replace a technical statement with a pointer
-  to a commercial document.
-
-A pointer where a specification should be is the failure this rule exists to stop: the reader who
-cannot open that path is left with nothing, and the reader who can is reading the wrong kind of
-document.
-
-## How the method arrives
-
-Method files in `.constitution/` (except this product's Articles 1, 2, and 5, `codebase/*-guide.md`
-once `Accepted`, and any extra file this repo added), the `wdi-*` skills, and `_bmad/custom/*.toml`
-arrive from the public WDI Method package via `npx wdi-method install` / `update`.
-
-At **read time** this repo is self-contained: every file the rules need is here, readable with the
-repo alone. At **change time** the method has one published writer — the WDI Method package. Two
-rules follow:
-
-- A method file MUST NOT be invented or patched here to improve the method. If a rule is wrong, it
-  is fixed in the WDI Method package, then brought here with `update`.
-- A rule particular to this repo MUST be written out in full, and MUST NOT be replaced by a pointer
-  into another repository.
-
+---
+status: Accepted
+---
+
+# Repo Guide
+
+**Loaded when:** adding a file that is neither code nor corpus, or unsure whether something may be
+kept in this repo
+
+Every other guide answers *where in the corpus does this go*. This one answers the question that
+comes before it: **does it belong in this repository at all?**
+
+## What this repository is
+
+One product, built for one owner. It holds what is needed to build and run that product, and
+nothing that merely relates to it commercially or organisationally.
+
+| MAY be here | MUST NOT be here |
+|---|---|
+| Application code, configuration, migrations, tests | Proposals, contracts, meeting notes with the client |
+| The corpus — `.constitution/` `.control/` `.what/` `.how/` | Contract values, pricing strategy, margins, rate cards |
+| Technical documentation, ADR, diagrams | Real customer data, production credentials, tokens |
+| Synthetic seed data | Anything whose leak would harm a bargaining position |
+| Built deliverables | An archive of commercial documents |
+
+The test is not "is it secret". It is **what changes when this file changes** — a commitment, or how
+the thing is built. Only the second belongs here.
+
+## Two failure modes, and why the second is worse
+
+The obvious one is a credential in a commit. It is loud, it is caught, and it has a known remedy.
+
+The quiet one is a **commercial fact restated as a technical one** — a limit that exists because of
+what was negotiated, written into an ADR as though it were an engineering constraint. It survives
+every scan, it is never noticed as a leak, and it teaches the next reader that the boundary is
+soft.
+
+When a technical decision genuinely follows from a commercial one, the ADR MUST state the technical
+fact and MUST NOT state the commercial one. *"Retention is 90 days"* is a technical fact.
+*"Retention is 90 days because the client would not pay for more"* is a commercial one wearing a
+technical coat.
+
+## `.work/` — scratch that is committed
+
+`.work/` holds work in progress that has no home yet: notes while reading an unfamiliar system,
+drafts, exploratory output, a working paper for a change spanning several sessions.
+
+It is **committed**, so that a session picked up on another machine finds it, and so a reviewer can
+see what a change was actually reasoning about.
+
+It is **ephemeral**, and the two together are what make its rules matter:
+
+- Any durable outcome MUST be moved out before the task closes — to the corpus if it is truth, to
+  `_bmad-output/` if it is a run's byproduct.
+- Obsolete scratch MUST be deleted when its task closes. `.work/` that only grows stops being
+  scratch and becomes a second, unindexed corpus that nobody trusts and nobody deletes.
+- Secrets and commercial figures MUST NOT be written here. Being scratch is not an exemption; it is
+  the reason people assume it is one.
+- Nothing MUST be read from `.work/` as authority. If something there is right, it belongs
+  somewhere with an owner.
+
+`.work/` MUST NOT be confused with `_bmad-output/`. That folder holds the output of skill runs, is
+never curated, and is cited by path. `.work/` holds what a human or agent wrote by hand while
+working, and is meant to empty out.
+
+## Referring to things outside this repository
+
+Engagement context — who the client is, what was agreed, what is due — lives elsewhere. This repo
+MUST work without it. An agent MUST be able to act on the rules stated here without opening any
+other repository.
+
+When an artifact genuinely needs external context:
+
+- MUST state the technical fact locally, in full.
+- MAY name the external source by **repository and path**, as provenance.
+- MUST NOT paste the external content in, and MUST NOT replace a technical statement with a pointer
+  to a commercial document.
+
+A pointer where a specification should be is the failure this rule exists to stop: the reader who
+cannot open that path is left with nothing, and the reader who can is reading the wrong kind of
+document.
+
+## How the method arrives
+
+Method files in `.constitution/`, the `wdi-*` skills, and `_bmad/custom/*.toml` arrive from the
+public WDI Method package via `npx wdi-method install` / `update`.
+
+`.constitution/` holds **exactly two folders**, and which one a file is in decides who owns it:
+
+| Folder | Owner | On `update` | On `promote` |
+|---|---|---|---|
+| `method/` | the method | **overwritten** in full | carried into the package |
+| `project/` | this product | **never touched** — seeded once when absent | **never carried**, so a product's rules cannot be published |
+
+Everything in the room is yours: `project/constitution.md` (Articles 1, 2, 5),
+`project/codebase-*-guide.md` (stack, conventions, brownfield — protected at **any** `status:`,
+including `Draft`, which is when they are actually written), and any rule file you add.
+
+The seam is the **folder**, never a marked region inside a generic file. `AGENTS.md` uses a marked
+block because it is one file with no alternative; `.constitution/` has fifty-odd, and blocks inside
+them would make every update perform surgery in every file. Prose has no merge algebra — only a path
+can say, unambiguously, whose a file is.
+
+At **read time** this repo is self-contained: every file the rules need is here, readable with the
+repo alone. At **change time** the method has one published writer — the WDI Method package. Two
+rules follow:
+
+- A method file MUST NOT be invented or patched here to improve the method. If a rule is wrong, it
+  is fixed in the WDI Method package, then brought here with `update`.
+- A rule particular to this repo MUST be written out in full, and MUST NOT be replaced by a pointer
+  into another repository.
+

package/package.json

@@ -1,37 +1,37 @@
-{
-  "name": "wdi-method",
-  "version": "0.4.5",
-  "description": "WDI Method — software delivery method that wraps BMad",
-  "type": "module",
-  "bin": {
-    "wdi-method": "bin/wdi-method.js"
-  },
-  "files": [
-    "bin/",
-    "lib/",
-    "kit/",
-    "kit-overlay/",
-    "scaffold/",
-    "README.md",
-    "LICENSE"
-  ],
-  "engines": {
-    "node": ">=20"
-  },
-  "scripts": {
-    "test": "node --test tests/*.test.mjs",
-    "prepublishOnly": "node --test tests/*.test.mjs"
-  },
-  "dependencies": {
-    "@clack/prompts": "^0.11.0"
-  },
-  "license": "MIT",
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/wiradigitalid/wdi-method.git"
-  },
-  "bugs": {
-    "url": "https://github.com/wiradigitalid/wdi-method/issues"
-  },
-  "homepage": "https://github.com/wiradigitalid/wdi-method#readme"
-}
+{
+  "name": "wdi-method",
+  "version": "0.5.0",
+  "description": "WDI Method — software delivery method that wraps BMad",
+  "type": "module",
+  "bin": {
+    "wdi-method": "bin/wdi-method.js"
+  },
+  "files": [
+    "bin/",
+    "lib/",
+    "kit/",
+    "kit-overlay/",
+    "scaffold/",
+    "README.md",
+    "LICENSE"
+  ],
+  "engines": {
+    "node": ">=20"
+  },
+  "scripts": {
+    "test": "node --test tests/*.test.mjs",
+    "prepublishOnly": "node --test tests/*.test.mjs"
+  },
+  "dependencies": {
+    "@clack/prompts": "^0.11.0"
+  },
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/wiradigitalid/wdi-method.git"
+  },
+  "bugs": {
+    "url": "https://github.com/wiradigitalid/wdi-method/issues"
+  },
+  "homepage": "https://github.com/wiradigitalid/wdi-method#readme"
+}

package/scaffold/.control/product-glossary.md

@@ -1,21 +1,21 @@
-# Product Glossary
-
-**Dimuat saat:** menulis dokumen apa pun di korpus.
-
-SSOT kosakata **produk** — apa yang produk ini bicarakan. Tiap istilah didefinisikan **sekali** di
-sini, lalu dipakai apa adanya di seluruh korpus.
-
-Kosakata **metode** tinggal di `.constitution/method-glossary.md` dan MUST NOT didefinisikan ulang di
-sini. Tes pemisahnya: apakah istilah ini tetap berlaku kalau dipakai di produk lain? Ya →
-`method-glossary.md`, tidak → sini.
-
-## Aturan
-
-- Istilah baru yang muncul di dokumen mana pun MUST ditambahkan ke sini **dalam lintasan yang sama**.
-- Definisi MUST menyebut hubungan ke istilah lain dan kardinalitasnya bila relevan.
-- Satu istilah MUST NOT punya dua entri.
-- Berkas ini lahir **kosong** dan diisi dari produknya. Entri pertamanya lahir bersama brief di G1.
-
-## Entri
-
-<!-- Urut abjad. Format: **Istilah** — definisi. Hubungan. Kardinalitas bila relevan. -->
+# Product Glossary
+
+**Loaded when:** writing any document in the corpus.
+
+The SSOT for **product** vocabulary — what this product talks about. Every term is defined **once**
+here, then used as-is across the corpus.
+
+**Method** vocabulary lives in `.constitution/method-glossary.md` and MUST NOT be redefined here. The
+split test: does this term still hold if used in another product? Yes → `method-glossary.md`, no →
+here.
+
+## Rules
+
+- A new term appearing in any document MUST be added here **in the same pass**.
+- A definition MUST name its relationship to other terms and its cardinality where relevant.
+- One term MUST NOT have two entries.
+- This file is born **empty** and filled from the product. Its first entries are born with the brief at G1.
+
+## Entries
+
+<!-- Alphabetical. Format: **Term** — definition. Relationship. Cardinality where relevant. -->

package/scaffold/.control/project-non-technical-log.md

@@ -1,23 +1,23 @@
-# Project Non-Technical Log
-
-**Dimuat saat:** sebuah fakta non-teknis yang membatasi pembangunan produk ini berubah, atau saat
-mencari tahu apa yang sudah berlaku di luar kode.
-
-Ditulis lewat skill `wdi-log` intent `fact`, tidak pernah dengan tangan langsung.
-
-Tes satu kalimat: **kalau angkanya dihapus dan faktanya masih berguna bagi yang membangun, ia boleh
-di sini.**
-
-Kategori: `domain` · `akun` · `legal` · `jadwal` · `organisasi`.
-
-## Berlaku
-
-| id | Tanggal | Kategori | Fakta | Akibat | Sumber |
-|---|---|---|---|---|---|
-| — | — | — | — | — | — |
-
-## Tidak Berlaku Lagi
-
-| id | Fakta | Berhenti berlaku | Digantikan |
-|---|---|---|---|
-| — | — | — | — |
+# Project Non-Technical Log
+
+**Loaded when:** a non-technical fact that constrains this product's build changes, or when finding
+out what already holds outside the code.
+
+Written through the `wdi-log` skill's `fact` intent, never by hand directly.
+
+One-sentence test: **if the number were deleted and the fact would still be useful to whoever is
+building, it belongs here.**
+
+Categories: `domain` · `account` · `legal` · `schedule` · `organisation`.
+
+## In force
+
+| id | Date | Category | Fact | Effect | Source |
+|---|---|---|---|---|---|
+| — | — | — | — | — | — |
+
+## No longer in force
+
+| id | Fact | Stopped holding | Superseded by |
+|---|---|---|---|
+| — | — | — | — |

package/scaffold/.control/questions/answered.md

@@ -1,11 +1,11 @@
-# Terjawab
-
-**Dimuat saat:** mencari keputusan yang sudah diambil lewat pertanyaan, bukan lewat `DEC-`.
-
-Baris pindah ke sini dari ketiga daftar lain. MUST NOT dihapus.
-
-## Terjawab
-
-| id | Pertanyaan | Jawaban | Ditutup |
-|---|---|---|---|
-| — | — | — | — |
+# Answered
+
+**Loaded when:** looking for a decision that was reached through a question, not through a `DEC-`.
+
+Rows move here from the other three lists. MUST NOT be deleted.
+
+## Answered
+
+| id | Question | Answer | Closed |
+|---|---|---|---|
+| — | — | — | — |

package/scaffold/.control/questions/assumptions.md

@@ -1,15 +1,15 @@
-# Asumsi
-
-**Dimuat saat:** disapu sekali per gate; boleh dilewati.
-
-Kelas **default** sebuah pertanyaan. Agent mengambil jawabannya sendiri lalu mencatatnya di sini, satu
-baris: asumsinya, plus akibat kalau ia salah. Berkas ini **tidak menahan apa pun**.
-
-Sebuah baris di sini MUST naik ke `blocking.md` begitu ia lulus salah satu dari tiga tes yang berkas
-itu nyatakan.
-
-## Terbuka
-
-| id | Asumsi | Akibat kalau salah | Diambil | Oleh |
-|---|---|---|---|---|
-| — | — | — | — | — |
+# Assumptions
+
+**Loaded when:** swept once per gate; MAY be skipped.
+
+The **default** class for a question. The agent takes the answer itself and records it here, one
+row: the assumption, plus the cost if it turns out wrong. This file **holds nothing**.
+
+A row here MUST move up to `blocking.md` the moment it passes one of the three tests that file
+states.
+
+## Open
+
+| id | Assumption | Cost if wrong | Taken | By |
+|---|---|---|---|---|
+| — | — | — | — | — |

package/scaffold/.control/questions/blocking.md

@@ -1,21 +1,21 @@
-# Pertanyaan yang Memblokir
-
-**Dimuat saat:** setiap gate.
-
-Hanya berkas ini yang menahan sebuah gate. Ditulis lewat `wdi-question`, tidak pernah dengan tangan
-langsung; bentuk barisnya di `.constitution/document/templates/questions.md`.
-
-Sasarannya **≤3 baris per Product Component**. Sebuah pertanyaan naik ke sini hanya lewat tiga tes,
-salah satu cukup:
-
-1. Menyentuh uang, data pribadi, atau kewajiban legal.
-2. Mengubah bunyi janji sebuah `FR`.
-3. Salah menjawab memaksa tulis ulang lebih dari satu komponen.
-
-Gagal ketiganya → `assumptions.md`. Sebuah pertanyaan MUST NOT didaftarkan di sini "untuk aman".
-
-## Terbuka
-
-| id | Pertanyaan | Memblokir | Owner | Sebelum |
-|---|---|---|---|---|
-| — | — | — | — | — |
+# Blocking Questions
+
+**Loaded when:** every gate.
+
+Only this file holds a gate. Written through `wdi-question`, never by hand directly; the row shape
+lives in `.constitution/document/templates/questions.md`.
+
+Target **<=3 rows per Product Component**. A question rises to here only through three tests, one is
+enough:
+
+1. It touches money, personal data, or a legal obligation.
+2. It changes the wording of an `FR`'s promise.
+3. Answering it wrong forces a rewrite of more than one component.
+
+Failing all three → `assumptions.md`. A question MUST NOT be filed here "to be safe".
+
+## Open
+
+| id | Question | Blocks | Owner | Before |
+|---|---|---|---|---|
+| — | — | — | — | — |

package/scaffold/.control/questions/external.md

@@ -1,11 +1,11 @@
-# Menunggu Pihak Luar
-
-**Dimuat saat:** ada jawaban yang hanya bisa datang dari luar sesi ini.
-
-Berkas ini **tidak menahan gate** kecuali barisnya juga ditunjuk dari `blocking.md`.
-
-## Terbuka
-
-| id | Pertanyaan | Menunggu | Sejak |
-|---|---|---|---|
-| — | — | — | — |
+# Waiting on an Outside Party
+
+**Loaded when:** an answer can only come from outside this session.
+
+This file **does not hold a gate** unless its row is also pointed to from `blocking.md`.
+
+## Open
+
+| id | Question | Waiting on | Since |
+|---|---|---|---|
+| — | — | — | — |

package/scaffold/.control/registry/components.yaml

@@ -1,21 +1,21 @@
-# components.yaml — SSOT untuk Product Component, container, dan Logical Component
-#
-# Tiga hal berbeda, dua di antaranya berbagi kata "component":
-#   Product Component (PC) — irisan DOMAIN, permukaan yang bisa disebut pengguna
-#   Container              — unit yang berjalan atau dideploy sendiri; C4 L2 memilikinya
-#   Logical Component (LC) — satu unit build yang bisa ditunjuk
-#
-# `mode` — KEDALAMAN DOKUMEN. Ditulis HANYA pada komponen yang memang perlu beda dari global.
-# `risk_accepted` — INTENSITAS REVIEW, bukan kedalaman. low · medium · high
-# `owns` — entitas domain yang komponen ini BERWENANG MENULIS.
-# `g4_passed` — hanya berarti pada komponen ber-mode di atas catalog.
-#
-# Komponen lahir lewat wdi-init intent `component` di ekor G2. Berkas ini lahir kosong.
-
-product_components: []
-
-platform_owns: []
-
-containers: []
-
-logical_components: []
+# components.yaml — SSOT for Product Components, containers, and Logical Components
+#
+# Three different things, two of which share the word "component":
+#   Product Component (PC) — a DOMAIN slice, a surface a user could name
+#   Container              — a unit that runs or deploys on its own; owned by C4 L2
+#   Logical Component (LC) — one nameable build unit
+#
+# `mode` — DOCUMENT DEPTH. Written ONLY on a component that genuinely needs to differ from global.
+# `risk_accepted` — REVIEW INTENSITY, not depth. low · medium · high
+# `owns` — the domain entities this component is AUTHORISED TO WRITE.
+# `g4_passed` — only means something on a component at a mode above catalog.
+#
+# A component is born through wdi-init intent `component` at the tail of G2. This file is born empty.
+
+product_components: []
+
+platform_owns: []
+
+containers: []
+
+logical_components: []

package/scaffold/.control/registry/defects.yaml

@@ -1,3 +1,3 @@
-# defects.yaml — SSOT untuk cacat: bug biasa dan hotfix.
-
-defects: []
+# defects.yaml — SSOT for defects: ordinary bugs and hotfixes.
+
+defects: []