Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions .claude-plugin/marketplace.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
{
"name": "decision-driven-design",
"owner": {
"name": "Mind Over Machine",
"url": "https://github.com/mindovermachine-dev"
},
"description": "The Decision-Driven Design method as a Claude Code plugin, versioned with the method.",
"plugins": [
{
"name": "ddd-method",
"source": "./plugins/ddd-method",
"description": "Run the method step by step from its step cards, read at the plugin's pinned release."
}
]
}
20 changes: 19 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ each decision where it is resolved, and say which actor, whether person, program
each one and who answers for it. This repository is the method's software projection: the step
cards, the claims they rest on, and the decisions that rule them.

**v0.5.0 is a preview: ready to try, not ready to use (`DDD-dec-74`).** The register of each
**v0.7.0, a pre-release, is a preview: ready to try, not ready to use (`DDD-dec-74`).** The register of each
reason below is stated beside it, and the [status table](#status-step-by-step) gives each step's.

## Why use it
Expand Down Expand Up @@ -55,6 +55,24 @@ Varve is the **subject** of the design, not a dependency. The example is **expos
evidence**. It is falsified by the junior-engineer test: someone at first contact performs the step
and cannot name the value it gave them. Running that test is Emil's act, and it has not been run.

## Run it in Claude Code

The method is also a Claude Code plugin, [`plugins/ddd-method/`](plugins/ddd-method/)
(`DDD-dec-121`). It claims discipline, not better step execution.

```bash
claude plugin marketplace add mindovermachine-dev/decision-driven-design
```

```bash
claude plugin install ddd-method@decision-driven-design
```

Then run `/ddd-method:run`. The plugin holds no method content. It reads the step cards and the
claims they cite from this repository at its pin, **`v0.7.0`**, and stops if it cannot. Its version
tracks the pin (`0.7.0`). Any method release that changes what the skill reads advances both, in
the same change ([plugin README](plugins/ddd-method/README.md)).

## Where it is the wrong tool

- **You can only read the work back from existing code.** Step 1 maps forward from the domain and
Expand Down
103 changes: 103 additions & 0 deletions core/decisions/DDD-dec-121.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,103 @@
format: 1
id: DDD-dec-121
kind: decision
statement: |
The method is installable as a Claude Code plugin in this repository, ddd-method in the marketplace decision-driven-design (.claude-plugin/marketplace.json at the root, the plugin in plugins/ddd-method/), for anyone adopting the method. The plugin is thin: its one entry skill, /ddd-method:run, carries procedure and discipline only, and reads the step table, the step cards and the canon they cite from this repository at one pinned method release, from a clone at the tag or otherwise over HTTPS at the tag; when neither is reachable it says so and stops, and never fills from memory. Per-step skills are not added. The plugin's version is the method pin it reads without its v (0.7.0 for v0.7.0); a plugin-only change at the same pin takes a +p.N suffix (0.7.0+p.1), and a re-pin takes the new pin's version (0.8.0 for v0.8.0). Any method release that changes a file the skill reads, anything under method/ or a claim or decision a card cites, re-pins the plugin in the same change, whatever part of the version it moves. The plugin claims discipline, not better step execution: it refuses to treat a [PROPOSED] step as ruled, reads at the pin, and stops when it cannot; it does not claim that a step is performed better with it than without it. That claim rests on the plugin's evals run at its current pin, re-run at each re-pin.
principal: Emil
made: |
2026-11-08, Round 27 of the claude.ai conversation (verbatim in meta/sessions/2026-11-08-method-plugin/prompt.md and rulings.md), and 2026-11-11, Round 28 of the same rulings.md, Emil's answers in Claude's question dialog on claude.ai, filed by the method-plugin session; amended before landing on 2026-11-19 by Rounds 29 and 30 of the same rulings.md; Emil's landing of the branch is the ratification act
resolution: |
## Round 27 (claude.ai conversation, 2026-11-08)

- **Ruled: who installs it, and from where.** "From the repo, for practitioners
(Recommended)" (option text: "A Claude Code plugin in decision-driven-design (a skill plus
marketplace entry), installable by anyone adopting the method; versioned with the method").
- **Ruled: scope.** "The whole method (Recommended)" (option text: "All steps, each run from its
step card; refuses to treat [PROPOSED] steps as ruled; step 1 and the demand-flow step first
in practice").
- **Ruled: holding.** "Thin, reads the repo at a pin (Recommended)" (option text: "The skill
carries procedure and discipline; step cards and canon are fetched from the repository at the
pinned version, so it never drifts").

## Round 28 (2026-11-11, method-plugin rulings.md)

- **F-1: design and build accepted together.** "Accept both (Recommended)" (option text: "Design
and build are separate commits and the design matches the charter; record the missed gate as
a finding").
- **F-3: the version scheme.** "Yes (Recommended)" (option text: "0.7.0 now; 0.7.0+p.1 for a
plugin fix; 0.8.0 when it re-pins to v0.8.0. Claude Code updates on any version-string
change").
- **F-4: filed.** "File it (Recommended)" (option text: "Thin skill reading at a pin, one entry
skill, the version scheme, and the README claiming discipline rather than step quality").
- **F-9: the README's opening line** names the current release; the pull request is Emil's to
open.

## Round 29 (2026-11-19, method-plugin rulings.md)

- **The hold.** "#74 is held. It does not land at v0.7.0." #84 changed step 1 after v0.7.0, and
the plugin reads the step cards at v0.7.0. Landing it then would ship a plugin that teaches a
superseded step 1. When the release that carries #84 is tagged, the plugin re-pins to it, its
evals are reworked and re-run, and the branch is rebased onto main.

## Round 30 (2026-11-19, method-plugin rulings.md)

- **The release that carries #84 is v0.8.0**, MINOR under DDD-dec-82's first row (a ruled step
superseded incompatibly). It is cut in its own session.
- **This decision is amended in place** by amendments 1 to 4 of the Round 29 report: the re-pin
trigger, evidence by pin, the carrying release, and these rounds. Amendment 5 (DDD-dec-122 in
basedOn) is declined: #84 is the occasion, not the basis.

## What the plugin claims, and the evidence

Discipline, not step quality. From the eval table in
meta/sessions/2026-11-08-method-plugin/findings.md, **at the pin v0.7.0** (3 runs per arm, with
and without the plugin): step 1 on a small example shows no gain, 0.81 to 0.95 with the plugin and 0.86 to 0.90
without. The gain is in discipline: a [PROPOSED] step asked as ruled, 1.00 with and 0.75 without;
the repository unreachable, 1.00 with and 0.33 without (without the plugin, 2 of 3 runs rebuilt
step 1's card from memory); demand flow offered from the PDLC's kinds as a start, 1.00 with and
0.75 without. These are evals of an agent on cases written inside the framework: exercised
evidence about the plugin's behaviour, none about the method. The claim stands on the evals at
the plugin's current pin. They are re-run at each re-pin, and each pin's table is kept in the
record, never overwritten.

## What is filed

- `.claude-plugin/marketplace.json`; `plugins/ddd-method/` (plugin.json at 0.7.0, the skill
`run` pinned at v0.7.0, README.md, check.py, evals/).
- `plugins/ddd-method/check.py` as the `plugin` gate of scripts/ci.py: the marketplace entry and
the manifest agree, the version tracks the pin, and the skill holds no claim or decision id and
no run of eight words shared with method/.

## Relation to earlier decisions

- **Release.** The plugin pins the newest method release when it lands. Any method release that
changes a file the skill reads (anything under method/, or a claim or decision a card cites)
re-pins the plugin in the same change, whatever part of the version it moves. No release is cut
by this decision.
- **Name.** The plugin is ddd-method, not ddd, which is product-cli's tool for product
repositories (DDD-dec-100).
- **Supersedes nothing.**
basedOn:
- DDD-dec-82
- DDD-dec-75
- DDD-dec-74
- DDD-dec-100
- DDD-dec-79
notes: |
Id. At filing (2026-11-11), DDD-dec-119 and DDD-dec-120 are held on the branch
claude/zealous-ptolemy-3txf8k, and no branch holds a higher decision, so this takes DDD-dec-121.
Re-checked across every origin branch before commit and before push (findings.md).

Open, not ruled (findings.md): claude plugin validate is not in CI (F-5); where a practitioner's
artefacts go in a repository that uses product-cli's .ddd/ graph (F-6); thinness holds for the
skill's text, not for the model's memory (F-7); one eval run reported reading at the pin with no
git call recorded, not reproduced (F-8).

Amended before landing, in place, in Round 30 (2026-11-19, method-plugin rulings.md), on the
Round 29 report (findings.md, R-1). The occasion was DDD-dec-122 (#84), which superseded step 1
after v0.7.0 without adding a card or moving a register, so the MINOR-only re-pin trigger of the
first filing would not have re-pinned the plugin. DDD-dec-122 is named here as the occasion. It
is not a basis (Round 30, item 2).

Review trigger. A method release that changes a file the skill reads without re-pinning the
plugin; or an eval in which the plugin fills a card from memory.
61 changes: 61 additions & 0 deletions meta/sessions/2026-11-08-method-plugin/bootstrap.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
# Bootstrap — an installable plugin for the method, 2026-11-08

Filled in at arrival (2026-11-10) and committed with `prompt.md` as the session's first commit.

| Parameter | Value |
|---|---|
| Invocation | Interactive. Emil's Round 27 (claude.ai conversation, 2026-11-08) is verbatim in `prompt.md` |
| Principal | Emil (sole ratifier; ratifies by landing the branch) |
| Issue | [#72](https://github.com/mindovermachine-dev/decision-driven-design/issues/72). Every commit of the session carries `Refs #72` |
| Start condition | `git ls-remote --tags origin v0.7.0` → `72f8f139d476cc1e5f559ccef601f497ddda3a4b refs/tags/v0.7.0` (the annotated tag object). **The tag exists**, so the session starts |
| The pin | `v0.7.0`, which peels to commit `84aa4665b4b0392ef4bb08ac042e42ae9fc6d12c` |
| Downstream base | `main` at arrival = `84aa466` ("releases/v0.7.0.yaml: ratified_head 74e4805 (canon ratify v0.7.0)"). **`main` is the `v0.7.0` commit**: `git log v0.7.0..origin/main` is empty |
| Downstream branch | `claude/confident-goldberg-c0y0ia`, from `main` at `84aa466` |
| Upstream pin | `v5.15.2` (`graph/upstream.yaml`), read only and unchanged by this session |
| Claude Code | `claude` 2.1.322 in the session container (`/opt/node22/bin/claude`) |
| Model | Claude Opus 5.5 |

## Gates

The prompt says "Stop at every gate" and also asks for items 1 to 8 in one run, ending "and
stop". This session reads that as follows. At each gate, the prediction and the outcome are
recorded in `predictions.md` and checked before the next item starts. **Only G3 stops for Emil.**
If Emil wanted to review the design before anything was built, the build is a separate later
commit that he can drop (flagged as F-1 in `findings.md`).

| Gate | What | Who |
|---|---|---|
| G0 | This charter committed before any other change | Claude |
| G1 | `rulings.md` (Round 27 verbatim); `design.md`, `[PROPOSED]`: names, place, skills, thinness, the pin | Claude |
| G2 | The plugin and the marketplace file built; `claude plugin validate` on both; installed from the local marketplace in a scratch home; the command name confirmed; evals written and run; installation documented | Claude |
| G3 | `scripts/ci.py` green; pushed, CI green; head and land commands reported. **Stops for Emil. Not landed, no release cut** | Claude; **Emil** lands |

## Ids

This session files **no claim and no decision**. The prompt asks for Round 27 to be recorded and
the design proposed, not filed. Whether Round 27 becomes a decision is Emil's call (`findings.md`).
For the record, the highest decision file across all 59 `origin/*` branches at arrival was
`DDD-dec-118`.

**"Round 27" is ambiguous in this repository.** The 2026-11-07 session's `rulings.md` has its own
Round 27 ("flow time"). The demand-flow `rulings.md` already notes that the claude.ai
conversation's round numbers and that record's numbers overlap. Here, Round 27 always means the
claude.ai conversation's Round 27, cited together with this record.

## Read at arrival

- **Claude Code docs, fetched live on 2026-11-10** (HTTP 200 for all ten):
`plugins.md`, `plugins/create.md`, `plugins/components.md`, `plugins/manifest-reference.md`,
`plugin-marketplaces.md`, `plugins/marketplace-reference.md`, `plugins/host-marketplace.md`,
`skills.md`, `plugin-evals.md`, `plugins/security.md`. What was confirmed, and what differed
from the prompt's summary, is in `design.md` §1.
- **This repository at `v0.7.0`:** `method/README.md`, every step card (`01`, `01b`, `02` to `10`),
`method/quick-start.md`, `graph/upstream.yaml`, `releases/v0.7.0.yaml`, `README.md`,
`LICENSING.md`, `meta/sessions/README.md`, the demand-flow session's `rulings.md`
(Rounds 23 to 26; **Round 25 has landed**).

## Baseline

`python3 scripts/ci.py` on `84aa466` first failed the `what` and `how` gates. The cause was the
environment, not the repository: rdflib, pyoxigraph and pyld were not installed. After
`pip install -r scripts/requirements.txt`, the result was **all gates passed**.
Loading
Loading