Skip to content

The act map, scope and pull: what they are, and how step 1 starts from them #80

Open

Description

@Hafeok

Outcome. The repository says what an act map is, when there is more than one, and what a process is. The method says how a practitioner declares the scope of a map and finds its pulls before mapping any act, and what each later step adds to the act map.

This issue carries all of the work. #79 is closed and folded in here, and #78 is closed without landing.

Ground. AGENTS.md. meta/way-of-working.md. method/README.md and the eleven step cards. core/claims/DDD-address-01.yaml to -05. core/claims/DDD-flow-01.yaml to -04. core/decisions/DDD-dec-114.yaml, -115 and -118. applications/pdlc/pdlc.md §11. applications/sdlc/sdlc.md. applications/pdlc/graph/ontology.ttl. meta/sessions/2026-09-27-act-address/ (the T2b pre-registration). Canon at the tag in graph/upstream.yaml, in particular DDD-ground-05, DDD-ground-06, DDD-frame-13 and term:outcome. The two session records on the archive branch (see "State at opening").

Ruled before this issue was opened, in the claude.ai project conversation. Both records are verbatim.

2026-11-17 (meta/sessions/2026-11-17-act-map-and-process/rulings.md, E-2 and R-2 to R-7):

  • The layering is canon: acts at ground axes, with composite acts above and below, and nothing else.
  • The act map holds act sites, the composite acts that layer them, the dependencies between them, and the index of determinables. Occurrences are recorded beside it. Each determinable in the index carries its rate of change.
  • A second act map exists when, and only when, a second declaration of ground axes exists.
  • North is an unresolved determinable, where demand originates. It is a cause, not a decision. The discharge act is the other end.
  • A process is a human understanding of work, 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. A view leaves out earlier readings. In tooling it is a saved view, never a node.
  • Time sets a determinable's rate of change, which is what creates demand.

2026-11-18 (meta/sessions/2026-11-18-pull-and-scope/rulings.md, R-1 to R-8):

  • Scope is the first declaration of a map. Everything outside it is world to the map, including other people's decisions. The trace back from a request stops where the answer lies outside the scope.
  • A determinable has two or more outcomes that cannot all hold together.
  • A kind of demand is a position on a declared ground axis. Kinds differ by ground, not by where the demand came from.
  • A pull of a narrow scope appears in a wider map as a dependency, and as a seam only where the wider map declares that scope.
  • A pull is a gap between two of four states: specified, actual, observed, expected. The concept is credited to GitHub user pjarnhus. It is mapped to canon from its four names only.

Stated, not ruled: the act map is the central modelling artefact for every application, and step 1 starts from north.

Deliverable.

  1. The two session records are carried onto this issue's branch as they stand, with the survey of every use of "act map" (109 lines in 38 files, read at 84aa466). Exit: both directories are present and nothing in them is reworded.
  2. The pull statement and the five-step procedure (scope, the determinables at the edge, the three readable states, the gaps, the trace to an entry act), carried through one worked example and tested against a junior engineer's first contact. Exit: every field has a check that passes or fails.
  3. Proposed claims, each with a falsifier and what it breaks, written once with both days' rulings in them: the act map, with its scope and its index; when a second act map exists; a process and north; the pull; kinds as ground positions; the four states. Exit: each says which filed claim or ruling it rests on, or that it rests on none.
  4. For each of steps 2 to 10, what the step adds to the act map and where it attaches. Exit: every card's "Value made visible" row is filled or says why it cannot be.
  5. The effect on T2b's pre-registration, on step 1b's kinds and on DDD-address-02's region ("a tree of occurrences"), stated before any card changes. Exit: the session says what stands, what is superseded and what is registered again.
  6. On the rulings, the claims are filed and the cards are changed by supersession. Exit: the validate workflow passes, not only python3 scripts/ci.py, and every commit carries Refs #80.

Gates. G1 after step 5: the principal rules each proposal and where it is filed. G2 after step 6. Then the merge.

Out of scope. Building the lifecycle's index of determinables. Changing any act. Mantle. Canon in the principle repository. tools/canon.

State at opening.

  • The archive. claude/pull-and-scope-2026-11-18 (head 47cf4cc). Keep it until this issue's branch is pushed, so that its ids show as taken. It holds everything done so far: both session records, and the claims and decision as they were filed on 2026-11-17 (DDD-address-06, -07, -08, DDD-dec-122, and one sentence each in method/01 and method/01b). None of it landed on main. Its commits carry no Refs line, so the branch cannot land as it is. It is a source to copy from, not a branch to merge.
  • The filed claims are out of date. They were written before the 2026-11-18 rulings. DDD-address-06 has no scope, and its index has no four states. DDD-address-07 is silent on scope. DDD-address-08 says a north exists "whether or not governance has taken it up", which now means the governance inside the scope. Deliverable 3 writes them again, once.
  • The ids. Ruled 2026-11-18 (R-8). The claims keep their ids: DDD-address-06 (the act map), -07 (a second act map), -08 (a process and north) and DDD-dec-122, each amended before landing, as DDD-flow-03 was. New claims take DDD-address-09 onwards. Each amended claim says in its notes that it was first drafted on 2026-11-17 on a branch that did not land, and was amended on the rulings of 2026-11-18. Check every branch of both repositories before filing.
  • The old branch. claude/act-map-and-process-2026-11-17 (head 66bc21f) is to be deleted. All of its commits are contained in the archive branch.
  • Open under the four states. "Actual" cannot be read directly, so the gap between actual and observed can only be suspected. "Expected" has one holder per stakeholder. Own-ground demand has no obvious place among the gaps. Whether pjarnhus has agreed to the concept appearing here is not recorded.
  • Open from 2026-11-17 (successor-items.md): O-2 to O-5 and O-9 stay open. O-1 and O-7 are taken up by deliverables 5 and 3. O-6 stays out of scope.
  • Not part of this issue. The Agent review check fails on a build error in tools/canon (NU1004: the package lock file expects Microsoft.NET.ILLink.Tasks 10.0.14 and the runner resolves 10.0.15).

Generated by Claude Code

Activity

  1. changed the title [-]Step 1 starts from scope and pull, and the act map is the method's central artefact[/-] [+]The act map, scope and pull: what they are, and how step 1 starts from them[/+] on Nov 18, 2026
  2. added 20 commits that reference this issue on Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    Priority

    None yet

    Effort

    None yet

    Progress

    None yet

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions