Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
25 commits
Select commit Hold shift + click to select a range
1de6540
Session applications-for-readers-redo: prompt and bootstrap
Hafeok Nov 10, 2026
25b73d0
rulings.md: Round 1, Emil's two rulings on PR #48, verbatim
Hafeok Nov 10, 2026
a8f5c45
Gate A: DDD-dec-94 re-filed on main; spec/doc-format.md ported from #48
Hafeok Nov 10, 2026
972f35a
rulings.md: Round 2, Emil's answers at Gate A, verbatim
Hafeok Nov 10, 2026
410f566
DDD-dec-119: the merge of #41 ratified the How's "not ruled separatel…
Hafeok Nov 10, 2026
153c6f2
DDD-dec-119: reaches how-vocabulary.md's banner too, under the same d…
Hafeok Nov 10, 2026
342b852
Gate B conventions: anchors kept, no splits, registers per document, …
Hafeok Nov 10, 2026
4a693b8
A-4 pre-registered: the human first-contact test, before any rewrite …
Hafeok Nov 10, 2026
47ac665
production-as-ground.md for readers: opener, register in words, basis…
Hafeok Nov 10, 2026
658d072
product-definition.md for readers: rulings D1.1 to D1.25 to the basis…
Hafeok Nov 10, 2026
1f3fb38
authority.md, its vocabulary and the test keys' README, for readers
Hafeok Nov 10, 2026
201140e
sdlc.md for readers: ruled, with its open items in words
Hafeok Nov 10, 2026
c029b39
what.md for readers: one document, numbering kept, 3.5's ruled title …
Hafeok Nov 10, 2026
b2ed229
pdlc.md and pdlc/README.md for readers
Hafeok Nov 10, 2026
f09f303
The four READMEs for readers; F-2: sdlc.md is ruled, not [PROPOSED]
Hafeok Nov 10, 2026
485353e
findings.md: Gate B, F-8 to F-12
Hafeok Nov 10, 2026
fdbc02a
how.md and how-vocabulary.md for readers: ruled, by DDD-dec-119
Hafeok Nov 10, 2026
670c525
DDD-dec-95 filed for the rewrite as done; spec/doc-format.md follows it
Hafeok Nov 10, 2026
9009500
Independent equivalence check: 89 points, each fixed or kept with its…
Hafeok Nov 10, 2026
733d40f
Session applications-for-readers-redo: report and the sessions index row
Hafeok Nov 10, 2026
3f2bba6
rulings.md: Round 3, Emil's message on PR #73, verbatim
Hafeok Nov 11, 2026
8c23588
DDD-dec-119's reach ruled (Round 3); F-13 closed
Hafeok Nov 11, 2026
5b4aa6d
DDD-dec-120: pdlc.md 2.1's seam rows 1 to 8 ruled as listed (Round 3)
Hafeok Nov 11, 2026
554adc8
rulings.md: Round 4, Emil's message on PR #73, verbatim
Hafeok Nov 11, 2026
118f2b3
DDD-dec-120 amended before landing: pdlc.md 2.1's rows 10 and 11 rule…
Hafeok Nov 11, 2026
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
64 changes: 55 additions & 9 deletions applications/README.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,58 @@
# applications/
# Applications — the framework applied to a kind of work

The framework denominated in a domain. Each application is a **projection** of the general principle,
not a restatement of it.
<!-- ddd:doc
reader: practitioners arriving in applications/, looking for the part that fits their work
act: find the application for their kind of work, how settled it is, and the first document to read in it
pin: v5.15.2
basis: [DDD-dec-94, DDD-dec-95, DDD-dec-114, DDD-dec-115, DDD-dec-119, DDD-dec-05, DDD-org-01@projected, DDD-org-02@projected, DDD-org-03@projected, DDD-org-04@projected]
status: current
supersedes: 84aa466:applications/README.md
-->

- **pdlc/** · the product lifecycle, ruled (Rounds 28 to 30; `DDD-dec-114`) — three owners: the What owner (what the product must do, everything the How needs, with product assurance), the When owner (the business: the order of all new demand and when each change reaches users), and the How owner (the SDLC, with implementation assurance and the order of owed and own-ground work). A pull system for new demand with an option pool, three kinds of demand, and responsibility placed per decision
- **sdlc/** · software delivery — the agentic/DAG design framework that was the whole of DDD through v3, now correctly positioned as one projection of the actor-general core. Within the PDLC, the SDLC is the How owner's arrangement and a composite act of the PDLC: every SDLC act's layer path begins PDLC ▸ SDLC ([`sdlc/sdlc.md`](sdlc/sdlc.md), `[PROPOSED]`, `DDD-dec-115`). The directories sit side by side, and the nesting is a relation in the act map, not a directory layout
- **organizations/** · organisation design as a directory of four claims, `DDD-org-01..04`, all projected
Each folder here applies Decision-Driven Design to one kind of work, in that work's own terms.
Start in the folder that matches yours.

*Conservation of Specification Demand* is what *Conservation of Determination Demand* is called when
the actor is building software. That relationship — general principle, domain projection — is the
structure the framework prescribes for itself.
**What an application is.** The framework denominated in a domain. Each application is a
**projection** of the general principle, not a restatement of it. *Conservation of Specification
Demand* is what *Conservation of Determination Demand* is called when the actor is building
software. That relationship, general principle and domain projection, is the structure the
framework prescribes for itself.

| Folder | What it is | How settled it is | Start with |
|---|---|---|---|
| [`pdlc/`](pdlc/) | The product lifecycle. Three owners: the What owner (what the product must do, everything the How needs, with product assurance), the When owner (the business: the order of all new demand, and when each change reaches users), and the How owner (the SDLC, with implementation assurance and the order of owed and own-ground work). A pull system for new demand with an option pool, three kinds of demand, and responsibility placed per decision | Ruled | [`pdlc/README.md`](pdlc/README.md) |
| [`sdlc/`](sdlc/) | Software delivery: the agentic/DAG design framework that was the whole of Decision-Driven Design through v3, now positioned as one projection of the actor-general core. Within the PDLC, the SDLC is the How owner's arrangement and a composite act of the PDLC: every SDLC act's layer path begins PDLC ▸ SDLC ([`sdlc/sdlc.md`](sdlc/sdlc.md)). The two directories sit side by side; the nesting is a relation in the act map, not a directory layout | The SDLC specification (`sdlc.md`) is ruled. The What, the How and the authority profile are ruled, each with the open points and unconfirmed readings it marks. See [`sdlc/README.md`](sdlc/README.md) for each document | [`sdlc/README.md`](sdlc/README.md) |
| [`organizations/`](organizations/) | Organisation design as a directory: four claims, and no documents of its own yet | All four claims are projected: predictions, not findings | [`organizations/README.md`](organizations/README.md) |

The repository presents the method as ready to try, not ready to use.

## How these documents are written

Every document here opens with who it is for, what you can do after reading it, and how settled it
is. Decided is the default and goes unmarked. A point that is proposed but not yet ruled is marked
*(proposed, not yet ruled)*, a point no one has settled is marked *(open)*, and a reading Emil has
not confirmed is marked *(Claude's reading, not yet confirmed by Emil)*. A document that has any
such point lists them near the end, under "Not settled yet".

Running text keeps decision, claim and promotion ids out. Every document closes with "Where this
comes from", which maps its sections to the decisions, claims and session records they rest on.
Reference material stays in its numbered section, because other files cite sections by number.
Deliberation stays in the session records.

**What these documents do not carry.** None of them is canon. Where a document and the decision
or claim it rests on disagree, the decision or claim governs, and the document is wrong.

## Where this comes from

| Section | Rests on |
|---|---|
| What an application is | The principle repository's canon, pinned in `graph/upstream.yaml` |
| `pdlc/`, ruled | `DDD-dec-114` (Rounds 28 to 30 of `meta/sessions/2026-11-07-sdlc-and-pdlc/`) |
| `sdlc/`: `sdlc.md` ruled | `DDD-dec-115`, S-11: Round 28 ruled the specification's proposals, and Round 30 entered by amendment. The earlier text of this page called `sdlc.md` `[PROPOSED]`; that was wrong (release session v0.7.0, finding F-2) |
| `sdlc/`: the What, the How, the authority profile | `DDD-dec-41`, `-42`, `-63`, `-64` (the What, ratified by the merge of #42); `DDD-dec-55` to `-61` and `DDD-dec-119` (the How); `DDD-dec-85`, `-86`, `-92`, `-93` (the authority profile, ratified by the merge of #45) |
| `organizations/` | `DDD-dec-05` (a directory, not a repository); `DDD-org-01` to `-04`, projected (`DDD-dec-40`) |
| Ready to try, not ready to use | `DDD-dec-74` |
| How these documents are written | `DDD-dec-94` and `spec/doc-format.md`; `DDD-dec-95` (this folder's format); the register phrases, Round 2 of `meta/sessions/2026-11-09-applications-for-readers-redo/` |
| What these documents do not carry | `DDD-dec-94` (only canon carries authority) |

The earlier text of this page is at `84aa466:applications/README.md`.
76 changes: 56 additions & 20 deletions applications/organizations/README.md
Original file line number Diff line number Diff line change
@@ -1,43 +1,79 @@
# applications/organizations/
# Organisation design — four predictions to test

Organisation design as a **directory**, not a repository (`DDD-dec-05`): four claims, no
documents of its own yet. Promotion to a repository requires core-like documents and an
identified external checker — not before.
<!-- ddd:doc
reader: people who design or run organisations, deciding whether the framework predicts anything about how theirs works
act: read the four organisation-design claims and the observation that would refute each, so they can test them
pin: v5.15.2
basis: [DDD-org-01@projected, DDD-org-02@projected, DDD-org-03@projected, DDD-org-04@projected, DDD-dec-05, DDD-dec-40]
status: current
supersedes: 84aa466:applications/organizations/README.md
-->

These are the organisation-design claims exactly as they stand in `core/claims/`
(`DDD-org-01..04`) — statements and falsifiers only, no new prose. All four are **projected**
and **session-authored** (flagged `UNVERIFIED — Emil review` in their claim files); they rest on
principle-layer claims pinned upstream in `graph/upstream.yaml`. Nothing here is canon.
Use this if you design or run an organisation and want to know what Decision-Driven Design
predicts about it. Organisation design is a **directory**, not a repository: four claims, and no
documents of its own yet. Promotion to a repository requires core-like documents and an identified
external checker, and not before.

## DDD-org-01 — graph discipline predicts organisational outcomes
**How settled this is.** All four claims are **projected**: predictions that have not been
tested, not findings. They were ratified as projected, and each was written in a session
(session-authored). They rest on principle-layer claims pinned upstream. Nothing here is canon.

*Status: projected.*
Below are the claims exactly as they stand in their claim files: each statement and its
falsifier, word for word, with no new prose.

## 1. Graph discipline predicts organisational outcomes

*Projected.*

> Graph discipline — status floors at the consumer boundary, manifests, correction flow to a single canon — predicts organisational outcomes: pivot cost, trust damage from shipping projected claims as established, decision-review latency after thesis change.

**Falsifier.** Organisations measurably differing in graph discipline show no difference in pivot cost or correction latency after size and sector controls.
**It is wrong if:**

## DDD-org-02 — statused Stable Dependency Principle
> Organisations measurably differing in graph discipline show no difference in pivot cost or correction latency after size and sector controls.

*Status: projected.*
## 2. The Stable Dependency Principle, with status

*Projected.*

> The Stable Dependency Principle, statused: decisions whose reversal cost exceeds what their basis claims' hazard can absorb (high commitment level on low-status claims) concentrate pivot cost and produce incident-discovered cascades; organisations cannot see these violations because their assumption layer carries no status field.

**Falsifier.** Decisions flagged by fragility (hazard × afferent decisions × reversal cost) generate no more rework or incident findings than unflagged decisions of equal size.
**It is wrong if:**

> Decisions flagged by fragility (hazard × afferent decisions × reversal cost) generate no more rework or incident findings than unflagged decisions of equal size.

## DDD-org-03 — priority as a governed decision
## 3. Priority as a governed decision

*Status: projected.*
*Projected.*

> Priority as a governed decision: backlogs ordered by decisions basedOn statused value-claims — with claim priority set by value of information and decision priority by cost of delay, reversal cost, and basis readiness — churn less and predict delivered value better than intuition-ordered backlogs; roadmap churn is the cascade from silently demoted value-claims.

**Falsifier.** Teams with statused value-claims and explicit basedOn priority show no less roadmap churn or no better value prediction than matched intuition-ordered teams; or churn events do not trace to value-claim status changes on audit.
**It is wrong if:**

## DDD-org-04 — cross-domain retrodiction of institutional discipline
> Teams with statused value-claims and explicit basedOn priority show no less roadmap churn or no better value prediction than matched intuition-ordered teams; or churn events do not trace to value-claim status changes on audit.

*Status: projected.*
## 4. Institutional discipline across industries, retrodicted

*Projected.*

> Cross-domain retrodiction: the intensity of an industry's institutionalised graph discipline — permits, licensure, stage-gates, mandatory inspection — is predicted by reversal cost and feedback latency. Construction and manufacturing evolved formal status floors because irreversibility forced them; software's informality is explained by cheap retries, and its formalisation pressure rises with consequence and with agent-generated code collapsing generation cost while verification cost stands.

**Falsifier.** Industries matched on reversal cost and feedback latency showing grossly different discipline intensity, or discipline intensity tracking regulation-historical accident better than the two parameters after controls.
**It is wrong if:**

> Industries matched on reversal cost and feedback latency showing grossly different discipline intensity, or discipline intensity tracking regulation-historical accident better than the two parameters after controls.

## Where this comes from

| Section | Rests on |
|---|---|
| A directory, not a repository; the promotion criterion | `DDD-dec-05` |
| How settled this is | `DDD-dec-40` (2026-10-26): each claim ratified as projected, its claim file its exposition. Each claim file's notes say "Session-authored" |
| 1 | `core/claims/DDD-org-01.yaml` |
| 2 | `core/claims/DDD-org-02.yaml` (credit: Martin's Stable Dependency Principle) |
| 3 | `core/claims/DDD-org-03.yaml` (credits: Reinertsen; Bezos's Type 1/Type 2 doors) |
| 4 | `core/claims/DDD-org-04.yaml` |
| Rests on principle-layer claims | `graph/upstream.yaml` |

The earlier text of this page said the claims were "flagged `UNVERIFIED — Emil review` in their
claim files". They are not: `DDD-dec-40` ratified all four as projected on 2026-10-26, and the
claim files carry no such flag. The earlier text is at
`84aa466:applications/organizations/README.md`.
60 changes: 42 additions & 18 deletions applications/pdlc/README.md
Original file line number Diff line number Diff line change
@@ -1,39 +1,63 @@
# The PDLC Projection

<!-- ddd:doc
reader: anyone setting up or joining a product's lifecycle: product, business and engineering leads
act: find the PDLC's specification and graph, and see where the What, the SDLC and the authority over a product live
pin: v5.15.2
basis: [DDD-dec-114, DDD-dec-115, DDD-dec-42]
status: current
supersedes: 84aa466:applications/pdlc/README.md
-->

**The product lifecycle.** The PDLC places responsibility for a product among three owners:
- the **What owner** holds what the product must do: everything the How needs in order to
implement, including product assurance (how sure we can be that users do the act we designed)
and its observability needs (Rounds 17–19);
and its observability needs;
- the **When owner**, the business and go-to-market, holds the order of all new demand and when
each change reaches users (Round 22);
each change reaches users;
- the **How owner** holds the SDLC, the process of getting approved changes to production, with
implementation assurance, the order of owed and own-ground work, and the DORA keys as its
answerability (Rounds 19, 20, 22).
answerability.

The SDLC is a composite act within the PDLC (`DDD-dec-114`, Rounds 8 and 9).
The SDLC is a composite act within the PDLC.

**Register: ruled (Rounds 28 to 30).** `DDD-dec-114` files the rulings.
Claude's construction in this directory was ruled item by item in Round 28 (R1 to R30), with the forecast settled in Rounds 29 and 30.
**How settled this is.** Decided. The construction in this directory was ruled item by item, and
the forecast was settled afterwards. Nothing here has run on a real product yet.

| Document | What it is |
|---|---|
| **[pdlc](pdlc.md)** · ruled (Rounds 28 to 30) | The PDLC: the stance (delivery does not decide when), the three owners, the What owner's output (everything the How needs), the two assurances (product and implementation), evidence in use and observation needs, the placement rule, the four loci, priority as a When decision, the three kinds of demand and their sources of pull, the option pool for new demand, ready for users and toggles, the seam to the SDLC, falsifiers and open items |
| **[graph/](graph/)** · ruled (Round 28, R30) | `lc:`, the lifecycle vocabulary (`ontology.ttl`); its shapes (`shapes.ttl`); the PDLC's acts on the act map (`acts.ttl`); an illustrative option pool (`example-pool.ttl`); and `check.py`, which validates the whole act map, PDLC and SDLC, with planted defects |
| **[pdlc](pdlc.md)** · decided | The PDLC: the stance (delivery does not decide when), the three owners, the What owner's output (everything the How needs), the two assurances (product and implementation), evidence in use and observation needs, the placement rule, the four loci, priority as a When decision, the three kinds of demand and their sources of pull, the option pool for new demand, ready for users and toggles, the seam to the SDLC, falsifiers and open items |
| **[graph/](graph/)** · decided | `lc:`, the lifecycle vocabulary (`ontology.ttl`); its shapes (`shapes.ttl`); the PDLC's acts on the act map (`acts.ttl`); an illustrative option pool (`example-pool.ttl`); and `check.py`, which validates the whole act map, PDLC and SDLC, with planted defects |

## Where things live

- **The What** stays in [`../sdlc/what.md`](../sdlc/what.md), where `DDD-dec-42` placed it. It is
**owned here**, by the What owner, and read by the SDLC as ground (Round 8: "Stays, read as
ground").
- **The SDLC** is in [`../sdlc/sdlc.md`](../sdlc/sdlc.md) (`DDD-dec-115`). It sits beside this
directory, not inside it. The nesting is a relation in the act map (every SDLC act's layer path
begins PDLC ▸ SDLC), not a directory layout. Whether the directory should one day nest is open
(`pdlc.md` §13, O-1).
- **The What** stays in [`../sdlc/what.md`](../sdlc/what.md), where it was placed. It is
**owned here**, by the What owner, and read by the SDLC as ground.
- **The SDLC** is in [`../sdlc/sdlc.md`](../sdlc/sdlc.md). It sits beside this directory, not
inside it. The nesting is a relation in the act map (every SDLC act's layer path begins
PDLC ▸ SDLC), not a directory layout. Whether the directory should nest has been decided
for now: it does not (`pdlc.md` §15, O-1).
- **The authority** over a product, the genesis grant and the scopes the three owners hold, is
the authority profile, [`../sdlc/authority.md`](../sdlc/authority.md) §2–3.

**Not Delivery.** The PDLC is not the Product Framework's Delivery revived; `DDD-dec-42` O-2
retired that. It carries no releases, versions or timeline as artefacts. Ordering and delivery
are recorded decisions, and forecasts are computed from the SDLC's record.
**Not Delivery.** The PDLC is not the Product Framework's Delivery revived; that was retired
when the What moved into `applications/sdlc/`. It carries no releases, versions or timeline as artefacts. Ordering and
delivery are recorded decisions, and forecasts are computed from the SDLC's record.

Run: `python3 applications/pdlc/graph/check.py` and `python3 applications/sdlc/acts/check.py`.

## Where this comes from

| Part | Rests on |
|---|---|
| The three owners | `DDD-dec-114`: What owner, Rounds 17–19; When owner, Round 22; How owner, Rounds 19, 20, 22 |
| The SDLC as a composite act | `DDD-dec-114`, Rounds 8 and 9 |
| How settled | Rounds 28 to 30: Round 28 ruled Claude's construction item by item (R1 to R30); Rounds 29 and 30 settled the forecast. `graph/` was ruled by Round 28, R30 |
| The What's place | `DDD-dec-42`; Round 8 ("Stays, read as ground") |
| The SDLC's place | `DDD-dec-115`; O-1, closed by Round 28, R9 |
| Not Delivery | `DDD-dec-42` O-2 |

The rulings are verbatim in
[`meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md`](../../meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md).
Supersedes `84aa466:applications/pdlc/README.md`, rewritten for readers by
`meta/sessions/2026-11-09-applications-for-readers-redo/`; no rule changed.
Loading
Loading