Skip to content
Merged
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
7 changes: 7 additions & 0 deletions core/claims/DDD-address-02.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -21,3 +21,10 @@ notes: |
Emil's ruling R-6, 2026-09-27, in his words: "our choice to reuse the same act in the code is an
optimization not the truth." Filed as a normative claim: it is a governing choice about
representation, and its test is utility.

Appended 2026-11-18 (DDD-dec-122; G1-Q10, option 1, in
meta/sessions/2026-11-18-act-map-scope-and-pull/rulings.md). The region's "Governs the act map
(a tree of occurrences)" is superseded by DDD-address-06: the act map's nodes are act sites,
the tree is containment under each top act, and occurrences are recorded beside the map. The
region is not reworded. This claim's statement, falsifier, test and breaks stand: every
occurrence is still its own act.
78 changes: 78 additions & 0 deletions core/claims/DDD-address-06.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
format: 1
id: DDD-address-06
kind: conceptual
statement: |
The act map is the record of one ruled decomposition of the work inside one declared scope into acts, read under one declaration of ground axes, and it holds 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 in its scope.
status: projected
region: |
Diachronic — it relates acts across occurrences, so it files here and not upstream
(DDD-dec-09's charter). One map per scope and per declaration of ground axes (DDD-address-07).
Its parts:

- Scope. The map's first declaration: the decisions its holders take. Everything outside it
is world to the map, including other people's decisions. A decision outside reaches the map
only as ground crossing its edge (2026-11-18 R-2).
- 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 (DDD-address-01), 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). 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. One row per determinable at or inside the edge: its outcomes,
its entry act, the act where its determinate lands, its specified, observed and expected
states (DDD-address-11; actual is never read), its kind as a position on the map's declared
kind axis (DDD-address-10) and its rate of change. The observed state is a pointer to the
latest observation in the occurrence record, not a copy, so the map stays structure and the
record holds what changes. A row whose specified state cites a decision in force has been
taken up by governance inside the scope, which makes it a decision anchored to acts
(DDD-ground-01).

The map has no direction of its own beyond causal order. A view gives it one by naming a
north (DDD-address-08). It is central as an index every later artefact attaches to, not as a
container that holds them: each of method steps 2 to 10 attaches to a part of it or to a
record beside it (DDD-dec-122, S-1).
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, a determinable that makes demand arrive in the scope and can be given no entry act on the map, or a composite act that cannot be placed wholly inside or wholly outside the declared scope.
test: |
T2b, the first independent application case: its act map is built in the five parts, and each falsifier limb is searched for (registered again as T-1 in meta/sessions/2026-11-18-act-map-scope-and-pull/effects.md). 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 and -09 with it. Fourth limb: scope as a declaration made before any act is mapped, and the first part of step 1.
owner: none
changed: 2026-11-18, act map, scope and pull session (G2, on the G1 rulings; DDD-dec-122)
notes: |
History. First drafted on 2026-11-17 on a branch that did not land
(claude/act-map-and-process-2026-11-17; its commits are kept on claude/pull-and-scope-2026-11-18
at 47cf4cc), and amended on the rulings of 2026-11-18 (meta/sessions/2026-11-18-pull-and-scope/
rulings.md, R-8). The amendment adds the scope, the readable states and kind in the index, the
observed pointer and the fourth falsifier limb.

Ruled by Emil: 2026-11-17 E-2, R-3, R-6 and R-7 points 1 and 2
(meta/sessions/2026-11-17-act-map-and-process/rulings.md); 2026-11-18 R-1, R-2, R-4 and R-5;
G1-Q1 and G1-Q8 of meta/sessions/2026-11-18-act-map-scope-and-pull/rulings.md.

Emil on the layers (2026-11-17 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 scope
(2026-11-18 R-2): "scope must be the first else we cant place the pull, or we would end up far
far from our area of influence".

Prose that contradicts this claim, flagged and not harmonised:
- DDD-address-02's region calls the act map "a tree of occurrences". By G1-Q10, option 1, a
note appended to DDD-address-02 records that the phrase is superseded by this claim. The
region is not reworded.
- 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. Open, successor item O-2 of
2026-11-17.
- Four places name the SDLC's part of the lifecycle map "the act map" (O-3 of 2026-11-17).

UNVERIFIED — Emil review:
- "Top act" 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"; Round 28, R30) and on no other claim.
- The index has not been built once. Building the lifecycle's index is out of #80's scope.
- The rate of change has no unit and no measure (O-7 of 2026-11-17).
64 changes: 64 additions & 0 deletions core/claims/DDD-address-07.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,64 @@
format: 1
id: DDD-address-07
kind: normative
statement: |
A second act map exists when, and only when, a second declaration exists: a second scope, or a second declaration of ground axes.
status: projected
region: |
Diachronic — a relation between records of acts (downstream per DDD-dec-09's charter). Scope
says what is world. Axes say what is comparable (G1-Q2). Two act sites belong to one map
exactly when they are inside one declared scope and their positions are read on the same
declared axes, under one ruled decomposition (DDD-ground-06's region). It follows that:

- a further top act under the same scope and axes 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);
- a wider map may declare a narrower scope within it. A pull of the narrower scope then shows
in the wider map as a seam at that scope's edge. Where the wider map does not declare the
narrower scope, the pull shows there as a dependency only (2026-11-18 R-3).

The lifecycle (applications/pdlc/pdlc.md §11) is one map, with the PDLC as its scope and the
How declared within it. A map with the How alone as its scope would be a second map on the
same axes.

Between maps with different declarations of ground axes, coincidence (DDD-address-04) and
applicability predicates (DDD-ground-01) are not defined. One relation remains: an act in one
reads state that an act in the other produced.
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 of axes: 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: |
Between maps with different declarations of ground axes, a governing decision whose applicability predicate must cover occurrences in both, or two occurrences in the two maps whose behaviour must be compared to answer a question the work poses; between maps of nested scopes on the same axes, shared acts that carry different addresses in the two maps.
test: |
Utility, on the second application case: an organisation mapped beside the PDLC either shares the PDLC's scope and axes or does not, and the rule holds if no governing decision, no behaviour comparison and no shared act has to cross the boundary it draws in the way the falsifier names.
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 reading of one map that is then given two scopes.
owner: none
changed: 2026-11-18, act map, scope and pull session (G2, on the G1 rulings; DDD-dec-122)
notes: |
History. First drafted on 2026-11-17 on a branch that did not land
(claude/act-map-and-process-2026-11-17; kept on claude/pull-and-scope-2026-11-18 at 47cf4cc),
and amended on the rulings of 2026-11-18 (meta/sessions/2026-11-18-pull-and-scope/rulings.md,
R-8). The 2026-11-17 statement read "A second act map exists when, and only when, a second
declaration of ground axes exists" (2026-11-17 R-7 point 3). G1-Q2 supersedes that wording,
adding the scope (meta/sessions/2026-11-18-act-map-scope-and-pull/rulings.md).

Correction by Emil (C-1): the falsifier first proposed kept the 2026-11-17 limb for every pair
of maps. "As written, any PDLC decision covering an SDLC act fires it on day one." The limb now
holds only between different declarations of axes, and nested scopes have their own.

Filed as a normative claim, as DDD-address-02 is: a governing choice about representation,
tested by utility.

UNVERIFIED — Emil review: whether two pieces of work share a scope or a declaration is decided
by whoever rules the decomposition. Any two maps on the same axes can be made one by declaring
the union of their scopes. The rule says what a second map is and what it costs. It does not
say when to make one.
78 changes: 78 additions & 0 deletions core/claims/DDD-address-08.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,78 @@
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 one act map, fixed by one or more norths and optionally bounded by composite acts inside the map's scope, where a north is the determinable of a pull whether or not a gap is open on it now.
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, both inside the map's scope (DDD-address-06), and inside the bound where
one is given. It leaves out readings of earlier occurrences, so rank from north is strict. Its
parts:

- North. A determinable from the map's index: a cause, not a decision and not an act. It is
the determinable of a pull (DDD-address-09) whether or not a gap is open on it now, so a
process keeps its north between occurrences. The determinable is to the gap as the act site
is to the occurrence. It is a north whether or not governance inside the scope has taken it
up (DDD-frame-13; upstream core/00 §4a). A decision taken outside the scope is world to the
map. 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 inside the scope (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, or a process its holders recognise whose work answers no gap between any two states at any time.
test: |
Utility, on a second mapped case outside software: the holders of a process there are shown its view, and the claim fails on any 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), the promotion condition of DDD-flow-01 to DDD-flow-04 ("a second process"), which would have no defined subject, and under the third limb the identification of north with a pull's determinable.
owner: none
changed: 2026-11-18, act map, scope and pull session (G2, on the G1 rulings; DDD-dec-122)
notes: |
History. First drafted on 2026-11-17 on a branch that did not land
(claude/act-map-and-process-2026-11-17; kept on claude/pull-and-scope-2026-11-18 at 47cf4cc),
and amended on the rulings of 2026-11-18 (meta/sessions/2026-11-18-pull-and-scope/rulings.md,
R-8). The 2026-11-17 statement fixed the view by "unresolved determinables". The amendment
makes north the determinable of a pull, bounds the view inside the scope, and drops
"unresolved" as a condition.

Ruled by Emil: 2026-11-17 E-1, R-2, R-4, R-5, R-6 and R-7 point 4; 2026-11-18 R-2 and R-5;
G1-Q3 with correction C-2, and K-1 (meta/sessions/2026-11-18-act-map-scope-and-pull/
rulings.md).

K-1, ruled 2026-11-18 13:26: C-2 supersedes the wording of 2026-11-17 R-2 ("North is the
unresolved determinable") and of the matching line in issue #80's "ruled before" list ("North
is an unresolved determinable, where demand originates"), not their meaning. A north is a cause
and a determinable, as R-2 ruled. It rests on 2026-11-17 R-6: time sets a determinable's rate
of change, which is what creates demand.

Emil on the process (2026-11-17 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 (2026-11-17 E-4): "North cant be a decision it
must be where the demand for decisions originate, so it is a cause."

Corrections, recorded in the session rulings with attribution:
- Claude first proposed "a process is a composite act". Withdrawn on 2026-11-17 E-2.
- 2026-11-17 R-1 ruled north to be the discharge act of a declared demand kind. Superseded by
R-2: north is the determinable, and the discharge act is the other end.
- Claude proposed north to be "a decision that must be made". Withdrawn on 2026-11-17 E-4.
- Claude kept calendar-started work as a candidate process with no north. Withdrawn on E-5.
- Claude made "unresolved" a condition of north at G1 (P-3). Corrected by Emil (C-2).

What this leaves as filed: DDD-dec-114's Round 9 reading of the SDLC as a composite act within
the PDLC. In this claim's terms the SDLC is a bound, and in DDD-address-06's it may also be
declared a scope. 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. Whether Mantle
keeps it is ruled there (O-9 of 2026-11-17).

UNVERIFIED — Emil review: that a process may cross composite acts without the decomposition
being wrong is Claude's reading of 2026-11-17 R-4.
Loading
Loading