wdi-method 0.4.5 → 0.5.0

package/kit/.constitution/{document → method/document}/sdd-guide.md

@@ -88,7 +88,7 @@ Flows **into and out of** each boundary MUST be stated, not just the boundary. A
 direction of call is a name, not a design.
 
 Flow diagrams in `06-flows/` are written only for a flow touching money, irreversible state, or a third
-party. The lane order is the project's to fix, once, in `codebase/conventions-guide.md`. **The `No-op` lane
+party. The lane order is the project's to fix, once, in `../../project/codebase-conventions-guide.md`. **The `No-op` lane
 rule is repealed** — it was a heavy convention for a folder that had never carried a file, and it belongs to
 how a diagram is drawn rather than to what binds.
 

package/kit/.constitution/{document → method/document}/templates/cross-cutting.md

@@ -53,17 +53,17 @@ updated: '{YYYY-MM-DD}'
      one component depends on it. corpus-guide.md owns that test, and it refuses the one use people
      reach for: "the owner is hard to decide".
 
-     `Jenis` is data · endpoint · job · screen, and the list is open. What is not open is the test.
+     `Kind` is data · endpoint · job · screen, and the list is open. What is not open is the test.
 
      `_platform` has no `FR`, so there is no owner-FR for another component to point at. What replaces
      "one writer" is ONE DOCUMENTED SHAPE — stated here, once. A component that wants it different is
      proposing a change to this file, not making a local choice. -->
 
-| Apa | Jenis | Kenapa tidak ada komponen yang menjelaskannya | Siapa yang menyentuhnya | Bentuk yang setiap penyentuh patuhi |
+| What | Kind | Why no component explains it | Who touches it | The shape every toucher obeys |
 | --- | --- | --- | --- | --- |
 
-<!-- `Siapa yang menyentuhnya` menyebut komponen, dan menyebut lebih dari satu adalah keadaan NORMAL —
-     itu separuh alasan barisnya ada di sini. Satu penyentuh adalah sinyal ia milik komponen itu. -->
+<!-- `Who touches it` names components, and naming more than one is a NORMAL state — that is half the
+     reason the row is here. A single toucher is a signal it belongs to that component instead. -->
 
 ## Other product-level agreements
 
@@ -72,7 +72,7 @@ updated: '{YYYY-MM-DD}'
      idempotency key convention · logging fields · rate-limit response shape.
 
      Each MUST state where it is enforced. An agreement nothing enforces is a preference, and
-     preferences belong in codebase/conventions-guide.md where nothing has to justify itself. -->
+     preferences belong in ../../../project/codebase-conventions-guide.md where nothing has to justify itself. -->
 
 ### {agreement}
 

package/kit/.constitution/{document → method/document}/templates/design-system.md

@@ -1,67 +1,67 @@
----
-type: design-system
-scope: _platform
-status: draft            # draft · reviewed · locked · superseded
-created: '{YYYY-MM-DD}'
-updated: '{YYYY-MM-DD}'
----
-
-# Design System — {product}
-
-<!-- TEMPLATE GUIDE — act on these comments, then delete them.
-
-     Home: .how/_platform/design-system.md. Written by wdi-ux, and it is the ONE file in _platform/
-     that wdi-blueprint does not own. Optional, like the rest of UX: it exists when the interface is
-     a substantial part of what the PRD promises.
-
-     WHY IT IS NOT IN A COMPONENT: tokens and base elements cross Product Components by definition. A
-     colour scale living in one component's 01-ux/ is a colour scale the other six will each redefine.
-
-     WHY ux.md DOES NOT SERVE IT: ux.md is the shape of DESIGN.md and EXPERIENCE.md, which are per
-     component. This is the third file, at product level, and it had no template at all.
-
-     THE CODE IS THE SSOT FOR VALUES. Where this repo's web side states a token in tokens.css, this
-     file MUST reference it rather than repeat the value. Two homes for one hex code is two hex codes
-     within a month. Read web/README.md before writing anything here — it is the authority for the
-     web side, and it MUST NOT be contradicted from this file.
-
-     Token and element NAMES are English: they are machine-facing keys, per language-guide.md. -->
-
-## Where the values actually live
-
-<!-- One line per source of truth — the stylesheet, the config, the generated file — with its path.
-     This section is what stops the rest of the document becoming a stale copy. -->
-
-## Tokens
-
-<!-- One table per scale. Name, what it is for, and where it resolves. NOT the raw value, unless this
-     file is genuinely the only place it exists. -->
-
-| Token | For | Resolves in |
-| --- | --- | --- |
-
-## Base elements
-
-<!-- The LC type `ui-element`, registered in components.yaml. One row each: what it is, its states,
-     and where its implementation lives. A composite reused across screens is `ui-composite` and
-     belongs in .how/<pc>/01-ux/, not here. -->
-
-| Element | States it MUST support | Implementation |
-| --- | --- | --- |
-
-<!-- Every element MUST state its empty, loading, error, and disabled states where they apply. The
-     populated state is the one that always gets designed; the others are the ones that ship broken. -->
-
-## Rules that bind every screen
-
-<!-- Only what a screen cannot legitimately override. Each MUST state what it prevents — a rule with
-     no failure behind it is a preference, and preferences go to codebase/conventions-guide.md.
-
-     A rule here that also holds for non-UI code is an AD-N and belongs in the spine instead. -->
-
-| Rule | Prevents |
-| --- | --- |
-
-## What this system deliberately does not cover
-
-<!-- Where a component is free to choose for itself. Absent, every local choice reads as a violation. -->
+---
+type: design-system
+scope: _platform
+status: draft            # draft · reviewed · locked · superseded
+created: '{YYYY-MM-DD}'
+updated: '{YYYY-MM-DD}'
+---
+
+# Design System — {product}
+
+<!-- TEMPLATE GUIDE — act on these comments, then delete them.
+
+     Home: .how/_platform/design-system.md. Written by wdi-ux, and it is the ONE file in _platform/
+     that wdi-blueprint does not own. Optional, like the rest of UX: it exists when the interface is
+     a substantial part of what the PRD promises.
+
+     WHY IT IS NOT IN A COMPONENT: tokens and base elements cross Product Components by definition. A
+     colour scale living in one component's 01-ux/ is a colour scale the other six will each redefine.
+
+     WHY ux.md DOES NOT SERVE IT: ux.md is the shape of DESIGN.md and EXPERIENCE.md, which are per
+     component. This is the third file, at product level, and it had no template at all.
+
+     THE CODE IS THE SSOT FOR VALUES. Where this repo's web side states a token in tokens.css, this
+     file MUST reference it rather than repeat the value. Two homes for one hex code is two hex codes
+     within a month. Read web/README.md before writing anything here — it is the authority for the
+     web side, and it MUST NOT be contradicted from this file.
+
+     Token and element NAMES are English: they are machine-facing keys, per language-guide.md. -->
+
+## Where the values actually live
+
+<!-- One line per source of truth — the stylesheet, the config, the generated file — with its path.
+     This section is what stops the rest of the document becoming a stale copy. -->
+
+## Tokens
+
+<!-- One table per scale. Name, what it is for, and where it resolves. NOT the raw value, unless this
+     file is genuinely the only place it exists. -->
+
+| Token | For | Resolves in |
+| --- | --- | --- |
+
+## Base elements
+
+<!-- The LC type `ui-element`, registered in components.yaml. One row each: what it is, its states,
+     and where its implementation lives. A composite reused across screens is `ui-composite` and
+     belongs in .how/<pc>/01-ux/, not here. -->
+
+| Element | States it MUST support | Implementation |
+| --- | --- | --- |
+
+<!-- Every element MUST state its empty, loading, error, and disabled states where they apply. The
+     populated state is the one that always gets designed; the others are the ones that ship broken. -->
+
+## Rules that bind every screen
+
+<!-- Only what a screen cannot legitimately override. Each MUST state what it prevents — a rule with
+     no failure behind it is a preference, and preferences go to ../../../project/codebase-conventions-guide.md.
+
+     A rule here that also holds for non-UI code is an AD-N and belongs in the spine instead. -->
+
+| Rule | Prevents |
+| --- | --- |
+
+## What this system deliberately does not cover
+
+<!-- Where a component is free to choose for itself. Absent, every local choice reads as a violation. -->

package/kit/.constitution/{document → method/document}/templates/inventory.md

@@ -1,69 +1,69 @@
----
-type: inventory
-kind: db                 # db · api · screen · endpoint — decides the row shape below
-scope: _platform         # `_platform` for the three product-level inventories; `{pc}` for kind: endpoint
-status: draft            # draft · reviewed · locked · superseded
-created: '{YYYY-MM-DD}'
-updated: '{YYYY-MM-DD}'
-derived_from: plan       # plan · code — see the TEMPLATE GUIDE
-verified: ''             # commit SHA the derivation was read at; required when derived_from: code
----
-
-# Inventory — {tables | endpoints | screens | endpoints of {pc}}
-
-<!-- TEMPLATE GUIDE — act on these comments, then delete them.
-
-     ONE template, four kinds. Only the row shape differs; the rules are the same for all four.
-
-       kind: db      -> .how/_platform/inventory-db.md
-       kind: api     -> .how/_platform/inventory-api.md
-       kind: screen  -> .how/_platform/inventory-screen.md
-       kind: endpoint-> .how/<pc>/02-contracts/00-inventory.md, at mode: deep only
-
-     The first three are BLUEPRINT output, born at G3 by wdi-blueprint intent `platform`. They exist
-     at every `mode`, including catalog, and they are what makes catalog usable at all: the use case
-     list plus these three plus C4 is the whole record a builder gets there.
-
-     THE NUMBER IS STABLE. A new row takes the next `No`, never a renumber. Renumbering renames every
-     file after it and breaks every link pointing at them. A removed row keeps its number and its
-     status becomes `removed`; the number MUST NOT be reused.
-
-     TWO WAYS THIS FILE COMES TO EXIST, and derived_from says which:
-       plan  no code yet. Written as intent — the tables, endpoints, or screens planned. Nothing can
-             be derived, because there is no source.
-       code  code exists. Derived by .constitution/scripts/inventory.py — migrations for tables,
-             route registration for endpoints, pages for screens — and THEN compared with the plan.
-             The difference is a FINDING, reported. It MUST NOT be patched into agreement by hand.
-
-     MUST NOT be assembled from a README, from a route name that looks plausible, or from memory. -->
-
-## Rows
-
-<!-- kind: db -->
-
-| No | Table | Owning component | What it holds | Key columns | Status |
-| --- | --- | --- | --- | --- | --- |
-
-<!-- kind: api  — keep this block and delete the others
-| No | Method | Path | Owning component | Description | Status |
-| --- | --- | --- | --- | --- | --- |
--->
-
-<!-- kind: screen
-| No | Screen | Route | Owning component | Actor | UC served |
-| --- | --- | --- | --- | --- | --- |
--->
-
-<!-- kind: endpoint
-| No | Method | Path | Spec file | Status |
-| --- | --- | --- | --- | --- |
--->
-
-<!-- Status values: draft · published · deprecated · removed. A row with no status reads as
-     published, which is the one reading that is never safe. -->
-
-## Findings
-
-<!-- Only when derived_from: code. Each difference between the plan and what the code actually does,
-     one line each, with which side is being reported — not which side was changed. Nothing here is
-     resolved by editing the other side; a finding routes to the skill that owns it. -->
+---
+type: inventory
+kind: db                 # db · api · screen · endpoint — decides the row shape below
+scope: _platform         # `_platform` for the three product-level inventories; `{pc}` for kind: endpoint
+status: draft            # draft · reviewed · locked · superseded
+created: '{YYYY-MM-DD}'
+updated: '{YYYY-MM-DD}'
+derived_from: plan       # plan · code — see the TEMPLATE GUIDE
+verified: ''             # commit SHA the derivation was read at; required when derived_from: code
+---
+
+# Inventory — {tables | endpoints | screens | endpoints of {pc}}
+
+<!-- TEMPLATE GUIDE — act on these comments, then delete them.
+
+     ONE template, four kinds. Only the row shape differs; the rules are the same for all four.
+
+       kind: db      -> .how/_platform/inventory-db.md
+       kind: api     -> .how/_platform/inventory-api.md
+       kind: screen  -> .how/_platform/inventory-screen.md
+       kind: endpoint-> .how/<pc>/02-contracts/00-inventory.md, at mode: deep only
+
+     The first three are BLUEPRINT output, born at G3 by wdi-blueprint intent `platform`. They exist
+     at every `mode`, including catalog, and they are what makes catalog usable at all: the use case
+     list plus these three plus C4 is the whole record a builder gets there.
+
+     THE NUMBER IS STABLE. A new row takes the next `No`, never a renumber. Renumbering renames every
+     file after it and breaks every link pointing at them. A removed row keeps its number and its
+     status becomes `removed`; the number MUST NOT be reused.
+
+     TWO WAYS THIS FILE COMES TO EXIST, and derived_from says which:
+       plan  no code yet. Written as intent — the tables, endpoints, or screens planned. Nothing can
+             be derived, because there is no source.
+       code  code exists. Derived by .constitution/method/scripts/inventory.py — migrations for tables,
+             route registration for endpoints, pages for screens — and THEN compared with the plan.
+             The difference is a FINDING, reported. It MUST NOT be patched into agreement by hand.
+
+     MUST NOT be assembled from a README, from a route name that looks plausible, or from memory. -->
+
+## Rows
+
+<!-- kind: db -->
+
+| No | Table | Owning component | What it holds | Key columns | Status |
+| --- | --- | --- | --- | --- | --- |
+
+<!-- kind: api  — keep this block and delete the others
+| No | Method | Path | Owning component | Description | Status |
+| --- | --- | --- | --- | --- | --- |
+-->
+
+<!-- kind: screen
+| No | Screen | Route | Owning component | Actor | UC served |
+| --- | --- | --- | --- | --- | --- |
+-->
+
+<!-- kind: endpoint
+| No | Method | Path | Spec file | Status |
+| --- | --- | --- | --- | --- |
+-->
+
+<!-- Status values: draft · published · deprecated · removed. A row with no status reads as
+     published, which is the one reading that is never safe. -->
+
+## Findings
+
+<!-- Only when derived_from: code. Each difference between the plan and what the code actually does,
+     one line each, with which side is being reported — not which side was changed. Nothing here is
+     resolved by editing the other side; a finding routes to the skill that owns it. -->

package/kit/.constitution/{document → method/document}/templates/model.md

@@ -32,8 +32,8 @@ updated: '{YYYY-MM-DD}'
 
 ## Relationships
 
-<!-- Direction and cardinality. State them as sentences a person would say: "satu member punya nol
-     atau satu sponsor". -->
+<!-- Direction and cardinality. State them as sentences a person would say: "one member has zero
+     or one sponsor". -->
 
 ## State Lifecycle
 

package/kit/.constitution/{document → method/document}/templates/questions.md

@@ -6,7 +6,7 @@ created: '{YYYY-MM-DD}'
 updated: '{YYYY-MM-DD}'
 ---
 
-# {Pertanyaan yang Memblokir | Asumsi | Menunggu Pihak Luar | Terjawab}
+# {Blocking Questions | Assumptions | Waiting on an Outside Party | Answered}
 
 <!-- TEMPLATE GUIDE — act on these comments, then delete them.
 
@@ -30,8 +30,9 @@ updated: '{YYYY-MM-DD}'
      A ROW MOVES BETWEEN FILES WHEN ITS CLASS CHANGES, and it MUST NOT be copied into a second one.
 
      Ids stay OQ-, allocated from the highest ever used including closed ones. An id MUST NOT be
-     reused. The literal values inside the tables stay Bahasa Indonesia — [BELUM DITETAPKAN] and the
-     rest — wherever they appear, including inside an English template. -->
+     reused. The prose inside the tables follows the product's `doc_language`; a machine-facing
+     marker such as `[NEEDS CONFIRMATION]` stays English wherever it appears — `language-guide.md`
+     owns that split. -->
 
 ## The class test
 
@@ -47,26 +48,26 @@ updated: '{YYYY-MM-DD}'
 
      A question MUST NOT be filed as blocking "to be safe". That habit is what produced 146 ids. -->
 
-## Terbuka
+## Open
 
 <!-- list: blocking · external -->
 
-| id | Pertanyaan | Memblokir | Owner | Sebelum |
+| id | Question | Blocks | Owner | Before |
 |---|---|---|---|---|
 
 <!-- list: assumptions — keep this shape instead
-| id | Asumsi | Akibat kalau salah | Diambil | Oleh |
-|---|---|---|---|---|
+| id | Assumption | Cost if wrong | Taken | By |
+|---|---|---|---|---|---|
 -->
 
 <!-- An empty list is a legitimate state and MUST be written as one, with the date and one line
      saying why. An empty table with no sentence reads as an unfinished file. -->
 
-## Terjawab
+## Answered
 
 <!-- list: answered only.
 
-     | id | Pertanyaan | Jawaban | Tanggal | Oleh |
+     | id | Question | Answer | Date | By |
 
      The answer is written beside the question, not in place of it. The record of what was once
      uncertain is what stops the same question being asked again in three months.

package/kit/.constitution/{document → method/document}/templates/sdd.md

@@ -137,7 +137,7 @@ reviewed:                # V13. Diisi hanya setelah bmad-review benar-benar dija
                        alone does not say what a column means. LC type store
      06-flows/         [deep]. Sequence diagrams ONLY for flows involving money, irreversible state, or
                        a third party. Lane order is fixed once for the project in
-                       codebase/conventions-guide.md; the No-op lane rule is REPEALED
+                       ../../../project/codebase-conventions-guide.md; the No-op lane rule is REPEALED
 
      supplements/ is REPEALED along with the ANX- concept it existed for. -->
 

package/kit/.constitution/{document → method/document}/templates/srs.md

@@ -66,7 +66,7 @@ reviewed:                # V13. Diisi hanya setelah bmad-review benar-benar dija
 
 | id | Use case | Actor | Satisfies | critical |
 | --- | --- | --- | --- | --- |
-| UC-{n} | {a sentence a user would say} | {from the Actor Register} | {FR-n} | tidak |
+| UC-{n} | {a sentence a user would say} | {from the Actor Register} | {FR-n} | no |
 
 ## Constraints · [G3]
 
@@ -106,7 +106,7 @@ reviewed:                # V13. Diisi hanya setelah bmad-review benar-benar dija
 
 ## Gate Checklist · [G3]
 
-<!-- The gate questions as they apply to THIS component, answered ya / tidak / ubah. The full list
+<!-- The gate questions as they apply to THIS component, answered yes / no / change. The full list
      lives in delivery-flow-guide.md and MUST NOT be copied here. At mode: catalog only the starred
      questions are asked. -->