Skip to content
Closed
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
68 changes: 68 additions & 0 deletions core/claims/DDD-address-06.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
format: 1
id: DDD-address-06
kind: conceptual
statement: |
The act map is the record of one ruled decomposition of work into acts under one declaration of ground axes, holding the act sites at their addresses, the composite acts that layer them, the causal dependencies between them and the index of the determinables that make demand arrive.
status: projected
region: |
Diachronic — it relates acts across occurrences, so it files here and not upstream
(DDD-dec-09's charter). One map per declaration of ground axes (DDD-address-07). Its four parts:

- Act sites. One site per address (DDD-ground-06): a ground position on the declared axes and
a layer path, with the occupant left out. Occurrences are not in the map. Each occurrence is
recorded against exactly one site, with its time index, in a record beside the map.
- Layers. Composite acts above an act and below it, and no other kind of layer (DDD-ground-06;
upstream core/09 §1, "acts nest as actors nest"). Containment is a tree under each top act,
and a top act is a composite act with none above it. A map may hold several top acts.
- Dependencies. Site B depends on site A when a state change an occurrence at A produced is
in the ground reading of an occurrence at B (DDD-address-01). A directed graph, not a tree.
It is acyclic over occurrences. Over sites it may loop.
- The index of determinables. Every determinable that makes demand arrive (DDD-frame-13), with
the act where it enters, the act where its determinate lands, whether governance has taken
it up — which makes it a decision anchored to acts (DDD-ground-01) — and its rate of change.

The map has no direction of its own beyond causal order. A view gives it one by naming a north,
a determinable from the index (DDD-address-08).
evidence: []
falsifier: |
An act site that must sit within two composite acts for its governing set to be stated, a dependency that can be stated between two occurrences and between no two sites, or a determinable that makes demand arrive and can be given no entry act on the map.
test: |
T2b, the first independent application case: its act map is built in the four parts, and each falsifier limb is searched for. The third limb also yields a finding when it fires — work the decomposition does not cover.
breaks: |
First limb: the layer path, and DDD-ground-06's exactly-one-address reading. Second limb: the split between the map and the occurrence record, and with it the lifecycle graph data (applications/pdlc/graph/, applications/sdlc/acts/). Third limb: that the map shows where demand comes from at all, and DDD-address-08 with it.
owner: none
changed: 2026-11-17, act map and process session (G2, on the G1 rulings; DDD-dec-122)
notes: |
Ruled by Emil, 2026-11-17 (DDD-dec-122; meta/sessions/2026-11-17-act-map-and-process/
rulings.md, E-2, R-3, R-6 and R-7 points 1 and 2).

Emil on the layers (E-2): "We have the layering its the acts at ground axes and then we have
composite acts below and above that - it can never be anything else." On the index (E-3): "we
must index the decisions not just the acts. without that index how can we see the pull". On
the rate (R-6): "time is the one that sets the change rate of a determinable which is what
creates the demand".

Prose that contradicts this claim, flagged and not harmonised:
- DDD-address-02's region calls the act map "a tree of occurrences", and
method/01-map-and-index-acts.md repeats it. This claim's nodes are act sites, and the tree is
containment. DDD-address-02's statement is untouched: every occurrence is still its own act.
The region is left as filed; whether it is superseded is open (successor item O-1).
- applications/sdlc/sdlc.md §10 says a second top act's acts "sit at the same addresses with a
different layer path". The layer path is part of the address (DDD-ground-06), so they can
share a ground position (DDD-address-04) and not an address (O-2).
- Four places name the SDLC's part of the lifecycle map "the act map" (O-3).

UNVERIFIED — Emil review:
- "Top act" is used in applications/sdlc/sdlc.md §3 and §10 and was not filed before this
claim. It is defined here as a position in the layering, not as a new kind.
- That occurrences sit outside the map rests on the lc: vocabulary (lc:Act, "an act site of
the map: one address, possibly many occurrences"; ruled by Round 28, R30) and on no claim.
- The index has not been built once. The lifecycle's six sources of pull
(applications/pdlc/graph/demand-flow.ttl) are the nearest thing: each names an entry act
and a discharge act, and none is marked taken up or not, or carries a rate.
- The rate of change has no unit and no measure. Owed demand recurs because an act upstream
failed, not because the world moved, and may need a rate of its own.
- Which method step builds the index is open (O-7).

Survey: meta/sessions/2026-11-17-act-map-and-process/survey.md lists every use of "act map" at
84aa466 (109 lines in 38 files) with what each implies.
52 changes: 52 additions & 0 deletions core/claims/DDD-address-07.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,52 @@
format: 1
id: DDD-address-07
kind: normative
statement: |
A second act map exists when, and only when, a second declaration of ground axes exists.
status: projected
region: |
Diachronic — a relation between records of acts (downstream per DDD-dec-09's charter). Two act
sites belong to one map exactly when their ground positions are read on the same declared
axes, under the same ruled decomposition (DDD-ground-06's region). It follows that:

- a further top act under the same declaration is a further tree in the same map;
- a part of a map, such as the acts within one composite act, is not a map;
- a view of a map (DDD-address-08) is not a map;
- the same work decomposed a second way gives one map at a time, because re-decomposition
supersedes (DDD-ground-06's region).

Between two maps one relation remains: an act in one reads state that an act in the other
produced. Coincidence (DDD-address-04) and applicability predicates (DDD-ground-01) range over
positions, and are not defined between two declarations.
evidence:
- kind: observation
ref: "meta/sessions/2026-11-17-act-map-and-process/survey.md, findings S-6 and S-7"
note: |
Three mapped cases in the repository, each with its own declaration: the dry run's T2a
(four axes), the quick start's Varve slice (three) and the product lifecycle (three,
DDD-dec-115). No map uses two declarations and no declaration serves two maps. The accepted
T2a map (DDD-dec-38) has three top acts under one declaration. An observation of how the
word has been used, written inside the framework: it does not test the rule.
falsifier: |
A governing decision whose applicability predicate must cover occurrences in two maps, or two occurrences in two maps whose behaviour must be compared to answer a question the work poses.
test: |
Utility, on the second application case: an organisation mapped beside the PDLC either shares the PDLC's declared axes or does not, and the rule holds if no governing decision and no behaviour comparison has to cross the boundary it draws.
breaks: |
Checking a map on its own (applications/pdlc/graph/check.py), the two grains of DDD-address-05, which assume one address space, and any tool that points from one map at acts in another.
owner: none
changed: 2026-11-17, act map and process session (G2, on the G1 rulings; DDD-dec-122)
notes: |
Ruled by Emil, 2026-11-17 (DDD-dec-122; rulings.md R-7, point 3). Filed as a normative claim,
as DDD-address-02 is: a governing choice about representation, tested by utility.

The alternative considered and not ruled: one map per top act. It matches "the SDLC's act
map" in four places, and fails on the accepted T2a map.

UNVERIFIED — Emil review:
- That the axis declaration is the boundary rested on no filed claim or ruling before this
one. It is this session's reading of survey finding S-6.
- Whether two pieces of work share a declaration is decided by whoever rules the
decomposition. Any two maps can be made one by declaring the union of their axes, and then
some acts never read some axes — the held T2b test item F-1 (act address landing, GATE 1
ruling 7). The rule says what a second map is and what it costs. It does not say when to
make one.
74 changes: 74 additions & 0 deletions core/claims/DDD-address-08.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,74 @@
format: 1
id: DDD-address-08
kind: normative
statement: |
A process is a human understanding of work, scoped within an area of expertise and not an object of the model, and its translation into the model is a named view of an act map fixed by one or more norths — unresolved determinables, where demand originates — and optionally bounded by composite acts.
status: projected
region: |
Wherever work that its holders call a process is mapped with the method. The view shows the
act sites on a dependency path (DDD-address-01) from each north's entry act to the act where
its determinate lands, inside the bound where one is given. It leaves out readings of earlier
occurrences, so rank from north is strict. Its parts:

- North. An unresolved determinable from the map's index (DDD-address-06): a cause. It exists
whether or not governance has taken it up (DDD-frame-13; upstream core/00 §4a). It is not a
decision and not an act. Time sets its rate of change, and that change is what creates
demand, so work that starts on a calendar has a north like any other.
- The other end. The act at which discharge produces the determinate (upstream core/09 §7a).
- The bound. None, one or more composite acts (DDD-ground-06). People name a process by where
the work happens and who holds it as well as by why it happens, and the model keeps those
apart: the first is composite acts, the second is norths.

A process is a saved view with a name. It is never a node of the map, and no decision is
anchored to it. A view is not a second act map (DDD-address-07). The translation may cross
composite acts.
evidence: []
falsifier: |
A view that the holders of a process do not recognise as their process, or a process whose holders can name no determinable it answers once the calendar is set aside.
test: |
Utility, on a second mapped case outside software: the holders of a process there are shown its view, and the claim fails on either limb. A process is settled inside one area of expertise, so the test is of use to its holders and not of fact.
breaks: |
Step 1b's use of "a process" as its unit (method/01b-map-the-flow-of-demand.md), and the promotion condition of DDD-flow-01 to DDD-flow-04 ("a second process"), which would have no defined subject.
owner: none
changed: 2026-11-17, act map and process session (G2, on the G1 rulings; DDD-dec-122)
notes: |
Ruled by Emil, 2026-11-17 (DDD-dec-122; rulings.md E-1, R-2, R-4, R-5, R-6 and R-7 point 4).

Emil on the process (R-4): "A process is a simple human understanding og work being done, it
is scoped and settled usually in a way that only makes sense within a given area of expertise.
Software, finance, hr etc. What we have is a much more complex model of the world and mapping
a process into our model is going to be hard. But I still think its the best translation of
the concept we have". On north (E-4): "North cant be a decision it must be where the demand
for decisions originate, so it is a cause."

Corrections recorded in rulings.md, with attribution:
- Claude first proposed "a process is a composite act". Withdrawn on E-2: the only name for a
layer is composite act.
- R-1 ruled north to be the discharge act of a declared demand kind. Superseded by R-2: north
is the unresolved determinable, and the discharge act is the other end.
- Claude then proposed north to be "a decision that must be made". Withdrawn on E-4: demand
is over determinables, and a decision is a determinable governance has taken up.
- Claude kept calendar-started work as a candidate process with no north. Withdrawn on E-5.

What this leaves as filed:
- DDD-dec-114's Round 9, "the SDLC is a subprocess under the PDLC", with its ruled reading, a
composite act within the PDLC. "Subprocess" is software's own word for its work. Nothing is
superseded. In this claim's terms the SDLC is a bound, with the norths whose determinates
land at its discharge act.
- The ruling made in Mantle's planning project on 2026-11-17, "a process is a composite act
that holds acts directly", is a view with a bound and no north: a case of this claim.
Whether Mantle keeps it is ruled there (O-9).

UNVERIFIED — Emil review:
- That a process may cross composite acts without the decomposition being wrong is Claude's
reading of R-4.
- Computed on the lifecycle map at 84aa466 (rulings.md, evidence): following dependencies
back from each demand kind's discharge act, honouring lc:forKind and leaving out
lc:readsEarlier, the chain ends at the kind's entry act (o0 for new, oC for owed, oG for
own-ground). New demand also declares oC as an entry act, and no dependency leads from oC
towards o16 for new demand (O-5). This was computed with the discharge act as north, before
R-2, and shows that the path between the two ends is well defined on that map, not that
the claim holds.
- That time is the cause of determination rests on E-5 and R-6 and on no filed claim. The
nearest text is the upstream holding note meta/holding-note-addendum-determinables.md, Q36,
which is not ratified.
97 changes: 97 additions & 0 deletions core/decisions/DDD-dec-122.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,97 @@
format: 1
id: DDD-dec-122
kind: decision
statement: |
The repository defines the act map, the rule for a second act map, and a process. The act map is the record of one ruled decomposition under one declaration of ground axes, holding act sites, the composite acts that layer them, their dependencies and the index of determinables (DDD-address-06). A second act map exists only with a second declaration of ground axes (DDD-address-07). A process is a human understanding of work and not an object of the model; its translation is a named view of an act map, fixed by one or more norths and optionally bounded by composite acts, where a north is an unresolved determinable (DDD-address-08). This adds to DDD-dec-114 and DDD-dec-118 and supersedes nothing.
principal: Emil
made: |
2026-11-17, in the claude.ai project conversation (verbatim in meta/sessions/2026-11-17-act-map-and-process/rulings.md), filed by the act map and process session the same day; Emil's landing of the branch is the ratification act
resolution: |
## The rulings (rulings.md, times Europe/Berlin)

- **E-2, 19:31. The layering is canon.** "We have the layering its the acts at ground axes and
then we have composite acts below and above that - it can never be anything else." Checked
against `DDD-ground-06` at `v5.15.2`.
- **R-1, 19:34. Superseded by R-2.** North is the discharge act of a declared demand kind.
- **R-2, 21:12. North.** North is the unresolved determinable, the source of pull. The
discharge act is the other end. Emil at 20:43: "North cant be a decision it must be where
the demand for decisions originate, so it is a cause."
- **R-3, 21:12. The index.** The index is an index of determinables, with decisions as the
ones governance took up. "Yes - that would build the index we need."
- **R-4, 21:12. A process.** "A process is a simple human understanding og work being done
[…] What we have is a much more complex model of the world and mapping a process into our
model is going to be hard. But I still think its the best translation of the concept we
have".
- **R-5, 21:19. The view.** A process translates to a named view with one or more norths,
optionally bounded by composite acts. In tooling it is a saved view, never a node. "agreed
on all".
- **R-6, 21:22. Time.** "time is the one that sets the change rate of a determinable which is
what creates the demand".
- **R-7, 21:25. G1 closed.** "i agree and accept on all seven points": (1) the map's nodes are
act sites, with occurrences recorded beside it; (2) the index of determinables is a part of
the act map, and each determinable carries its rate of change; (3) the rule for a second
map as written; (4) the process definition as amended, and a view leaves out earlier
readings; (5) one decision and three claims in the address area, with one cited sentence
each in `method/01` and `method/01b`; (6) definitions only in this session; (7) no issue
number on the commits.

## What is filed

- **`DDD-address-06`**, conceptual, projected: the act map.
- **`DDD-address-07`**, normative, projected: when a second act map exists.
- **`DDD-address-08`**, normative, projected: a process, and north.
- **Two pointers**: one sentence in `method/01-map-and-index-acts.md`, under the step card,
and one in `method/01b-map-the-flow-of-demand.md`, under "What the step does".

## What is not changed

- No act, no source of pull and no other lifecycle data (`applications/`). Out of scope by
the issue.
- No term in `core/graph/`, nothing in the `lc:` vocabulary, nothing upstream.
- `DDD-address-02`. Its region still says "a tree of occurrences". `DDD-address-06` flags the
difference in its notes and does not harmonise it.
- The step cards' registers. Step 1 stays ruled for test, step 1b stays `[PROPOSED]`.

## Relation to earlier decisions

- **Adds to `DDD-dec-114`.** Round 9's "the SDLC is a subprocess under the PDLC" keeps its
ruled reading, a composite act within the PDLC. In `DDD-address-08`'s terms the SDLC is a
bound.
- **Adds to `DDD-dec-118`.** Step 1b's unit, "a process", now has a filed definition. Its
sources of pull are norths. Its content stays `[PROPOSED]`.
- **Supersedes nothing.**
- **Release.** Not cut by this decision or this session.
basedOn:
- DDD-address-06
- DDD-address-07
- DDD-address-08
- DDD-address-01
- DDD-address-02
- DDD-address-04
- DDD-ground-06
- DDD-ground-01
- DDD-frame-13
- DDD-dec-114
- DDD-dec-118
- DDD-dec-38
notes: |
Id. Checked on every branch of both repositories at 15:40 UTC and again at 20:26 UTC,
2026-11-17. The highest decision file on main is DDD-dec-118; DDD-dec-119 is on PR #73's
branch, and DDD-dec-120 and -121 on PR #74's. Upstream's highest is DDD-dec-39. DDD-dec-122 and
DDD-address-06 to -08 appear only in this session's records.

No GitHub issue carries this work (R-7, point 7). The issue text is the session's prompt.md.

The ruling made in Mantle's planning project on 2026-11-17, "a process is a composite act that
holds acts directly", is not adopted as this repository's definition. DDD-address-08 reads it
as a view with a bound and no north. Whether Mantle keeps it is ruled there.

Not ruled, open for Emil (meta/sessions/2026-11-17-act-map-and-process/successor-items.md):
O-1 to O-9, among them building the lifecycle's index of determinables (O-6) and which method
step builds it (O-7).

Readings — Claude, UNVERIFIED — Emil review: marked in each claim's notes and in rulings.md.

Review trigger. A second mapped case, outside software: its act map either fits the four
parts of DDD-address-06 and the view of DDD-address-08 or does not, and the three claims are
reviewed with it.
Loading
Loading