diff --git a/core/claims/DDD-address-06.yaml b/core/claims/DDD-address-06.yaml new file mode 100644 index 0000000..4168c50 --- /dev/null +++ b/core/claims/DDD-address-06.yaml @@ -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. diff --git a/core/claims/DDD-address-07.yaml b/core/claims/DDD-address-07.yaml new file mode 100644 index 0000000..8a01dbd --- /dev/null +++ b/core/claims/DDD-address-07.yaml @@ -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. diff --git a/core/claims/DDD-address-08.yaml b/core/claims/DDD-address-08.yaml new file mode 100644 index 0000000..82d461c --- /dev/null +++ b/core/claims/DDD-address-08.yaml @@ -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. diff --git a/core/decisions/DDD-dec-122.yaml b/core/decisions/DDD-dec-122.yaml new file mode 100644 index 0000000..63c63c6 --- /dev/null +++ b/core/decisions/DDD-dec-122.yaml @@ -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. diff --git a/meta/sessions/2026-11-17-act-map-and-process/bootstrap.md b/meta/sessions/2026-11-17-act-map-and-process/bootstrap.md new file mode 100644 index 0000000..3a6e349 --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/bootstrap.md @@ -0,0 +1,54 @@ +# Bootstrap — the act map and a process, 2026-11-17 + +| Parameter | Value | +|---|---| +| Invocation | Interactive. Emil gave the issue text as one message in the claude.ai project conversation. `prompt.md` carries it verbatim | +| Principal | Emil (sole ratifier; ratifies by landing the branch) | +| Issue | None found on GitHub at arrival. The newest issue is #77, and none carries this title. The issue text exists only in the conversation and in `prompt.md`. Commits carry no `Refs` line until Emil names a number | +| Upstream repo | github.com/mindovermachine-dev/actor-indexed-determination, read only, at tag `v5.15.2` (`084bce7`) | +| Upstream pin | `v5.15.2` (`graph/upstream.yaml`, line 133), unchanged by this session | +| Downstream repo | github.com/mindovermachine-dev/decision-driven-design | +| Downstream base | `84aa466`, head of `main` at arrival | +| Downstream branch | `claude/act-map-and-process-2026-11-17` | +| Parallel work | PR #73 (`claude/zealous-ptolemy-3txf8k`, `applications/` for readers, `DDD-dec-94`, `-95`, `-119`) and PR #74 (`claude/confident-goldberg-c0y0ia`, the method plugin, `DDD-dec-121`). Both are open and unlanded. #73 rewrites prose under `applications/`, where this session's survey reads line numbers | +| Model | Claude Fable 5.2 | + +## Gates + +| Gate | What | Who | +|---|---|---| +| G0 | This charter committed before any other change | Claude | +| G1 | Deliverables 1 and 2: `survey.md` and `proposals.md`. Nothing is filed | Claude; **stops for Emil**, who rules each definition and where it is filed | +| G2 | Deliverable 3: the definitions filed as ruled; `python3 scripts/ci.py` passes; pushed | Claude; **stops for Emil** | +| Merge | Land the branch | **Emil** | + +## Scope at arrival + +In scope: the survey, the proposals, and after G1 the filings Emil rules. + +Out of scope, from the issue: changing any act; new processes such as budget or employment; Mantle; canon in the principle repository. + +## Decision ids + +Checked across every branch of both repositories at arrival (2026-11-17, 15:40 UTC). + +- **Upstream** (27 remote branches): the highest decision id is `DDD-dec-39`. +- **Downstream** (every `origin/*` branch): the highest decision file on `main` is `DDD-dec-118`. `DDD-dec-119` is on PR #73's branch. `DDD-dec-120` and `DDD-dec-121` are on PR #74's branch. No branch mentions an id above `DDD-dec-121`. + +The next free decision id is **`DDD-dec-122`**. Nothing is filed before G1. + +The highest claim id in the address area is `DDD-address-05`. + +## Deviations at arrival + +- **Reading before the charter.** The ground files were read, and the search for "act map" was run, before this charter was committed. Nothing was written. Recorded here because the convention puts the charter first. +- **Project instructions are stale on the head.** They name `main` at `4004b49`. `main` is at `84aa466`. The upstream pin they name, `v5.15.2`, is still the pin. + +## Read at arrival + +- `AGENTS.md`; `meta/way-of-working.md`; `meta/sessions/README.md`. +- `method/01-map-and-index-acts.md`; `method/quick-start.md` §3 and §4; `method/01b-map-the-flow-of-demand.md` (the lines that name the act map or a process). +- `core/claims/DDD-address-01.yaml`, `-02`, `-04`; `core/decisions/DDD-dec-114.yaml`, `-118`. +- `applications/pdlc/pdlc.md` §11 and §13; `applications/sdlc/sdlc.md` §3 and §10; `applications/pdlc/graph/ontology.ttl`, `shapes.ttl`, `acts.ttl`; `applications/sdlc/acts/acts.ttl`. +- `meta/sessions/2026-09-27-act-address/` (`rulings.md`, `prereg-act-coordinates.md`, `results-act-address-dry-run.md`). +- Upstream at `v5.15.2`: `core/claims/DDD-ground-06.yaml`; `term:act` and `term:act-address` in `core/graph/terms.yaml`; `core/14-indexed-determination.md` §5. diff --git a/meta/sessions/2026-11-17-act-map-and-process/predictions.md b/meta/sessions/2026-11-17-act-map-and-process/predictions.md new file mode 100644 index 0000000..76dc2cc --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/predictions.md @@ -0,0 +1,28 @@ +# Predictions — the act map and a process, 2026-11-17 + +Written before each operation is run. Results are recorded against each prediction. + +## P-1 — the survey + +Not a prediction. The search for "act map" ran before the charter was committed (`bootstrap.md`, deviations). Its result could not be predicted afterwards, so none is claimed. + +**Result:** 109 lines in 38 files. See `survey.md`. + +## P-2 — the full gate at G1 + +`python3 scripts/ci.py` passes on this branch at G1. The branch adds session records only. It changes no claim, no decision, no What or How file and no fixture. Two environment failures are likely before any gate reads a file, as in `2026-11-08-specification-feasibility/predictions.md` P-2: `ssh-keygen` missing, and the shallow clone hiding release tags. + +**Result:** held, with one of the two environment failures. The first run failed at `preflight`: `ssh-keygen` was not on PATH. Installed (`openssh-client`). Tags were fetched before the run (`git fetch --force --tags origin`), so the releases gate was not seen to fail. The second run passed every gate (exit 0). + +## P-3 — the full gate at G2 + +Written at 21:27 (Europe/Berlin), after R-7 and before any filing. + +Filed: `core/claims/DDD-address-06.yaml`, `-07`, `-08`; `core/decisions/DDD-dec-122.yaml`; one sentence in `method/01-map-and-index-acts.md` and one in `method/01b-map-the-flow-of-demand.md`. + +1. `python3 scripts/validate-claims.py core/claims/` passes. It may warn on rule 1 for `DDD-address-06` and `-08`, whose statements list parts. A warning is not an error (`spec/claim-format.md` §4). +2. `python3 scripts/validate-claims.py core/decisions/ --decisions` passes. Every id in `DDD-dec-122`'s `basedOn` exists here or is pinned in `graph/upstream.yaml` (`DDD-ground-06` and `DDD-frame-13` are). +3. `python3 scripts/ci.py` passes. No pin moves, no release descriptor is added, and no What, How or lifecycle file is touched. +4. The ids are free. Re-checked at 21:26 on every branch of both repositories: `DDD-dec-122` and `DDD-address-06` to `-08` appear only in this session's own records. + +**Result:** held, with one miss on the cautious side. (1) Passed, and no rule 1 warning fired on the three new claims: the six warnings are on claims this session did not touch. (2) Passed: 97 decisions. (3) Passed: every gate, exit 0, after the session index row was added. (4) Held. diff --git a/meta/sessions/2026-11-17-act-map-and-process/prompt.md b/meta/sessions/2026-11-17-act-map-and-process/prompt.md new file mode 100644 index 0000000..6078a84 --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/prompt.md @@ -0,0 +1,21 @@ +# The repository says what an act map is, when there is more than one, and what a process is + +The issue, verbatim, as Emil gave it in the claude.ai project conversation on 2026-11-17 at 16:27 (Europe/Berlin). + +> The repository says what an act map is, when there is more than one, and what a process is +> +> Outcome. One filed definition each of the act map and of a process, and a stated rule for when a second act map exists. +> +> Ground. `AGENTS.md`. `meta/way-of-working.md`. `method/01-map-and-index-acts.md`. `core/claims/DDD-address-01.yaml` and `DDD-address-02.yaml`. `applications/pdlc/pdlc.md` §11. `applications/sdlc/sdlc.md`. `applications/pdlc/graph/ontology.ttl`. Canon at the tag in `graph/upstream.yaml`. +> +> Ruled before this issue was opened, 2026-11-17, in Mantle’s planning project: for Mantle’s view, a process is a composite act that holds acts directly. Whether this repository adopts that is ruled here. +> +> Deliverable. +> +> 1. Every use of “act map” in the repository, with what each implies: one or many, tree or graph. Exit: the list names each file and line. +> 2. Proposed definitions, each with a falsifier and what it breaks: the act map; when a second one exists; a process. Exit: each says which filed claim or ruling it rests on, or that it rests on none. +> 3. On the rulings, the definitions are filed where the session proposed and the principal ruled. Exit: `python3 scripts/ci.py` passes. +> +> Gates. G1 after step 2: the principal rules each definition and where it is filed. G2 after step 3. Then the merge. +> +> Out of scope. Changing any act. New processes such as budget or employment. Mantle. Canon in the principle repository. diff --git a/meta/sessions/2026-11-17-act-map-and-process/proposals-2.md b/meta/sessions/2026-11-17-act-map-and-process/proposals-2.md new file mode 100644 index 0000000..303729f --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/proposals-2.md @@ -0,0 +1,161 @@ +# Proposals, second form — after R-2, R-3 and R-4 + +The three definitions as they stand after Emil's rulings of 2026-11-17. This file supersedes `proposals.md`, which is kept as written. Nothing here is filed. + +| # | Definition | Ruled so far | Still to rule | +|---|---|---|---| +| D-1 | **The act map** is the record of one ruled decomposition under one declaration of ground axes. It holds act sites, the composite acts above and below them, the dependencies between them, and the index of determinables | Layers are composite acts and nothing else (E-2). The index is of determinables (R-3) | Nodes are sites. "Top act". Whether the index is part of the map | +| D-2 | **A second act map** exists when, and only when, a second declaration of ground axes exists | Nothing | The whole rule | +| D-3 | **A process** is a human understanding of work, scoped to an area of expertise. Its translation into the model is a view of an act map: the acts between one unresolved determinable and the determinate that discharge produces | North is the unresolved determinable; the discharge act is the other end (R-2). A process is a human concept, and this is its best translation (R-4) | The wording. Whether the view leaves out earlier readings | + +Arguments below that Emil has not confirmed are `UNVERIFIED — Emil review`. + +## D-1 — the act map + +**Definition.** The act map is the record of one ruled decomposition of work into acts, read under one declaration of ground axes. It holds four things: + +| Part | What it is | Source | +|---|---|---| +| Act sites | One site per address: a ground position on the declared axes and a layer path. The occupant is not part of it | `DDD-ground-06` | +| Layers | Composite acts above an act and below it. There is no other kind of layer. A top act is a composite act with none above it | `DDD-ground-06`; `core/09` §1; E-2 | +| 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. A directed graph | `DDD-address-01` | +| The index of determinables | Every determinable that makes demand arrive, with the act where it enters and the act where its determinate lands. Each is marked taken up, which makes it a decision anchored to acts, or not taken up, which makes it a candidate escape | `DDD-frame-13`; `core/00` §4a; R-3 | + +The map has no direction of its own beyond causal order. A view gives it one by naming a north: one determinable from the index (E-1, R-2). + +Occurrences are not in the map. Each is recorded against one site, with its time index. + +**Weakest point.** Two, of different kinds. +1. `DDD-address-02`'s region says "a tree of occurrences". This says the nodes are sites. Unchanged from `proposals.md`. +2. The index is new, and nothing in the repository has one. The lifecycle's six sources of pull are the nearest thing: each names an entry act and a discharge act, and none is marked taken up or not. So the fourth part is defined before it has been built once. + +**Rests on.** `DDD-ground-06`, `DDD-address-01`, `DDD-address-02`, `DDD-frame-13` (all projected); `core/00` §4a; the `lc:` vocabulary (Round 28, R30); E-2 and R-3 of this session. "Top act" and "occurrences sit outside the map" rest on **no claim**. + +**Falsifier.** Any of: +1. An act site that must sit within two composite acts for its governing set to be stated. +2. A dependency that can be stated between two occurrences and between no two sites. +3. A determinable that makes demand arrive and that cannot be given an entry act on the map. This limb also yields a finding: work the decomposition does not cover. + +**What it breaks.** Limb 1: the layer path and `DDD-ground-06`'s "exactly one address". Limb 2: the split between map and occurrence record. Limb 3: the claim that the map shows the pull at all. + +## D-2 — when a second act map exists + +Unchanged from `proposals.md`, and not yet ruled. + +**Rule.** A second act map exists when, and only when, a second declaration of ground axes exists. A second top act under the same declaration is a second tree in the same map. A view is not a second map. + +**Weakest point.** Whether two pieces of work share a declaration is the mapper's decision. The rule names it and does not make it. + +**Rests on.** `DDD-ground-06`'s region; `DDD-address-04`; the accepted T2a map (`DDD-dec-38`), which has three roots under one declaration. That the declaration is the boundary rests on **no filed claim or ruling**. + +**Falsifier.** A governing decision whose applicability predicate must cover occurrences in two maps, or two occurrences in two maps whose behaviour must be compared. + +**What it breaks.** Checking a map on its own, and the two grains of `DDD-address-05`. + +## D-3 — a process + +**Definition.** A process is a human understanding of work being done. It is scoped and settled within an area of expertise, such as software, finance or HR. It is not an object of the model. + +Its translation into the model is a view of an act map, fixed by one north: + +| Part of the view | What it is | Source | +|---|---|---| +| North | One unresolved determinable: the cause, where demand originates. It exists whether or not anyone has taken it up | `DDD-frame-13`; `core/00` §4a; R-2 | +| The other end | The act at which discharge produces the determinate | `core/09` §7a; R-2 | +| The acts shown | The act sites on a dependency path from the determinable's entry act to that discharge act | `DDD-address-01` | +| Rank | Distance from north along dependencies | E-1 | + +The translation is the passage from determinable to determinate (`core/00` §4a), read over a chain of acts. It may cross composite acts. + +**Weakest point.** A process is settled inside one area of expertise, so there is no fact against which the translation can be wrong. It can only be more or less useful to the people who hold the process. The falsifier below is therefore a test of utility, as `DDD-address-02`'s is, and weaker than a test of fact. + +**What this settles without a new ruling.** +- **Round 9.** "The SDLC is a subprocess under the PDLC" is software's own word for its work. Its ruled reading in the model, a composite act within the PDLC, stands (`DDD-dec-114`). Nothing is superseded. +- **The lifecycle.** The six sources of pull are six norths. The SDLC is a composite act that several views pass through. +- **Mantle.** "A composite act that holds acts directly" is another translation of the same human concept, made for display. Whether Mantle keeps it is ruled in Mantle's project. + +**Rests on.** R-2 and R-4 of this session; `DDD-frame-13`; `core/00` §4a; `core/09` §7a; `DDD-address-01`. "Process" has no filed term, here or upstream. + +**Falsifier.** Either: +1. A process its holders recognise that has no north: no determinable in the world starts it. Work that starts only because an earlier decision scheduled it is the candidate. The holding note `meta/holding-note-addendum-determinables.md` Q36 (upstream, not ratified) calls that ledger-pull. +2. A view that the holders of the process do not recognise as their process, in a second mapped case. + +**What it breaks.** Step 1b's use of "a process" as its unit, and the promotion condition of `DDD-flow-01` to `-04` ("a second process"). + +## Where to file — proposed, not ruled + +| What | Where | Form | +|---|---|---| +| The rulings of this session | `core/decisions/DDD-dec-122.yaml` | One decision. `basedOn` the claims below, `DDD-ground-06`, `DDD-frame-13`, `DDD-address-01`, `DDD-dec-114`, `-38` | +| D-1, the act map | `core/claims/DDD-address-06.yaml` | Conceptual, projected. Test: T2b | +| D-2, a second act map | `core/claims/DDD-address-07.yaml` | Normative, projected | +| D-3, a process | `core/claims/DDD-address-08.yaml` | Normative, projected | +| Pointers | `method/01-map-and-index-acts.md`, "Artefact out"; `method/01b-map-the-flow-of-demand.md`, first use of "process" | One cited sentence each | + +Not proposed: the term registry, the `lc:` vocabulary, upstream, and any change to the lifecycle's acts or sources of pull. + +## What the rulings would leave open + +| # | Item | +|---|---| +| O-1 | `DDD-address-02`'s region says "a tree of occurrences" | +| O-2 | `sdlc.md` §10: the second top act has no graph data, and one sentence contradicts `DDD-ground-06` (S-8, S-9) | +| O-3 | Four places call the SDLC's part "the act map" (S-10) | +| O-4 | The o5 and o6 loop is left out of the data (S-4) | +| O-5 | New demand declares oC as an entry act, and no dependency leads from oC towards o16 for new demand (`rulings.md`, evidence) | +| O-6 | The lifecycle has no index of determinables. Its six sources of pull are not marked taken up or not. Building the index changes the lifecycle data, which this issue puts out of scope | +| O-7 | Which step builds the index: step 1, or step 3, which is not filed | +| O-8 | PR #73 rewrites prose under `applications/`. The survey's line numbers are `main`'s at `84aa466` | +| O-9 | Carry R-2 and R-4 to Mantle's planning project | + +## For G1 + +1. D-1: are the map's nodes act sites, with occurrences recorded beside it? +2. D-1: is the index of determinables a part of the act map? +3. D-2: is the rule ruled as written? +4. D-3: is the wording ruled as written? Does a view leave out earlier readings (`lc:readsEarlier`), so that rank is strict? +5. Filing: one decision and three claims in the address area? +6. Scope: definitions only in this session, with O-6 and O-7 as new issues? +7. Is there a GitHub issue number for the commits? + +## Amendments + +Added after the file was first committed. The sections above are left as written. + +### A-1 — D-3 after R-5 and E-5 + +**Definition, as amended.** A process is a human understanding of work being done, scoped and settled within an area of expertise. It is not an object of the model. Its translation into the model is a **named view** of an act map, fixed by: + +| Part | What it is | How many | +|---|---|---| +| Norths | Unresolved determinables: the causes the work answers | One or more | +| Bound | Composite acts the view is limited to | None, one or more | + +The view shows the act sites on a dependency path from each north's entry act to the act where its determinate lands, inside the bound where one is given. + +**Why two parts.** People name a process by where the work happens and who holds it, and by why it happens. The model keeps those apart: the first is composite acts, the second is norths. The SDLC is a bound with the norths that end at its discharge act. The PDLC is one bound with six norths. + +**In tooling.** A process is a saved view with a name. It is never a node, so no decision can be anchored to it. + +**Falsifier, as amended.** Limb 1 of D-3 ("a process with no north", with calendar-started work as the candidate) is withdrawn on E-5: time makes a determinable unresolved again, so calendar-started work has a north. What remains: + +1. A view that the holders of the process do not recognise as their process, in a second mapped case. +2. A process whose holders cannot name any determinable it answers, after the calendar is set aside. + +**Weakest point, added.** If time is the cause of every determination, then "time" cannot tell one north from another. What tells them apart is which determinable time moves, and how fast. So north stays the determinable, and a north's rate of change is a property the index may need. Nothing filed says so. + +**Rests on.** R-2, R-4, R-5 and E-5 of this session; `DDD-frame-13`; `core/00` §4a; `DDD-address-01`; `DDD-ground-06` for the bound. + +**Effect on Mantle.** "A composite act that holds acts directly" is a view with a bound and no north. It is a case of this definition, not a rival to it. Whether Mantle keeps it is ruled there (O-9). + +### A-2 — D-1 after R-6 + +**The index of determinables, as amended.** Each determinable in the index carries a fourth property beside its entry act, its discharge act and whether it is taken up: its **rate of change**, the rate at which time makes it unresolved again. That rate is what creates demand (R-6). + +**What it gives.** A north's rate of change says how often the work recurs. The lifecycle writes this on acts, as free text (`lc:recurs "per issue"`, `"per event"`). On R-6 it is a property of the cause first, and the acts inherit it. + +**Weakest point.** No filed claim carries a rate of change for a determinable. The method's step 4, which is `[PROPOSED]` and not filed, speaks of declaring ground with its tick rate. So this property is defined here before it has a unit or a way to measure it. + +**Falsifier.** A determinable whose demand recurs at a rate that its own rate of change does not explain, for example work that recurs because an act upstream failed and not because the world moved. That is owed demand in the lifecycle, and it may need a rate of its own. + +**Rests on.** R-6 and E-5 of this session; `DDD-frame-13`. On no filed claim for the rate itself. diff --git a/meta/sessions/2026-11-17-act-map-and-process/proposals.md b/meta/sessions/2026-11-17-act-map-and-process/proposals.md new file mode 100644 index 0000000..09e07cf --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/proposals.md @@ -0,0 +1,139 @@ +# Proposals — the act map, a second act map, a process + +Three definitions, `[PROPOSED]`. Nothing here is filed. Emil rules each one, and where it is filed, at G1. + +| # | Proposal | Rests on | Weakest point | +|---|---|---|---| +| D-1 | **The act map** is the record of one ruled decomposition under one declaration of ground axes. It holds act sites. It has two relations: containment, which is a tree under each top act, and causal dependency, which is a directed graph | `DDD-ground-06`; `DDD-address-01`; `DDD-address-02`; the `lc:` vocabulary (Round 28, R30) | It says "sites" where `DDD-address-02`'s region says "occurrences" | +| D-2 | **A second act map** exists when, and only when, a second declaration of ground axes exists. A second top act under the same declaration is a second tree in the same map | `DDD-ground-06`'s region; `DDD-address-04`; the accepted T2a map | Whether two pieces of work share a declaration is the mapper's decision. The rule names the decision. It does not make it | +| D-3 | **A process** is a composite act. Mantle's ruling is its limiting case, with depth fixed at one | `DDD-dec-114` (Round 9, ruled reading); `DDD-ground-06` | It adds a second word for a filed term and no new content | + +Every argument below that Emil has not confirmed is `UNVERIFIED — Emil review`. That is all of them. + +## D-1 — the act map + +**Definition.** The act map is the record of one ruled decomposition of work into acts, read under one declaration of ground axes. It holds: + +| Part | What it is | Shape | Source | +|---|---|---|---| +| Act sites | One site per full address: a ground position on the declared axes and a layer path. The occupant is not part of it | Nodes | `DDD-ground-06` | +| Containment | Each act site and each composite act sits within at most one composite act. A composite act within none is a **top act** | A tree under each top act. A forest when there is more than one top act | `DDD-ground-06` (the layer path); `DDD-address-02` (no act is shared) | +| Dependency | 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 | A directed graph. Not a tree | `DDD-address-01` | + +Occurrences are not in the map. Each occurrence is recorded against exactly one site, with its time index. The record of occurrences is a second artefact. + +**Weakest point.** `DDD-address-02`'s region and step 1's card say "a tree of occurrences". This definition says the nodes are sites. The claim's statement is untouched: every occurrence is still its own act, and no act has two parents. But a ruled region is being read more narrowly than it is written, and ruled material changes by supersession. If Emil holds that the map's nodes are occurrences, then the lifecycle's `acts.ttl` is not an act map, because `lc:Act` is a site (S-5). + +**Why "tree or graph" has two answers.** The survey finds 11 lines that need a tree and 13 that need a graph. They are about different relations. "A tree of occurrences" (R-6) rules out one act under two parents. "Follows an edge of the act map" (`lc:` shapes) walks dependencies. Neither can be given up: the layer path needs the tree, and step 1b and the fan-out query need the graph. + +**Rests on.** +- `DDD-ground-06` (upstream, projected): the address, the layer path, and "addresses are relative to a ruled decomposition". +- `DDD-address-01` (projected): dependency over ground readings. +- `DDD-address-02` (projected): every occurrence is its own act. +- The `lc:` vocabulary, ruled by Round 28 (R30): `lc:Act` as a site, `lc:within`, `lc:dependency`. +- "Top act" rests on **none**. It is used in `sdlc.md` §3 and §10 and is not filed (S-8). This definition would file it. +- That occurrences sit outside the map rests on the `lc:` data and on **no claim**. + +**Falsifier.** Any of: +1. An act site that must sit within two composite acts for its governing set to be stated. +2. A dependency that can be stated between two occurrences and between no two sites. +3. A question about the work that the sites and the occurrence record together cannot answer, and a single tree of occurrences can. + +**Pressure case already in the repository.** S-4: a later o5 reads an earlier o6, and o6 reads o5. Between sites that is a loop. The data omits one edge to keep sites acyclic. Limb 2 does not fire, because the dependency can be stated between sites. But "dependencies are acyclic" is true of occurrences and not of sites, and the definition must not claim otherwise. + +**What it breaks.** If limb 1 fires: `lc:ActShape`, the uniqueness of the layer path, and `DDD-ground-06`'s "exactly one address". If limb 2 or 3 fires: the split between map and record, and with it the lifecycle graph data and Mantle's reading of it. + +## D-2 — when a second act map exists + +**Rule.** A second act map exists when, and only when, a second declaration of ground axes exists. Two act sites belong to one map exactly when their ground positions are read on the same declared axes, under the same ruled decomposition. + +| Case | One map or two | Why | +|---|---|---| +| The PDLC's acts and the SDLC's acts, in two files | One | One declaration: surface read, change locus, authority read (`DDD-dec-115`) | +| A second top act under the same axes, such as changes to the SDLC itself (`sdlc.md` §10) | One, with two trees | Same declaration. T2a already has three roots in one accepted map (S-7) | +| The quick start's Varve slice and the lifecycle | Two | Different declarations | +| The same work, decomposed a second way | One at a time | Re-decomposition supersedes (`DDD-ground-06`'s region). The old map is history | +| A part of a map, such as o1b to o13 | Not a map | It is the acts within one composite act of the map (S-10) | + +**Why the axes decide.** An address is a position on declared axes. Coincidence is equality of ground positions (`DDD-address-04`). Applicability predicates range over positions (`DDD-ground-01`). None of the three is defined between two declarations. So the boundary of a map is the boundary of what can be compared and governed together. Between two maps only one relation remains: an act in one reads state that an act in the other produced. + +**Weakest point.** 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. Then some acts never read some axes, which is the held T2b test item F-1: "an act that never reads an axis a governing predicate uses" (act address landing, GATE 1 ruling 7). Whether that is a position is not ruled. So the rule says what a second map is and what it costs. It does not say when to make one. + +**The alternative, for the ruling.** One map per top act. It is simpler to state, and it matches "the SDLC's act map" in four places. It fails on the accepted T2a map, which has three roots (S-7). It would also make the changes to the SDLC a second map whose acts are compared with the first at every o11, across a boundary where comparison is not defined. + +**Rests on.** +- `DDD-ground-06`'s region: axes are declared, and addresses are relative to a ruled decomposition. +- `DDD-address-04`: coincidence at ground position. +- Act address landing, GATE 1 ruling 7 (`DDD-dec-38`): the T2a map accepted. +- `DDD-dec-115`: the lifecycle map's three axes. +- That the axis declaration is the boundary rests on **no filed claim or ruling**. It is this session's reading of S-6. + +**Falsifier.** Either: +1. A governing decision whose applicability predicate must cover occurrences in two maps. +2. Two occurrences in two maps whose behaviour must be compared (`DDD-address-05`) to answer a question the work poses. + +Each shows a split that loses governance. The second application case will test it: an organisation mapped beside the PDLC either shares the PDLC's axes or does not. + +**What it breaks.** Checking a map on its own (`check.py`). The two grains of `DDD-address-05`, which assume one address space. Any tool that points from one map at acts in another. + +## D-3 — a process + +**Definition.** A process is a composite act. A subprocess is a composite act within another. A process's acts are the act sites whose layer paths pass through it. + +**Mantle's ruling as the limiting case.** "A process is a composite act that holds acts directly" is this definition with depth fixed at one: the members shown are the acts one step below. Mantle's view may keep it. This repository cannot adopt it as written: + +| Composite act | Holds acts directly | A process under Mantle's ruling | Called a process in this repository | +|---|---|---|---| +| PDLC | Yes: o0, o2a, oS, o1, oC, oR, o16, oU | Yes | Yes (`DDD-dec-118`; step 1b) | +| SDLC | **No.** It holds frame, build, accept, land and run | **No** | **Yes.** Round 9: "the SDLC is a subprocess under the PDLC". Round 5: "the process of getting changes to production" (`DDD-dec-114`) | +| frame, build, accept, land and run | Yes | Yes | No. They are "stages" (`acts.ttl`) | + +Adopting the ruling as written would un-name the SDLC as a process, or require moving its acts, which is out of scope. + +**Weakest point.** The definition adds nothing canon lacks. "Process" becomes a reader's word for "composite act". If Emil means more by a process (owners, declared kinds of demand, an entry and a discharge), this definition is too weak, and step 1b is where the stronger one would come from. I found no ruling that asks for more. + +**The alternative, for the ruling.** A process is a composite act that declares kinds of demand, with an entry act and a discharge act for each (step 1b's unit). It separates the PDLC from "frame". It rests on `DDD-dec-118` and on four projected claims with one process as their whole evidence, so it would define a general word from one case. + +**Rests on.** +- `DDD-dec-114`: Round 9, with the reading ruled in Round 14, already equates a subprocess with a composite act within another. +- `DDD-ground-06` and `term:act-address`: composite acts and the layer path. +- "Process" itself rests on **no filed claim or term**, here or upstream. +- Mantle's ruling is taken from the issue text. This session has not read Mantle's planning project. + +**Falsifier.** A use of "process" in this repository, or in a mapped case, that names something no composite act can be: work with no containing act, or a flow that crosses two top acts and belongs to neither. + +**What it breaks.** Step 1b's wording ("each process declares its own kinds of demand") and the promotion condition of `DDD-flow-01` to `-04` ("a second process"), which would then have no defined subject. + +## Where to file — proposed + +| What | Where | Form | +|---|---|---| +| The rulings of G1 | `core/decisions/DDD-dec-122.yaml` | One decision, `basedOn` the claims below and `DDD-dec-114`, `-115`, `-38` | +| D-1, the act map, with "top act" | `core/claims/DDD-address-06.yaml` | Conceptual, projected. Test: T2b | +| D-2, a second act map | `core/claims/DDD-address-07.yaml` | Normative, projected, as `DDD-address-02` is: a governing choice about representation | +| D-3, a process | `core/claims/DDD-address-08.yaml` | Normative, projected | +| Pointers | `method/01-map-and-index-acts.md`, "Artefact out" row; `method/01b-map-the-flow-of-demand.md`, first use of "process" | One cited sentence each | + +Not proposed: +- **The term registry.** `core/graph/terms.yaml` holds terms established by numbered core documents. None of the three is. +- **The `lc:` vocabulary.** It is ruled, and an `lc:Process` class would add a second name for `lc:CompositeAct`. +- **Upstream.** Out of scope. The act map is diachronic, so it files downstream by `DDD-dec-09`'s charter in any case. + +## What the rulings would leave open + +| # | Item | From | +|---|---|---| +| O-1 | `DDD-address-02`'s region says "a tree of occurrences". If D-1 is ruled, the region is superseded or annotated, not rewritten | D-1 | +| O-2 | `sdlc.md` §10: the second top act has no graph data, and "the same addresses with a different layer path" contradicts `DDD-ground-06` | S-8, S-9 | +| O-3 | Four places call the SDLC's part "the act map" | S-10 | +| O-4 | The o5 and o6 loop is left out of the data | S-4 | +| O-5 | PR #73 rewrites prose under `applications/`. The survey's line numbers are `main`'s at `84aa466` | `bootstrap.md` | + +## For G1 + +1. D-1: are the map's nodes act sites, with occurrences in a record beside it? +2. D-1: is "top act" filed, as a composite act within no other? +3. D-2: does the axis declaration bound a map, or does each top act have its own? +4. D-3: is a process any composite act, with Mantle's ruling as the depth-one view? +5. Filing: one decision and three claims in the address area, or another form? +6. Is there a GitHub issue number for the commits? diff --git a/meta/sessions/2026-11-17-act-map-and-process/rulings.md b/meta/sessions/2026-11-17-act-map-and-process/rulings.md new file mode 100644 index 0000000..5427f5e --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/rulings.md @@ -0,0 +1,39 @@ +# Rulings — the act map and a process, 2026-11-17 + +Emil's rulings and statements, in the order given, in his words. Recorded when given. G1 closed at R-7. `proposals-2.md`, with its amendments A-1 and A-2, carries the definitions as ruled. + +| # | Time (Europe/Berlin) | Status | Emil's words | Reading | +|---|---|---|---|---| +| E-1 | 19:28 | Direction given, not a ruling | "im thinking that an act map must have a direction - and ours must have acts and ground axes. Then we must take into account what a process is, and how that is a simple view of our act map. Because ours have layers and act chains. - a full act map will show all the acts at their ground axes, which will be a wierd visual picture. I think the direction needs to be the demand pull, so "north" is a demand pull, and then we can change the diretion to get different views. This will also allow us to see the chain of acts to a pull. Which then leads us to the conclussion that a process is an act map with a direction towards the defined demand pull" | A process is a view of the act map, directed at a declared demand pull. Claude's reading, `UNVERIFIED — Emil review` | +| E-2 | 19:31 | Statement of 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. We have ruled this in the actor indexed determation theory repo" | Checked at `v5.15.2`: `DDD-ground-06` (the layer path is "the chain of composite acts it sits within"); `core/14` §5 and `core/09` §1 ("acts nest as actors nest"). A layer is a composite act and nothing else | +| R-1 | 19:34 | **Ruled** | "yes to the first" | North is the discharge act of a declared demand kind | +| — | 19:34 | Open, asked by Emil | "but for the other end im not sure, could there be multiple ends ?" | Not ruled. See below | +| E-3 | 20:27 | Direction given. Whether it is a ruling is asked | "we follow the determination pull, which means that the decisions that must be made, this also means that we must index the decisions not just the acts. without that index how can we see the pull" | The pull is determination demand: the governing decisions that must be made. Checked at `v5.15.2`: `term:act` ("an act is decisions resolved against ground"; "the unit demand is counted in"), `term:conservation` ("Every governing decision gets made"), `term:last-decision`. The lifecycle map carries no decision on any act: an act has a label, an address, a holder and dependencies. So R-1's north, the discharge act of a demand kind, is a stand-in for a decision. Claude's reading, `UNVERIFIED — Emil review` | +| E-4 | 20:43 | Correction by Emil. Whether it supersedes R-1 is asked | "North cant be a decision it must be where the demand for decisions originate, so it is a cause. This is very clear in the actor theory, a fire in a forest creates demand even though no one is there. Take a look at the Canon we have defined this befire" | Checked at `v5.15.2`. `DDD-frame-13` (projected): "determination demand is thereby a measure over unresolved determinables". `core/00` §4a: "a decision is a determinable taken up by governance", and "what no governance takes up is still a determinable — resolved, when its act completes, by whatever resolves it". `core/09` §7a: a determinate lands "whether or not anything governed it". The fire itself is in `meta/holding-note-addendum-determinables.md` Q36 ("World-pull … the fire"), which is a holding note and not ratified. North is therefore an unresolved determinable: the cause. Claude's reading, `UNVERIFIED — Emil review` | +| R-2 | 21:12 | **Ruled**, supersedes R-1 | "1. Yes i think so this would make the most sense." | Asked: "Is north the unresolved determinable, the source of pull, and does that supersede R-1? R-1's discharge act would become the other end." North is the unresolved determinable. The discharge act is the other end | +| R-3 | 21:12 | **Ruled** | "2. Yes - that would build the index we need." | Asked: "Is the index an index of determinables, with decisions as the ones governance took up?" The index is of determinables | +| R-4 | 21:12 | **Ruled** | "3. 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" | A process is a human concept, scoped to an area of expertise. It is not an object of the model. The view from determinable to determinate is its translation into the model, and the best one available. Claude's reading, `UNVERIFIED — Emil review`: a process may therefore cross composite acts, and that is not a defect in the decomposition | +| R-5 | 21:19 | **Ruled** | "agreed on all" | Said in reply to Claude's view of 21:15, which proposed three things. (1) A process translates to a named view with one or more norths, optionally bounded by composite acts, because people name processes by scope and ownership as well as by cause. (2) In tooling a process stays a saved view with a name, never a node. (3) The second mapped case is where the translation is tested. Claude reads "all" as these three, and not as the seven G1 questions of 21:12. `UNVERIFIED — Emil review` | +| E-5 | 21:19 | Statement | "the calendar observation is good, time is always the cause of determination one way or the other the law of thermo dynamics is in essence what will ensure that the world changes with time." | Work that starts on a calendar has a north like any other: a determinable that time makes unresolved again. The schedule is governance sampling a world that changes whether or not anyone looks. Not checked against a filed claim: the nearest text is the upstream holding note's Q36 ("the world sets the tempo and never misses a tick"), which is not ratified. Claude's reading, `UNVERIFIED — Emil review` | +| R-6 | 21:22 | **Ruled** | "agreed time is the one that sets the change rate of a determinable which is what creates the demand" | Said in reply to Claude's caution of 21:19, that time cannot tell one north from another and that what tells them apart is which determinable time moves and how fast. Time sets a determinable's rate of change, and that change is what creates demand. North stays the determinable. Claude does not read this as closing G1: the seven questions were not answered. `UNVERIFIED — Emil review` | +| R-7 | 21:25 | **Ruled. G1 closed** | "i agree and accept on all seven points" | The seven points as Claude listed them at 21:19, with the rate of change added to point 2 at 21:22. (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) D-2 as written: a second act map exists only with a second declaration of ground axes. (4) D-3 as amended in A-1, and a view leaves out earlier readings, so rank from north is strict. (5) One decision, `DDD-dec-122`, and three claims, `DDD-address-06` to `-08`, with one cited sentence each in `method/01` and `method/01b`. (6) Definitions only in this session; building the lifecycle's index, and which step builds it, become new issues. (7) No issue number on the commits | + +## Corrections + +- **Emil, on Claude's reading of E-3 (E-4).** Claude proposed that north is "a decision that must be made". That fused demand with decisions. Canon keeps them apart: demand is over determinables, and a decision is a determinable that governance has taken up. Demand exists before any decision, and without any actor. The proposal is withdrawn. + +- **Claude, on E-2.** `proposals.md` D-3 proposed "a process is a composite act". After E-2 that proposal is withdrawn: the only name for a layer is composite act, so a process cannot be one. Claude's question whether to keep "two words, one for the layer and one for the chain" is withdrawn with it. `proposals.md` is revised at the close of G1, not rewritten now. + +## Evidence computed for the open question + +Run over `applications/pdlc/graph/acts.ttl`, `applications/sdlc/acts/acts.ttl` and `demand-flow.ttl` at `84aa466`. Dependencies only (`lc:dependency`), honouring `lc:forKind`. Earlier readings (`lc:readsEarlier`) are left out. + +| Demand kind | Declared entry acts | North | Acts behind north | Where the chain ends on its own | +|---|---|---|---|---| +| New | o0, oC | o16 | 15 | o0 | +| Owed | oC | o13 | 11 | oC | +| Own-ground | oG | o13 | 11 | oG | + +- For each kind, every act behind north is also after a declared entry act. Nothing is behind north and outside the entry. +- Without `lc:forKind`, the chain behind o13 has three ends: o0, oC and oG. +- New demand declares two entry acts. Its chain reaches only o0. No dependency leads from oC towards o16 for new demand, though `f:what-is-wrong` says such an item is "classified new at oC, then an option at o0". diff --git a/meta/sessions/2026-11-17-act-map-and-process/successor-items.md b/meta/sessions/2026-11-17-act-map-and-process/successor-items.md new file mode 100644 index 0000000..8b7ea9e --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/successor-items.md @@ -0,0 +1,15 @@ +# Successor items — the act map and a process, 2026-11-17 + +Nine items stay open after `DDD-dec-122`. None is ruled. O-6 and O-7 become new issues (R-7, point 6). + +| # | Item | Where it shows | For | +|---|---|---|---| +| O-1 | `DDD-address-02`'s region says the act map is "a tree of occurrences". `DDD-address-06` says its nodes are act sites and the tree is containment. The region is superseded, annotated or left | `core/claims/DDD-address-02.yaml:8`; `method/01-map-and-index-acts.md:62` | Emil | +| O-2 | The second top act, changes to the SDLC itself, has no graph data. One sentence about it contradicts `DDD-ground-06`: "the same addresses with a different layer path" | `applications/sdlc/sdlc.md:451`, `:455` | Emil | +| O-3 | Four places call the SDLC's part of the lifecycle map "the act map" | `survey.md`, S-10 | A prose pass, after PR #73 | +| O-4 | A later o5 reads an earlier o6, and o6 reads o5. The data leaves the first edge out | `applications/sdlc/sdlc.md:106`; `applications/sdlc/acts/acts.ttl:88` | Emil | +| O-5 | New demand declares oC as an entry act. No dependency leads from oC towards o16 for new demand | `applications/pdlc/graph/demand-flow.ttl`; `rulings.md`, evidence | Emil | +| O-6 | **New issue.** The lifecycle has no index of determinables. Its six sources of pull are not marked taken up or not, and carry no rate of change | `applications/pdlc/graph/demand-flow.ttl` | Emil opens the issue | +| O-7 | **New issue.** Which method step builds the index: step 1, or step 3, which is not filed. The rate of change has no unit and no measure, and step 4's tick rate is not filed either | `method/01-map-and-index-acts.md`; `method/03-surface-decisions.md` | Emil opens the issue | +| O-8 | PR #73 rewrites prose under `applications/`. The survey's line numbers are `main`'s at `84aa466` | `survey.md` | Whoever lands second | +| O-9 | Carry R-2, R-4 and R-5 to Mantle's planning project. Mantle's ruling of 2026-11-17 is a view with a bound and no north | `DDD-address-08`, notes | Emil | diff --git a/meta/sessions/2026-11-17-act-map-and-process/survey.md b/meta/sessions/2026-11-17-act-map-and-process/survey.md new file mode 100644 index 0000000..7c279ef --- /dev/null +++ b/meta/sessions/2026-11-17-act-map-and-process/survey.md @@ -0,0 +1,156 @@ +# Survey — every use of "act map" + +"Act map" stands on 109 lines in 38 files. The repository uses the word in three ways that do not agree, and it defines none of them. + +| Question | What the uses say | +|---|---| +| One or many? | **One per mapped case.** No line has two maps of one case. The repository holds three cases, each with its own map: the dry run's T2a, the quick start's Varve slice, and the product lifecycle. Four lines name the SDLC's part of the lifecycle map as "the SDLC's act map", against seven that say the two files are one map | +| Tree or graph? | **Both, over different relations.** Containment is a tree: 11 lines, and the data enforces it. Dependency is a graph: 13 lines, and the data has acts with two and three incoming dependencies. Ten more lines read the map as a table with rows | +| Nodes? | **The claim says occurrences. The data says act sites.** `DDD-address-02` and step 1's card say "a tree of occurrences". `lc:Act` is "an act site of the map: one address, possibly many occurrences", and occurrences live in a separate record | + +Read at `84aa466` (`main`), with canon at `v5.15.2`. The search was `grep -rnIiE "act[- ]maps?\b|actmap|act_map"` over the working tree, excluding `.git` and this session's directory. + +## Findings + +| # | Finding | Where | +|---|---|---| +| S-1 | **Only one filed sentence says what the act map is, and it is in a region, not a statement.** `DDD-address-02`'s region says the claim "governs the act map (a tree of occurrences)". Step 1's card repeats it. No claim, decision or term defines the act map | `core/claims/DDD-address-02.yaml:8`; `method/01-map-and-index-acts.md:62` | +| S-2 | **Containment is a tree in the data.** Every act sits within exactly one composite act (`lc:ActShape`, `lc:within`, at most one). The lifecycle map has one root, `m:PDLC` | `applications/pdlc/graph/shapes.ttl:29`; `applications/pdlc/graph/acts.ttl:17` | +| S-3 | **Dependency is not a tree in the data.** o1b has three incoming dependencies, scoped by kind. o2b and o12 have two each. `lc:readsEarlier` adds loops across issues: o2a reads earlier o13s | `applications/sdlc/acts/acts.ttl`; `applications/pdlc/graph/ontology.ttl:113` | +| S-4 | **The stream has a loop between act sites that the data leaves out.** The prose has o5 read "o4 (then o6)" and o6 read o5's report. The data gives o5 a dependency on o4 only. The loop is between occurrences: a later o5 reads an earlier o6. "Within an issue, dependencies are acyclic" therefore holds over occurrences, and over sites only because the edge is omitted | `applications/sdlc/sdlc.md:95`, `:106`, `:107`; `applications/sdlc/acts/acts.ttl:88` | +| S-5 | **Nodes are act sites in the data and occurrences in the claim.** `lc:Act` is a site with many occurrences. The occurrence record is a second artefact, merged with the map for checking. The quick start's rows are called occurrences and then used as sites ("if you run o3 again tomorrow, the new occurrence has o3's address") | `applications/pdlc/graph/ontology.ttl:33`; `applications/sdlc/acts/check.py:10`; `method/quick-start.md:77`, `:101` | +| S-6 | **Each case's map has its own declared ground axes.** T2a declares four. The quick start declares three. The lifecycle declares three (`DDD-dec-115`: "the act map's three axes"). No map uses two declarations, and no declaration serves two maps | `meta/sessions/2026-09-27-act-address/results-act-address-dry-run.md:31`; `method/quick-start.md:63`; `core/decisions/DDD-dec-115.yaml:5` | +| S-7 | **One map already holds several roots.** T2a's layer paths start at three different composite acts: delivery pipeline, operations, runtime. Emil accepted that map (act address landing, GATE 1 ruling 7; `DDD-dec-38`) | `meta/sessions/2026-09-27-act-address/results-act-address-dry-run.md:35` to `:37` | +| S-8 | **"Top act" is used and not filed.** `sdlc.md` names "the second top act: changes to the SDLC itself", and has o11 read changes "produced in other top acts". The second top act has no graph data: `m:PDLC` is the only root. Nothing says whether it belongs to the lifecycle map or to a second map | `applications/sdlc/sdlc.md:124`, `:451` | +| S-9 | **A sentence in `sdlc.md` §10 contradicts `DDD-ground-06`.** "Its acts sit at the same addresses with a different layer path." The layer path is part of the address, so two acts with different layer paths never share an address. They can share a ground position, which is coincidence (`DDD-address-04`). Flagged, not harmonised (`AGENTS.md`) | `applications/sdlc/sdlc.md:455` | +| S-10 | **A part is named as a map in four places.** "The SDLC's act map", "its act map", "the act map, o1b to o13". Each sits beside a sentence saying the two files are one map | `applications/sdlc/acts/acts.ttl:5`; `applications/sdlc/README.md:68`; `applications/sdlc/sdlc.md:89` | +| S-11 | **"Process" is used and not filed.** Canon at `v5.15.2` has no term for it. Downstream, Emil's Round 9 sentence "the SDLC is a subprocess under the PDLC" was ruled to read "the SDLC is a composite act within the PDLC". Step 1b uses the word 24 times without saying what one is, and its four claims wait on "a second process" | `core/decisions/DDD-dec-114.yaml:18`; `method/01b-map-the-flow-of-demand.md`; `core/claims/DDD-flow-01.yaml:73` | +| S-12 | **The SDLC holds no act directly.** Its members are four composite acts: frame, build, accept, land and run. Every SDLC act sits within one of those. The PDLC holds eight acts directly, and the SDLC | `applications/sdlc/acts/acts.ttl:126` to `:130` | + +## The list + +"One per mapped case" marks a line that names a map belonging to one case or one run of step 1. "One" marks a line that says "the act map" inside one case. "Not implied" means the line names the map and says nothing of its shape. + +### In force: claims, decisions, the method, the applications + +| File and line | One or many | Tree or graph | What the line says | +|---|---|---|---| +| `applications/README.md:7` | one | tree: containment | nesting is "a relation in the act map" | +| `applications/pdlc/README.md:21` | one | not implied | "the PDLC's acts on the act map": the PDLC has acts on it, not a map of its own | +| `applications/pdlc/README.md:29` | one | tree: containment | nesting is a relation in the map | +| `applications/pdlc/graph/acts.ttl:5` | one, held in two files | not implied | "the PDLC's acts on the act map"; "the two files are one map" | +| `applications/pdlc/graph/check.py:1` | one, held in two files | not implied | "the act map (PDLC and SDLC)" | +| `applications/pdlc/graph/check.py:138` | one | graph: dependency edges | "follows an edge of the act map" | +| `applications/pdlc/graph/check.py:155` | one | table: rows | "a seam is a row of the act map" | +| `applications/pdlc/graph/demand-flow.ttl:11` | one, held in two files | not implied | names both acts.ttl files | +| `applications/pdlc/graph/ontology.ttl:11` | one | tree and graph | the form: composite acts, act sites, causal dependencies | +| `applications/pdlc/graph/ontology.ttl:33` | one | not implied | "an act site of the map": the nodes are sites, not occurrences | +| `applications/pdlc/graph/ontology.ttl:54` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:62` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:64` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:66` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:69` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:70` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:71` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:72` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:73` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:92` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:93` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:94` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:106` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:114` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:124` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:125` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/ontology.ttl:195` | one | not implied | dct:source names "the act map" of Round 2 as where a term comes from | +| `applications/pdlc/graph/shapes.ttl:8` | one | not implied | | +| `applications/pdlc/graph/shapes.ttl:252` | one | not implied | | +| `applications/pdlc/graph/shapes.ttl:367` | one | graph: dependency edges | an edge is a dependency or an earlier reading | +| `applications/pdlc/graph/shapes.ttl:393` | one | table: rows | "a seam is a row of the act map"; the row is a producing act and a reading act joined by a dependency | +| `applications/pdlc/pdlc.md:152` | one | table: rows | the seam table is checked against it | +| `applications/pdlc/pdlc.md:156` | one, held in two files | not implied | names both acts.ttl files | +| `applications/pdlc/pdlc.md:566` | one | not implied | "the PDLC's acts on the act map" | +| `applications/pdlc/pdlc.md:568` | one, held in two files | not implied | "one map, validated together"; "the form of method step 1" | +| `applications/sdlc/README.md:68` | a part named as a map | not implied | "its act map": the SDLC's own | +| `applications/sdlc/acts/acts.ttl:5` | a part named as a map | not implied | "the SDLC's act map"; four lines later "the two files are one map" | +| `applications/sdlc/acts/acts.ttl:13` | one | tree: containment | "the act map's layers, read as composite acts" | +| `applications/sdlc/acts/check.py:1` | one | not implied | "the lifecycle act map" | +| `applications/sdlc/acts/check.py:6` | one | not implied | | +| `applications/sdlc/acts/check.py:10` | one | not implied | the occurrence record is merged with the map: the map holds sites, not occurrences | +| `applications/sdlc/acts/shapes.ttl:16` | one | not implied | | +| `applications/sdlc/sdlc.md:89` | a part named as a map | not implied | heading "The act map, o1b to o13"; the body says "one map" | +| `applications/sdlc/sdlc.md:118` | one | graph: dependency edges | readings from the causal index | +| `applications/sdlc/sdlc.md:665` | one | graph: dependency edges | dependencies scoped by kind | +| `applications/sdlc/sdlc.md:762` | one | not implied | another product's sessions would be "mapped onto the act map": one map that adopters share | +| `core/claims/DDD-address-02.yaml:8` | one | tree: containment | "a tree of occurrences"; the only claim that says what the map is | +| `core/claims/DDD-flow-03.yaml:14` | one, held in two files | not implied | names both acts.ttl files | +| `core/claims/DDD-flow-03.yaml:22` | one | tree and graph | traced on the map; the seam table has rows read at an act | +| `core/decisions/DDD-dec-114.yaml:20` | one | tree: containment | nesting is "a relation in the act map" | +| `core/decisions/DDD-dec-114.yaml:128` | one | table: rows | a seam listing is checked against it | +| `core/decisions/DDD-dec-115.yaml:5` | one | not implied | the map has three axes: one axis declaration | +| `core/decisions/DDD-dec-115.yaml:124` | one | not implied | "the act map's graph data" | +| `core/decisions/DDD-dec-115.yaml:185` | one | graph: dependency edges | readings from the causal index | +| `core/decisions/DDD-dec-38.yaml:55` | one per mapped case | not implied | "the T2a act map" | +| `method/01-map-and-index-acts.md:62` | one | tree: containment | "a tree of occurrences" | +| `method/01-map-and-index-acts.md:82` | one per mapped case | not implied | "this step's act map" | +| `method/01b-map-the-flow-of-demand.md:24` | one | graph: dependency edges | demand is traced across it | +| `method/01b-map-the-flow-of-demand.md:41` | one per mapped case | not implied | step 1's output | +| `method/01b-map-the-flow-of-demand.md:57` | one | graph: dependency edges | "along edges of the act map" | +| `method/01b-map-the-flow-of-demand.md:97` | one per mapped case | not implied | "your act map" | +| `method/01b-map-the-flow-of-demand.md:132` | one per mapped case | not implied | ground in | +| `method/01b-map-the-flow-of-demand.md:134` | one | not implied | graph data sits beside it | +| `method/01b-map-the-flow-of-demand.md:145` | one, held in two files | not implied | names both acts.ttl files | +| `method/01b-map-the-flow-of-demand.md:249` | one per mapped case | not implied | | +| `method/quick-start.md:75` | one per mapped case | table: rows | a table, one row per occurrence, with the layer path as a column | + +### Release notes + +| File and line | One or many | Tree or graph | What the line says | +|---|---|---|---| +| `CHANGELOG.md:15` | one per mapped case | graph: dependency edges | demand is traced across it | +| `CHANGELOG.md:25` | one per mapped case | not implied | each specification carries its own | +| `releases/v0.7.0.yaml:41` | one per mapped case | graph: dependency edges | copy of CHANGELOG.md:15 | +| `releases/v0.7.0.yaml:51` | one per mapped case | not implied | copy of CHANGELOG.md:25 | + +### Session records (history, never edited) + +| File and line | One or many | Tree or graph | What the line says | +|---|---|---|---| +| `meta/sessions/2026-09-27-act-address-landing/gate1-rulings.md:15` | one per mapped case | not implied | the T2a map is accepted | +| `meta/sessions/2026-09-27-act-address-landing/gate1-survey.md:145` | one per mapped case | not implied | | +| `meta/sessions/2026-09-27-act-address-landing/gate1-survey.md:148` | one per mapped case | not implied | axes and five occurrences | +| `meta/sessions/2026-09-27-act-address-landing/gate1-survey.md:174` | one per mapped case | not implied | | +| `meta/sessions/2026-09-27-act-address-landing/prompt.md:48` | one per mapped case | not implied | | +| `meta/sessions/2026-09-27-act-address/prereg-act-coordinates.md:26` | one | tree: containment | R-6: "a tree of occurrences" | +| `meta/sessions/2026-09-27-act-address/prereg-act-coordinates.md:77` | one | tree: containment | "a tree of unique occurrences" | +| `meta/sessions/2026-09-27-act-address/prereg-act-coordinates.md:108` | one per mapped case | not implied | "its act map": the first independent case has its own | +| `meta/sessions/2026-09-27-act-address/results-act-address-dry-run.md:7` | many (plural) | not implied | "the act maps below": one per case | +| `meta/sessions/2026-09-27-act-address/results-act-address-dry-run.md:11` | one per mapped case | not implied | the map depends on the axes the mapper declared | +| `meta/sessions/2026-09-27-act-address/results-act-address-dry-run.md:31` | one per mapped case | table: rows | a table of occurrences under its own four declared axes; its layer paths start at three different roots | +| `meta/sessions/2026-09-27-act-address/results-act-address-dry-run.md:70` | one per mapped case | not implied | | +| `meta/sessions/2026-09-27-act-address/rulings.md:27` | one per mapped case | not implied | "the T2a act map's axis declarations" | +| `meta/sessions/2026-11-02-ready-to-try/predictions.md:378` | one per mapped case | not implied | the quick start's map | +| `meta/sessions/2026-11-02-ready-to-try/predictions.md:421` | one per mapped case | table: rows | the quick start's map, counted in rows | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/findings.md:10` | one | graph: dependency edges | an order between two acts | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/findings.md:19` | one | graph: dependency edges | causal-index readings | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/predictions.md:57` | one | not implied | a record is merged with the map: the map holds sites, not occurrences | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt-2.md:208` | one | table: rows | a row is checked against the map | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt-2.md:240` | one | not implied | "the act map, the occurrence record": two things | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:35` | one | not implied | | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:197` | one | tree: containment | nesting is "a relation in the act map" | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:314` | one | not implied | the o1 to o15 map | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:373` | one | not implied | "the act map's form" | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:438` | one | table: rows | seam rows are checked against it | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:478` | one | not implied | "the PDLC's acts on the act map" | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:498` | one | not implied | | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/prompt.md:504` | a part named as a map | not implied | "the act map for o1b to o13" | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:39` | one | not implied | | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:201` | one | tree: containment | nesting is "a relation in the act map" | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:576` | one | graph: dependency edges | causal-index readings | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:710` | one | tree: containment | R-9, the ruled reading | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:717` | one | graph: dependency edges | causal-index readings | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:719` | one | table: rows | the seam table is checked against it | +| `meta/sessions/2026-11-07-sdlc-and-pdlc/rulings.md:739` | one | not implied | the o1 to o15 map, verbatim | +| `meta/sessions/2026-11-08-demand-flow/findings.md:41` | one | not implied | | +| `meta/sessions/2026-11-08-demand-flow/successor-items.md:14` | one | not implied | | +| `meta/sessions/README.md:53` | one | not implied | "the lc: act map" | +| `meta/sessions/README.md:55` | one | not implied | | diff --git a/meta/sessions/README.md b/meta/sessions/README.md index ecd9910..065ed2f 100644 --- a/meta/sessions/README.md +++ b/meta/sessions/README.md @@ -54,3 +54,4 @@ session's later work exceeds the committed prompt, the excess is visible as exce | `2026-11-08-specification-feasibility/` | Rulings filed, gated — specification feasibility, from a claude.ai conversation (F-1 to F-12): every dependency on ground has a What layer and a How layer, the How decides by three loose-coupling conditions, any granted actor vets a pinned What change and product-cli records the decision (`DDD-dec-116`); vetted ground becomes a ground-sourced bounded context, admitted per system for Deciders, Projectors and Views, with permission the data owner's; product-cli and the framework carry grants and roles, superseding `[D1.11]` (`DDD-dec-117`). Not applied; S-1 to S-8. Issue #62 | | `2026-11-08-demand-flow/` | Rulings filed, gated — map the flow of demand, from the claude.ai conversation's Rounds 23 to 25: a method step after step 1 (`method/01b-map-the-flow-of-demand.md`, `[PROPOSED]`), general, with each process declaring its kinds of demand and the PDLC's new, owed and own-ground as its worked example and starting point; four PDLC-scoped claims in a new area, `DDD-flow-01` to `-04`, projected; `DDD-dec-118`, adding to `DDD-dec-114`; the acme shop's #101, #103 and #104 traced as graph data checked against the act map. Nothing upstream. Round 26 (2026-11-10) closed R-1: sighting separated from entry, only the What owner says whether a defect is a bug. Open: numbering (N-1), promotion (P-1), the two examples (E-1). Issue #67 | | `2026-11-10-release-v0.7.0/` | Release descriptor, gated. `releases/v0.7.0.yaml` is MINOR under `DDD-dec-82`: step 1b's card was added (`DDD-dec-118`), and no step's register moved (F-1). Format 2, `prerelease: true` for Emil to confirm (F-3). Its `CHANGELOG.md` section is from `canon changelog`, and `canon ratify` fills the ratified head. The prompt calls the PDLC and SDLC specifications `[PROPOSED]`, while the repository says they are ruled (Round 28). The summary follows the repository, and Emil is to settle it (F-2). Not landed and not cut. Issue #69 | +| `2026-11-17-act-map-and-process/` | Rulings filed, gated — what an act map is, when there is a second one, and what a process is, from a claude.ai conversation (E-1 to E-5, R-1 to R-7). Every use of "act map" surveyed (109 lines in 38 files). The act map is act sites, the composite acts that layer them, their dependencies and the index of determinables (`DDD-address-06`); a second map needs a second declaration of ground axes (`DDD-address-07`); a process is a human understanding of work, translated as a named view with one or more norths, a north being an unresolved determinable (`DDD-address-08`); `DDD-dec-122`, adding to `DDD-dec-114` and `DDD-dec-118`. All three claims projected. No act and no lifecycle data changed. Nine successor items, among them building the lifecycle's index. `python3 scripts/ci.py` passes. Awaiting Emil's landing | diff --git a/method/01-map-and-index-acts.md b/method/01-map-and-index-acts.md index 5ec5e02..112e56e 100644 --- a/method/01-map-and-index-acts.md +++ b/method/01-map-and-index-acts.md @@ -65,6 +65,8 @@ not, the field says so. Claude's assembly of the fields from their sources is | Exit check | Within the ruled decomposition, every occurrence has exactly one address, and its governing set can be computed from that address, its ground readings and the decisions' applicability predicates, without the verdict itself | `DDD-ground-06` falsifier and test, read as a check. Reading `UNVERIFIED — Emil review` | | Principal | Whoever rules the decomposition. The method names no role for it | `DDD-ground-06` region ("a ruled decomposition"); the role is not filed | +**The act map is defined in `DDD-address-06`** (`DDD-dec-122`): act sites at their addresses, the composite acts that layer them, the dependencies between them and the index of determinables, with occurrences recorded beside it; the card's "a tree of occurrences" is `DDD-address-02`'s region, and the two are not yet reconciled. + ## What would break it - **The claims.** Each claim above carries its own falsifier in its file. `DDD-ground-06` fails if diff --git a/method/01b-map-the-flow-of-demand.md b/method/01b-map-the-flow-of-demand.md index 14a6265..27ef025 100644 --- a/method/01b-map-the-flow-of-demand.md +++ b/method/01b-map-the-flow-of-demand.md @@ -27,6 +27,8 @@ which owner orders it, which seams it crosses, and where it is discharged. Then it asks what else pulls, and classifies every source of pull into the kinds of demand the process declares. +**"A process" is defined in `DDD-address-08`** (`DDD-dec-122`): a human understanding of work, whose translation into the model is a named view of the act map, fixed by one or more norths (a source of pull is a north) and optionally bounded by composite acts. + The step is not about delivery. "Delivery" is reserved by upstream `core/13` for whether an authored decision reaches the act it governs. This step is about how demand arrives and is ordered, which neither delivery nor supply (who resolves a governing decision, and when) says.