wdi-method 0.3.0

package/kit-overlay/constitution.md

@@ -0,0 +1,135 @@
+---
+status: Accepted
+---
+
+# Constitution — {product}
+
+Rewrite Articles 2 and 5 for the product this repo is. Article 1 cites
+`.control/registry/index.yaml` — replace `{product}` there at G1, not here.
+Articles 3, 4, 6, and 7 are the method and travel unchanged.
+
+An agent working here MUST be able to act on the contents of this repo alone.
+
+## Article 1 — Scope
+
+This repo covers the product named at `product.name` in
+`.control/registry/index.yaml`. One product, one repo. A second product MUST
+get a repo of its own.
+
+`product.client` in the same file names the client if there is one, and stays
+empty if there is not. The product brief at G1 uses `product.name` as its
+title. Neither this file nor the brief is a second source of the name.
+
+An agent working here MUST NOT demand that sibling organisation repositories
+be open in the same session.
+
+## Article 2 — Content boundary, `.work/`, and cross-repo references
+
+All three are governed by [`repo-guide.md`](repo-guide.md). Its rules MUST NOT be
+repeated here — one rule, one place.
+
+What is particular to this repo, and therefore lives here:
+
+- Name any extra boundary this product has (a public-repo rule, a ban on `3p.md`,
+  a `.work/` resting state). If there is none, delete this bullet list and the
+  sentence above it.
+- `3p.md` MUST NOT be created in a product repo. Operational engagement memory
+  lives outside.
+
+## Article 3 — Layers
+
+The repo layout is governed by `corpus-guide.md` and mapped by
+`.control/structure-document.md`. What MUST be known before opening either:
+
+| Path | Role |
+|---|---|
+| `.constitution/` | Rules — how we work. `method/` holds the non-binding explanation of them |
+| `.control/` | Control — what currently holds and what has been decided |
+| `.what/` | What is promised |
+| `.how/` | How it is built |
+| `_bmad-output/` | Run workspace; committed, not curated |
+| `.work/` | Scratch; committed, emptied when a task closes |
+| *(application roots)* | Application code — name them in this row |
+
+The method does not use a `docs/` layer for corpus or rules. A leftover `docs/`
+folder is inventory to sort, not a second home.
+
+## Article 4 — Lifecycle
+
+Every `.constitution/` file MUST carry a `status:` frontmatter, and it MUST be one of five:
+
+| Status | Means |
+|---|---|
+| `Accepted` | **Binds.** It MAY be cited as the reason to reject a change |
+| `Reference` | **Explains, does not bind.** It MUST NOT be cited as the reason to reject a change, and MUST NOT be installed as `doc_standards` or `persistent_facts` |
+| `Draft` | Not settled. Its contents MAY be read as guidance but MUST NOT be used to reject a change |
+| `Superseded` | Replaced. It MUST name its replacement |
+| `Cancelled` | Withdrawn without a replacement, and kept so nobody rewrites it |
+
+**One exception, by construction:** a file in `document/templates/` MUST NOT carry a `status:` of its own.
+A template's frontmatter is the *artifact's* frontmatter — it is copied into what the template produces —
+so a status there would land in the artifact and mean something else entirely.
+
+A missing header anywhere else is a **finding**, not an implicit anything.
+
+`Reference` exists so that the *explanation* of a rule can live beside the rule without competing with it —
+`method/` holds four such files. Where a `Reference` file and an `Accepted` one disagree, the `Accepted`
+one wins, and the disagreement MUST be reported as a defect rather than resolved by preferring whichever was
+opened first. A rule MUST NOT be born in a `Reference` file; when one is noticed there, it is stated as a
+finding and written in the guide that owns it.
+
+## Article 5 — The method arrives from WDI Method
+
+This is the **consumer** article. Use it in every product repo.
+
+`.constitution/` guides and templates (except this file's Articles 1, 2, and 5,
+`codebase/*-guide.md`, 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`.
+
+- 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`.
+- `wdi-method update` MUST overwrite method files and MUST NOT touch `.what/`,
+  `.how/`, `.control/` product state, this file's Articles 1–2 and 5,
+  `codebase/*-guide.md` once `Accepted`, extra constitution files this repo
+  added, or `_bmad/custom/*.user.toml`.
+- A rule particular to this repo MUST be written out in full in this file or a
+  sibling, and MUST NOT be replaced by a pointer into another repository.
+
+A prefix in `.claude/skills/` names the **method**, not the owner: `bmad-*` is
+BMad's, `wdi-*` is this method's.
+
+## Article 6 — Decisions
+
+A decision worth remembering is a `DEC-NNN`. Its shape, the one test that decides whether it is
+recorded at all, global numbering, the `draft → accepted → applied` status ladder, and supersession
+are governed by [`document/decision-guide.md`](document/decision-guide.md). Decisions live in
+`.control/decisions/` and are registered in `.control/registry/decisions.yaml`.
+
+Recording a decision is **not mandatory**, and one case is: a decision that contradicts or changes an
+`AD-N`. The guide owns both halves and they MUST NOT be restated here.
+
+The name ADR is retired, along with `layer:` and `component:` on a decision. `ADR-NNN` appearing in a
+document frozen before that date is a retired alias for `DEC-NNN`, and those documents MUST NOT be
+rewritten for the prefix. A course correction is a `DEC-` of `type: course-correction`.
+
+## Article 7 — Non-technical facts
+
+A non-technical fact that constrains what may be built, used, or promised — a domain now held, a
+third-party account now active, the legal entity a screen must name, a date that locks scope — MUST
+be recorded in `.control/project-non-technical-log.md`, and MUST NOT be scattered into a `DEC-`, a
+PRD, or a code comment as though it were an engineering constraint.
+
+That file states its own entry shape, its closed category list, and which facts belong to another
+home instead. It MUST be written through the skill `wdi-log` intent `fact`, never by hand.
+
+Two boundaries hold over it and MUST NOT be relaxed there:
+
+- The content boundary in [`repo-guide.md`](repo-guide.md). This file is not an exemption from it;
+  a commercial fact does not become admissible by being called non-technical.
+- Article 2's ban on `3p.md`. Operational engagement memory stays outside this repo, and the log
+  MUST NOT grow into a substitute for it.
+
+It is control, not chronology. What happened on a given day is recovered from git by `wdi-report`;
+what is recorded here is what still holds.

package/kit-overlay/portability.md

@@ -0,0 +1,91 @@
+---
+status: Reference
+---
+
+# Portability — what is method, what is product
+
+**Opened when:** carrying a method change into the WDI Method package, or installing
+the method in a product repo.
+
+This file **explains**. It does not bind. Installing is the act, and that act lives in
+the WDI Method package README plus `wdi-method` (`install` · `update` · `promote` ·
+`verify`). Where this file and that README disagree, the README wins and the
+disagreement is a defect.
+
+It exists so that "promote the method, leave the product" is not a fresh re-reading of
+fifty files every time.
+
+## The seam
+
+Most of `.constitution/` is portable as it stands. A handful name **this product**, and in most of
+them only an *example* does — not a rule.
+
+| File | What is this product's | What to do when carrying it |
+|---|---|---|
+| `constitution.md` | Articles 1, 2, and 5 | **Rewrite 2 and 5.** Article 1 cites `index.yaml` `product.name`. Articles 3, 4, 6, 7 travel unchanged. `wdi-method promote` already replaces this file with the kit template |
+| `document/architecture-guide.md` | Seed examples of stack and tree shape | Re-point the examples. Every rule around them travels |
+| `document/corpus-guide.md` | Worked examples of `_platform` ownership | Re-point the examples. **Keep both kinds**: they teach the trap better than the rule alone |
+| `templates/design-system.md` | The pointer to wherever this project keeps its tokens | Re-point at that project's token file |
+| `templates/oq.md` | One example of a bad question title | Cosmetic |
+
+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.
+
+## What does NOT travel
+
+| Stays behind | Why |
+|---|---|
+| `.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/codebase/*-guide.md` | Written by the **project**, not the method. They ship as empty `Draft` stubs |
+| `_bmad-output/` | Run workspace |
+| The `bmad-*` skills themselves | BMad's, installed by BMad. Only `_bmad/custom/*.toml` is ours |
+
+## What travels beside `.constitution/`
+
+The method is not `.constitution/` alone. Three sets move together, and carrying one without the
+others leaves a method that cannot run:
+
+| Set | Note |
+|---|---|
+| `.constitution/` | Minus the product articles; `promote` / `install` handle the seam |
+| `.claude/skills/wdi-*/` (and `.agents/skills/wdi-*/` when those agents are selected) | Every wrapper. A wrapper without its guide, or a guide without its wrapper, is half a method |
+| `_bmad/custom/*.toml` | The one most likely to be forgotten. `*.user.toml` stays behind |
+| `AGENTS.md` | The routing table is the method; from `## Code` down is the product. `install` / `update` MUST NOT overwrite an existing `AGENTS.md` |
+
+## Two directions
+
+```
+a product repo with a newer working copy of the method
+        --promote-->
+WDI Method (this package)
+        --install / update-->
+product repos
+```
+
+- **Promote** copies the method *up* once it has settled in a working copy.
+- **Install / update** copies that snapshot *out* to a repo that consumes it.
+- Do not run `update` against a repo you are about to promote from — that would overwrite the newer copy.
+- There is no SHA lock and no per-file increment. The snapshot is the unit. The package version on npm / GitHub is the name of that snapshot.
+
+## Installing in a fresh repo
+
+BMad first (`npx bmad-method install`), then WDI Method. There is no numbered install runbook:
+the steps that a runbook used to carry are now `wdi-init` intent `setup`. The order the acts come in:
+
+1. `npx bmad-method install` in the product repo.
+2. `npx wdi-method install` (optionally `--agents …`).
+3. Set `product.name` in `.control/registry/index.yaml`. Rewrite `constitution.md` Articles 2 and 5.
+4. Merge the method routing into `AGENTS.md` if that file already existed.
+5. Run `wdi-init` intent `setup`.
+6. Sort what already existed. A file that is already the artifact one slot asks for goes into that
+   slot through the skill that owns it; everything else goes to `_bmad-output/prior-knowledge/`.
+   `corpus-guide.md` owns that test.
+7. Then G1 — which confirms `product.name` and writes the brief under that name.
+
+**Two things a fresh install MUST NOT do:**
+
+- Set `mode` and `risk_accepted` before the components exist. They are per-component fields, and the
+  components are born at the tail of G2.
+- Fill `.control/generated/` by hand. It is script output, and a hand-written table there is the one
+  lie no validator catches.

package/kit-overlay/repo-guide.md

@@ -0,0 +1,97 @@
+---
+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.
+

package/lib/agents-block.mjs

@@ -0,0 +1,52 @@
+export const BEGIN = "<!-- BEGIN:wdi-method -->";
+export const END = "<!-- END:wdi-method -->";
+
+export function extractBlock(template) {
+  const i = template.indexOf(BEGIN);
+  const j = template.indexOf(END);
+  if (i === -1 || j === -1 || j < i) {
+    throw new Error("AGENTS.md template is missing BEGIN/END:wdi-method markers");
+  }
+  return template.slice(i, j + END.length).trimEnd();
+}
+
+export function hasMethodBlock(text) {
+  return text.includes(BEGIN) && text.includes(END) && text.indexOf(END) > text.indexOf(BEGIN);
+}
+
+export function replaceMarkedBlock(text, block) {
+  const i = text.indexOf(BEGIN);
+  const j = text.indexOf(END);
+  return `${text.slice(0, i)}${block}${text.slice(j + END.length)}`;
+}
+
+export function injectWithoutMarkers(text, block) {
+  const start = text.search(/^## Language\s*$/m);
+  if (start !== -1) {
+    const rest = text.slice(start);
+    const endRel = rest.search(/\n(?=## Code\b|<!-- BEGIN:|## Sync rule\b)/);
+    const end = endRel === -1 ? text.length : start + endRel;
+    const before = text.slice(0, start).replace(/\s+$/, "\n\n");
+    const after = text.slice(end).replace(/^\s+/, "\n\n");
+    return `${before}${block}${after}`;
+  }
+  const heading = text.match(/^#[^\n]+\n+/);
+  const at = heading ? heading[0].length : 0;
+  return `${text.slice(0, at)}\n${block}\n\n${text.slice(at).replace(/^\s+/, "")}`;
+}
+
+export function upsertMethodBlock(existing, template) {
+  const block = extractBlock(template);
+  if (!existing || !existing.trim()) {
+    return template;
+  }
+  if (hasMethodBlock(existing)) {
+    return replaceMarkedBlock(existing, block);
+  }
+  return injectWithoutMarkers(existing, block);
+}
+
+export function fillProductTitle(template, productName) {
+  if (!productName || productName === "{product}") return template;
+  return template.replace(/^# Agent Rules — \{product\}/m, `# Agent Rules — ${productName}`);
+}

package/lib/identity.mjs

@@ -0,0 +1,65 @@
+const PRODUCT_BLOCK = /(?:^|\n)product:\n(?:  .*\n)*/;
+
+export function yamlQuote(value) {
+  return `"${String(value).replaceAll("\\", "\\\\").replaceAll('"', '\\"')}"`;
+}
+
+export function readProductIdentity(text) {
+  const name = text.match(/product:\n(?:  .*\n)*?  name:\s*"([^"]*)"/);
+  const client = text.match(/product:\n(?:  .*\n)*?  client:\s*"([^"]*)"/);
+  return {
+    name: name ? name[1] : "",
+    client: client ? client[1] : "",
+  };
+}
+
+export function writeProductIdentity(text, { name, client }) {
+  const block =
+    `product:\n  name: ${yamlQuote(name)}\n  client: ${yamlQuote(client ?? "")}\n`;
+  if (/^product:/m.test(text)) {
+    return text.replace(PRODUCT_BLOCK, (m) => (m.startsWith("\n") ? `\n${block}` : block));
+  }
+  return `${block}\n${text.replace(/^/, "")}`;
+}
+
+export function identityIsPlaceholder(name) {
+  return !name || name === "{product}";
+}
+
+// ---------------------------------------------------------------------- language policy
+//
+// Two settings, and only two. Everything else about language is NOT a choice: method terminology,
+// document code prefixes, machine-facing markers, and code identifiers are always English —
+// `language-guide.md` owns that, and a caller MUST NOT ask about them.
+//
+//   doc_language           the PROSE of working documents in .what/ .how/ .control/
+//   doc_filename_language  the SLUG part of a document filename
+//
+// Both default to `en`. A corpus written before these existed is NOT migrated for them: the readers
+// in validate.py accept both languages, so an existing document keeps working and only new writing
+// follows the setting.
+const POLICY_BLOCK = /(?:^|\n)policy:\n(?:  .*\n)*/;
+export const DOC_LANGUAGES = ["en", "id"];
+
+export function readLanguagePolicy(text) {
+  const doc = text.match(/policy:\n(?:  .*\n)*?  doc_language:\s*([A-Za-z-]+)/);
+  const file = text.match(/policy:\n(?:  .*\n)*?  doc_filename_language:\s*([A-Za-z-]+)/);
+  return {
+    docLanguage: doc ? doc[1] : "",
+    docFilenameLanguage: file ? file[1] : "",
+  };
+}
+
+export function writeLanguagePolicy(text, { docLanguage, docFilenameLanguage }) {
+  const block =
+    `policy:\n  doc_language: ${docLanguage}\n  doc_filename_language: ${docFilenameLanguage}\n`;
+  if (/^policy:/m.test(text)) {
+    return text.replace(POLICY_BLOCK, (m) => (m.startsWith("\n") ? `\n${block}` : block));
+  }
+  // Sits right after `product:` when that block exists — the two answer the same kind of question,
+  // so a reader who finds one finds the other.
+  if (/^product:/m.test(text)) {
+    return text.replace(/^product:\n(?:  .*\n)*/m, (m) => `${m}\n${block}`);
+  }
+  return `${block}\n${text.replace(/^/, "")}`;
+}

package/package.json

@@ -0,0 +1,37 @@
+{
+  "name": "wdi-method",
+  "version": "0.3.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/generated/.gitkeep

@@ -0,0 +1,2 @@
+# generated/ is script output. MUST NOT be edited by hand.
+# validate.py --generate and timeline.py write here.

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

@@ -0,0 +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. -->

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

@@ -0,0 +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 |
+|---|---|---|---|
+| — | — | — | — |

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

@@ -0,0 +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 |
+|---|---|---|---|
+| — | — | — | — |

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

@@ -0,0 +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 |
+|---|---|---|---|---|
+| — | — | — | — | — |

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

@@ -0,0 +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 |
+|---|---|---|---|---|
+| — | — | — | — | — |

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

@@ -0,0 +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 |
+|---|---|---|---|
+| — | — | — | — |

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

@@ -0,0 +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: []

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

@@ -0,0 +1,6 @@
+# decisions.yaml — SSOT untuk keputusan `DEC-`
+#
+# Penomoran GLOBAL. `status`: draft | accepted | applied | superseded | rejected.
+# Keputusan MEMBEKU saat `applied`, bukan saat `accepted`.
+
+decisions: []

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

@@ -0,0 +1,3 @@
+# defects.yaml — SSOT untuk cacat: bug biasa dan hotfix.
+
+defects: []