Skip to content

The repository says what an act map is, when there is more than one, and what a process is #79

Closed as not planned

Description

@Hafeok

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.


Generated by Claude Code

Activity

  1. Hafeok commented on Nov 18, 2026

    @Hafeok
    CollaboratorAuthor

    State at 2026-11-18, 09:40 (Europe/Berlin). This issue was opened after the work was done. Its text was given in the claude.ai project conversation on 2026-11-17 and is verbatim in the session's prompt.md.

    What Where
    Branch claude/act-map-and-process-2026-11-17, head 66bc21f, 11 commits on 84aa466
    Pull request #78
    Filed DDD-address-06, -07, -08; DDD-dec-122; one cited sentence each in method/01 and method/01b
    Record meta/sessions/2026-11-17-act-map-and-process/
    Gates G1 closed (rulings R-2 to R-7). G2 reached. Not landed

    What blocks the merge. The validate workflow refuses the branch at canon issue-refs --basis: none of the 11 commits carries a Refs #N line. Everything before that step passes (scripts/ci.py, canon's tests, the changelog check). The session reported the gate as passing on scripts/ci.py alone, which was wrong.

    To do, in a Claude Code session.

    1. Reword the 11 commit messages to add Refs and this issue's number. No file content changes. The filing commit keeps its Basis: line.
    2. Force-push the branch. The head to ratify changes from 66bc21f, so The act map, a second act map and a process: DDD-dec-122, DDD-address-06 to -08 #78's description needs the new head.
    3. Record in the session's rulings.md that point 7 of R-7 ("no issue number on the commits") is superseded by this issue.
    4. Rebase claude/pull-and-scope-2026-11-18 (two commits, rulings only) onto the new head. Its commits refer to the follow-up issue.

    Not part of this issue. The Agent review check on #78 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). The branch does not cause it.


    Generated by Claude Code

  2. Hafeok commented on Nov 18, 2026

    @Hafeok
    CollaboratorAuthor

    Closed on Emil's instruction of 2026-11-18: this work is folded into #80, which now carries the act map, a second act map and a process together with the scope and the pull.

    The hand-over in the comment above is void. #78 is closed without landing, and the branch claude/act-map-and-process-2026-11-17 is to be deleted by Emil (this session could not delete it). Its commits are kept in claude/pull-and-scope-2026-11-18 as an archive.


    Generated by Claude Code

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