wdi-method 0.5.4 → 0.5.9

package/kit/skills/wdi-log/SKILL.md

@@ -1,107 +1,107 @@
----
-name: wdi-log
-description: Use when a fact from outside the code has to be recorded — a meeting that finished, or a non-technical fact that constrains what may be built. Two intents, meeting and fact. Routes decisions and open questions to their own skills.
----
-
-# WDI Log
-
-Free of stage and free of role. Two intents, because both record **a fact that came from outside the code** and
-neither belongs to any gate.
-
-| Intent | Owns | Home |
-|---|---|---|
-| `meeting` | What a meeting decided and left open | `.control/meetings/YYYY-MM-DD-<slug>.md` |
-| `fact` | A non-technical fact that constrains what may be built, used, or promised | `.control/project-non-technical-log.md` |
-
-They share a shape and a failure mode: both are tempting places to record something that belongs somewhere with
-an owner. Neither MAY absorb a decision or an open question.
-
-## Intent `meeting`
-
-### What the note MUST carry
-
-| Section | Content |
-|---|---|
-| Attendees and date | Who was actually there, not who was invited |
-| What was decided | Each decision as one sentence, stated as what now holds |
-| What was left open | Each unresolved item, with who can resolve it |
-| Action items | Grouped by role, each with an owner |
-| `## DEC` | Links to the decisions this meeting produced — filled after `wdi-decision` runs |
-
-The `## DEC` back-link makes the trail run both ways. Minutes whose decisions have no `DEC-`, and a `DEC-` with
-no minutes behind it, are both traceability gaps the audit surfaces later at a worse time.
-
-### Rules
-
-- It MUST NOT write the decision itself. That goes to `wdi-decision` intent `open`, which numbers it globally.
-  Minutes say what was **discussed**; a `DEC-` says what was **chosen** and what it cost.
-- It MUST NOT write to `.what/` or `.how/`. A meeting changes documents only through `wdi-decision` intent
-  `apply`.
-- It MUST NOT record an open question only in the note. Those go to `wdi-question`, so they land in one of four
-  lists rather than scattered across meetings nobody rereads.
-- Record what was decided, not what was discussed. A transcript is not minutes, and nobody rereads one.
-- A decision recorded with no owner and no consequence MUST be treated as an open question instead. "We agreed
-  to look into it" is not a decision.
-- Client commitments MUST be recorded verbatim where the wording matters. Paraphrasing a commitment is how a
-  scope dispute starts.
-
-## Intent `fact`
-
-`.control/project-non-technical-log.md` is the authority on **what may be recorded** — its content boundary, its
-closed category list, and the table of facts belonging to another home. Read it before acting; this skill MUST
-NOT restate those rules and MUST NOT override them. What this skill owns is **how** the file is read and written.
-
-### Looking one up
-
-1. Read the Berlaku table in full. It is short by design and MUST NOT be sampled with grep alone — a fact retired
-   last week reads as current when only its row is seen.
-2. Check Tidak Berlaku Lagi for the same subject. A superseded entry names its replacement.
-3. If the answer is absent, **say it is absent.** You MUST NOT infer a fact from a commit message, from
-   `.control/memlog/`, or from a sibling repo and report it as recorded — those are leads for registering, not
-   answers.
-
-An entry marked `[BELUM DIKONFIRMASI]` MUST be reported with that tag attached, never flattened into a plain
-fact.
-
-### Registering one
-
-1. Apply the log's content boundary first. A fact that fails it is refused here and MUST NOT be softened to fit —
-   say which rule refused it and where it belongs.
-2. **Route before writing.** If the fact is a decision expensive to reverse, an open question, a meeting outcome,
-   a domain term, or an infrastructure asset detail, its own skill or repo runs first. A row here MAY then hold
-   only the consequence for this product, pointing at that home.
-3. Assign the next `NT-NNN` from the highest id ever used, including retired ones. An id MUST NOT be reused.
-4. Fill every column. `Akibat` MUST name something in this repo — a gate, an `FR`, a prerequisite, a file.
-   `Sumber` MUST name a person, a repo and path, or another entry id.
-5. A fact whose source is hearsay MUST be written with `[BELUM DIKONFIRMASI]` **and** filed through
-   `wdi-question` in the same run. Recording it and leaving it unowned is the failure this step exists to stop.
-
-**One fact, one row.** A single event producing several facts — a domain bought, and a launch date it makes
-possible — MUST become several rows, because they stop holding at different times.
-
-### Updating one
-
-A fact that changed is **never** edited in place, and its row is never deleted.
-
-1. Move the old row to Tidak Berlaku Lagi, filling `Berhenti berlaku` with the date and `Digantikan` with the new
-   id.
-2. Register the new fact as a fresh `NT-NNN`.
-3. Follow the old row's `Akibat` and check whatever it named. A fact that stops holding usually leaves a document
-   behind that still assumes it; that document MUST be raised, and if it sits under an `applied` decision, routed
-   to `wdi-decision` intent `apply`.
-
-Correcting a typo or a wrong `Sumber` is not an update in this sense and MAY be edited in place.
-
-## Rules
-
-- Terms MUST match `.control/product-glossary.md`. A note that coins a new domain noun MUST propose it through
-  `wdi-blueprint`, not leave two words meaning the same thing.
-- This skill MUST NOT write any file other than the two it owns. Every other file it touches is reached through
-  the skill that owns it.
-- `.control/structure-document.md` MUST NOT be edited to reflect a new entry — it maps folders, not rows, and
-  `wdi-init` intent `structure` re-derives it.
-
-## Output
-
-Intent taken · what was recorded, in one line · what was **routed** rather than recorded, and to which skill ·
-for `fact`, the `NT-` id and what its `Akibat` names.
+---
+name: wdi-log
+description: Use when a fact from outside the code has to be recorded — a meeting that finished, or a non-technical fact that constrains what may be built. Two intents, meeting and fact. Routes decisions and open questions to their own skills.
+---
+
+# WDI Log
+
+Free of stage and free of role. Two intents, because both record **a fact that came from outside the code** and
+neither belongs to any gate.
+
+| Intent | Owns | Home |
+|---|---|---|
+| `meeting` | What a meeting decided and left open | `.control/meetings/YYYY-MM-DD-<slug>.md` |
+| `fact` | A non-technical fact that constrains what may be built, used, or promised | `.control/project-non-technical-log.md` |
+
+They share a shape and a failure mode: both are tempting places to record something that belongs somewhere with
+an owner. Neither MAY absorb a decision or an open question.
+
+## Intent `meeting`
+
+### What the note MUST carry
+
+| Section | Content |
+|---|---|
+| Attendees and date | Who was actually there, not who was invited |
+| What was decided | Each decision as one sentence, stated as what now holds |
+| What was left open | Each unresolved item, with who can resolve it |
+| Action items | Grouped by role, each with an owner |
+| `## DEC` | Links to the decisions this meeting produced — filled after `wdi-decision` runs |
+
+The `## DEC` back-link makes the trail run both ways. Minutes whose decisions have no `DEC-`, and a `DEC-` with
+no minutes behind it, are both traceability gaps the audit surfaces later at a worse time.
+
+### Rules
+
+- It MUST NOT write the decision itself. That goes to `wdi-decision` intent `open`, which numbers it globally.
+  Minutes say what was **discussed**; a `DEC-` says what was **chosen** and what it cost.
+- It MUST NOT write to `.what/` or `.how/`. A meeting changes documents only through `wdi-decision` intent
+  `apply`.
+- It MUST NOT record an open question only in the note. Those go to `wdi-question`, so they land in one of four
+  lists rather than scattered across meetings nobody rereads.
+- Record what was decided, not what was discussed. A transcript is not minutes, and nobody rereads one.
+- A decision recorded with no owner and no consequence MUST be treated as an open question instead. "We agreed
+  to look into it" is not a decision.
+- Client commitments MUST be recorded verbatim where the wording matters. Paraphrasing a commitment is how a
+  scope dispute starts.
+
+## Intent `fact`
+
+`.control/project-non-technical-log.md` is the authority on **what may be recorded** — its content boundary, its
+closed category list, and the table of facts belonging to another home. Read it before acting; this skill MUST
+NOT restate those rules and MUST NOT override them. What this skill owns is **how** the file is read and written.
+
+### Looking one up
+
+1. Read the In force table in full. It is short by design and MUST NOT be sampled with grep alone — a fact retired
+   last week reads as current when only its row is seen.
+2. Check No longer in force for the same subject. A superseded entry names its replacement.
+3. If the answer is absent, **say it is absent.** You MUST NOT infer a fact from a commit message, from
+   `.control/memlog/`, or from a sibling repo and report it as recorded — those are leads for registering, not
+   answers.
+
+An entry marked `[UNCONFIRMED]` MUST be reported with that tag attached, never flattened into a plain
+fact.
+
+### Registering one
+
+1. Apply the log's content boundary first. A fact that fails it is refused here and MUST NOT be softened to fit —
+   say which rule refused it and where it belongs.
+2. **Route before writing.** If the fact is a decision expensive to reverse, an open question, a meeting outcome,
+   a domain term, or an infrastructure asset detail, its own skill or repo runs first. A row here MAY then hold
+   only the consequence for this product, pointing at that home.
+3. Assign the next `NT-NNN` from the highest id ever used, including retired ones. An id MUST NOT be reused.
+4. Fill every column. `Effect` MUST name something in this repo — a gate, an `FR`, a prerequisite, a file.
+   `Source` MUST name a person, a repo and path, or another entry id.
+5. A fact whose source is hearsay MUST be written with `[UNCONFIRMED]` **and** filed through
+   `wdi-question` in the same run. Recording it and leaving it unowned is the failure this step exists to stop.
+
+**One fact, one row.** A single event producing several facts — a domain bought, and a launch date it makes
+possible — MUST become several rows, because they stop holding at different times.
+
+### Updating one
+
+A fact that changed is **never** edited in place, and its row is never deleted.
+
+1. Move the old row to No longer in force, filling `Stopped holding` with the date and `Superseded by` with the new
+   id.
+2. Register the new fact as a fresh `NT-NNN`.
+3. Follow the old row's `Effect` and check whatever it named. A fact that stops holding usually leaves a document
+   behind that still assumes it; that document MUST be raised, and if it sits under an `applied` decision, routed
+   to `wdi-decision` intent `apply`.
+
+Correcting a typo or a wrong `Source` is not an update in this sense and MAY be edited in place.
+
+## Rules
+
+- Terms MUST match `.control/product-glossary.md`. A note that coins a new domain noun MUST propose it through
+  `wdi-blueprint`, not leave two words meaning the same thing.
+- This skill MUST NOT write any file other than the two it owns. Every other file it touches is reached through
+  the skill that owns it.
+- `.control/structure-document.md` MUST NOT be edited to reflect a new entry — it maps folders, not rows, and
+  `wdi-init` intent `structure` re-derives it.
+
+## Output
+
+Intent taken · what was recorded, in one line · what was **routed** rather than recorded, and to which skill ·
+for `fact`, the `NT-` id and what its `Effect` names.

package/kit/skills/wdi-report/SKILL.md

@@ -89,7 +89,7 @@ A published report is **frozen**. It states what was true on a date, exactly lik
 overwrite one (exit 4) rather than trusting anyone to remember.
 
 - You MUST NOT edit a published report. If it was wrong, the next report says so.
-- The `## Catatan` block is the one part a person writes, once, at publish time, before the commit.
+- The `## Note` block is the one part a person writes, once, at publish time, before the commit.
 - Commentary MUST cite rather than restate: a slip has a cause, and that cause already lives in a `DEC-`, an
   `OQ-`, a risk, or a defect.
 
@@ -144,11 +144,11 @@ is the ideal shape of a wave and because an `FR` has had a proof of done since b
 | `FR` | Its id |
 | Epic | The Product Component |
 | `mode` | That component's depth — this is what makes document load visible |
-| Paparan | `risk_accepted` + `risk_note` |
-| Beban | Mandays, derived from the parent `CAP`'s `estimate_mandays`, divided among its `FR` |
-| Prioritas | From the `CAP` |
-| Bergantung pada | From `depends_on` |
-| Rilis | The `CAP`'s `target_release` |
+| Exposure | `risk_accepted` + `risk_note` |
+| Effort | Mandays, derived from the parent `CAP`'s `estimate_mandays`, divided among its `FR` |
+| Priority | From the `CAP` |
+| Depends on | From `depends_on` |
+| Release | The `CAP`'s `target_release` |
 
 ## Step 4 — Say what it is, and what it is not
 

package/kit-overlay/README.md

@@ -68,6 +68,8 @@ used to reject a change.
 ## `scripts/`
 
 `validate.py` — registry gates and the `.control/generated/` generator. `timeline.py` — the time
-dimension from git history. `inventory.py` — derives the three inventories from code and reports the
-difference against the plan; it MUST NOT patch either side into agreement. All three run through
-`uv run`.
+dimension from git history. `inventory.py` — compares the three inventories against the code
+and reports the difference; it MUST NOT patch either side into agreement. It reads no code itself:
+the patterns live in `../project/inventory-readers.py`, because comparing is generic and reading a
+stack is not. That file ships as a skeleton and `wdi-init` intent `readers` writes it for the repo
+in front of it. All three run through `uv run`.

package/kit-overlay/portability.md

@@ -31,6 +31,12 @@ them only an *example* does — not a rule.
 Everything else — the five gates, the two fields, the fifteen skills, the templates, `validate.py`,
 `inventory.py`, `../method-glossary.md`, and the three files beside this one — carries without edit.
 
+One half-exception, and it is by design: `inventory.py` is the generic engine and carries whole, but
+it reads no code itself. The three readers live in `../../project/inventory-readers.py`, which ships
+as a skeleton and belongs to the product. A new project runs `wdi-init` intent `readers` once and
+rewrites that file, nothing else. No example ships, deliberately — an example is a guess about a
+stack nobody here has seen.
+
 ## What does NOT travel
 
 | Stays behind | Why |
@@ -38,6 +44,7 @@ Everything else — the five gates, the two fields, the fifteen skills, the temp
 | `.control/` | This product's state. A new project scaffolds its own through `wdi-init` intent `setup`, or receives empty stubs on first `install` |
 | `.what/` · `.how/` | This product's promises and build |
 | `.constitution/project/codebase-*-guide.md` | Written by the **project**, not the method. They ship as empty `Draft` stubs |
+| `.constitution/project/inventory-readers.py` | How THIS product's code is read. Seeded as a SKELETON — no patterns and no stack. `wdi-init` intent `readers` writes it against the repo in front of it |
 | `_bmad-output/` | Run workspace |
 | The `bmad-*` skills themselves | BMad's, installed by BMad. Only `_bmad/custom/*.toml` is ours |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wdi-method",
-  "version": "0.5.4",
+  "version": "0.5.9",
   "description": "WDI Method — software delivery method that wraps BMad",
   "type": "module",
   "bin": {

package/scaffold/.control/registry/decisions.yaml

@@ -1,6 +1,6 @@
-# decisions.yaml — SSOT untuk keputusan `DEC-`
+# decisions.yaml — SSOT for `DEC-` decisions
 #
-# Penomoran GLOBAL. `status`: draft | accepted | applied | superseded | rejected.
-# Keputusan MEMBEKU saat `applied`, bukan saat `accepted`.
+# Numbering is GLOBAL. `status`: draft | accepted | applied | superseded | rejected.
+# A decision FREEZES at `applied`, not at `accepted`.
 
 decisions: []