D1.24: remove the Rust tree from main #165

Activity

1. Hafeok commented on Nov 3, 2026

   

   Hafeok

   on Nov 3, 2026 – with Claude

   CollaboratorAuthor

   More actions

   Plan, for approval

   No file is written until you approve. The plan has nine parts:

   • §0 the preconditions I checked;
   • §1 to §6 the PR (claude/lucid-hamilton-jxk6pv, Refs #165), one commit per numbered item;
   • §7 the decision-driven-design PR;
   • §8 the dispositions;
   • §9 questions.

   0. Preconditions, checked

   • rust-final on GitHub is tag object d0cf1f1ec40eb55c271b8d4dadfefcd260c03312. It points at 70395dfe317cb9a00665433813766ca763f3c58a, and GitHub reports verified: true, reason: valid.
   • origin/main is 70395dfe317cb9a00665433813766ca763f3c58a.
   • product-cli-adrs.md is in hand. The PR copies it unchanged and adds no ADR text of its own.
   • I read:
     • the definition at decision-driven-design fcda5ed (Draft 4, all of it);
     • Writ 6737ac9 ADR 0008 and docs/traceability/;
     • Varve 3024c7a AGENTS.md, eng/ and releases/ with docs/releases.md;
     • this repository at 70395df.

   1. Removal: one commit, nothing edited first

   chore: remove the Rust tree from main (D1.24) deletes these paths, with their tracked file counts at 70395df (1,935 of 1,939 files):

   • Workspace and crates:
     • Cargo.toml (1), rust-toolchain.toml (1), deny.toml (1), dist-workspace.toml (1), .cargo/ (1), xtask/ (11), dagger/ (6);
     • product-core/ (232), product-mcp/ (115), product-cli/ (93);
     • ddd-core/ (48), ddd-lsp/ (36), ddd-mcp/ (15), ddd-cli/ (106);
     • ledger/ (30), ledger-core/ (143), ledger-cli/ (114);
     • spec-core/ (31), spec-cli/ (24), spec-mcp/ (8), spec-flow/ (43, .NET);
     • eval-core/ (25), eval-dotnet/ (24, .NET), ground-cli/ (8).
     • There is no Cargo.lock at 70395df, so there is nothing to remove for it.
   • Content: schema/ (28), spec/ (38), conventions/ (12), examples/ (2), scripts/ (13), docs/ (58).
   • Stores and agent configuration: .product/ (53), .decisions/ (189), .ddd/ (411), .claude/ (7), .mcp.json, .htmlvalidate.json, .stylelintrc.json.
   • CI: .github/workflows/product-ci.yml, publish-mcp.yml and release.yml.
   • CLAUDE.md.
   • Beyond your list. These two paths are not in the brief, but "main contains only what deliverable 2 adds" requires removing them:
     • .gitignore;
     • .github/copilot-instructions.md. AGENTS.md becomes the single source for agents.
   • Kept in this commit and replaced later: LICENSE and README.md. Each is rewritten in its own commit (§2), so the relicensing and the README rewrite each show as a diff.

   2. Additions, in this order

   2. docs: AGENTS.md, the single source for agents (ADR-0007). It covers:

      • what the repository is: the tool, its ADRs and its tests;
      • where the definition lives, and that a definition change merges in decision-driven-design first, with its commit cited here (D1.24);
      • the gates, and how to run them locally;
      • commit rules:
        • signed;
        • Refs #N;
        • Signed-off-by: Emil Okkels Klein <emil@okkels-klein.dk>;
        • no model identifier anywhere, Co-Authored-By trailers and author names included;
        • Claude-Session: kept, as in Writ, because it is a session URL and names no model;
      • the session record (ADR-0007 D2);
      • the never list (question 1).

   3. docs: CLAUDE.md points to AGENTS.md: one line.

   4. docs: README.md for the rewrite:

      • two paragraphs from chapter 1: the promise and its consequences;
      • that the Rust tool is frozen at rust-final and its published releases (through v0.7.0) keep working;
      • a link to the definition.

   5. licence: Apache-2.0 replaces MIT; add NOTICE:

      • LICENSE is the canonical Apache-2.0 text from apache.org, unedited;
      • NOTICE names the copyright holder, and states that everything at rust-final and before remains under the MIT licence it was published with.
      • The PR states this, and asks you to confirm the relicensing in review as the holder named in the MIT file ("Emil Klein").

   6. docs(decisions): the collected ADR text of 2026-11-03 adds docs/decisions/collected-2026-11-03.md, byte-identical to the attachment. The PR states its sha256.

   7. docs(decisions): ADR-0001 to ADR-0012, split from the collected file adds the twelve file names from the brief.

      • Each file is its section: ## ADR-… becomes # ADR-…, and ### … becomes ## …. Nothing else changes, including the trailing newline. The --- separators belong between sections, so no file carries one.

   8. docs(decisions): the Draft 4 notes on ADR-0001, 0008, 0009 and 0011. This is a separate commit, so the notes are a reviewable diff on top of the verbatim split.

      • Each note sits after the status lines and before ## Context.
      • Its text is the preamble's bullet with the **ADR-NNNN.** lead removed and its sub-bullets de-indented one level. For example:

        > **Note (2026-11-03, Draft 4)**
        >
        > D1 now reads `docs/decisions/ADR-####-<slug>.md` (D1.22). The first PR carries ADR-0001 to ADR-0012.
        

   9. docs(decisions): README, the interim rule (D1.22). It says:

      • review keeps ADR discipline, under Writ ADR 0008's interim rule;
      • writ import reads these files once Writ Split tests/integration/mod.rs by topic; add tests/ file-length fitne… #7 exists;
      • every package entry carries Adr=.

   10. ci: gates.yml with the checks in eng/gates/. They are Bash plus git, jq and curl, which the runner has, so they add no toolchain file. Five jobs run on every pull_request against main, with permissions: contents: read, pull-requests: read:

       • commits, over every commit in base..head, checks:

         • a Refs #N line;
         • a well-formed Signed-off-by: naming a person, never a noreply or agent address;
         • no model identifier in the message, the author or committer name or email, or any trailer. The pattern covers vendor model ids (claude-…, gpt-…, gemini-…, o1/o3/o4-style, llama…, mistral…), the product family names followed by a version number, and any Co-Authored-By: naming an AI vendor address. Claude (Emil) and Claude-Session: pass.

       • signatures reads each PR commit's verification from the REST API and fails on any verified: false, printing the reason.

       • adr-shape checks each docs/decisions/ADR-NNNN-*.md:

         • an H1 # ADR-NNNN: … whose number matches the file name;
         • a **Status:** line;
         • ## Alternatives considered;
         • ## Consequences.

         Any other file in the directory fails, except README.md and collected-*.md, so nothing escapes the shape check by its name.

       • adr-text rebuilds each ADR file from the collected file and compares bytes. It takes the section, promotes its headings outside code fences, and inserts the preamble's note for the four noted ADRs. It fails on any byte difference, on a note in any other ADR, or on a missing note.

       • no-toolchain fails if any Rust, Node or Python toolchain file is at the root:

         • Rust: Cargo.toml, Cargo.lock, rust-toolchain, rust-toolchain.toml, .cargo/;
         • Node: package.json, the npm, yarn, pnpm and bun lockfiles, pnpm-workspace.yaml, .nvmrc, .node-version, deno.json;
         • Python: pyproject.toml, setup.py, setup.cfg, requirements*.txt, Pipfile, Pipfile.lock, poetry.lock, uv.lock, .python-version, tox.ini;
         • and .tool-versions.

       A sixth job, selftest, plants a failing case for each check in a scratch repository on the runner and passes only if every check fails on its case. It keeps the "fails on a planted case" property on every run. The red runs to show in the PR are in question 3.

       • CI kept: none. CI added: gates.yml only.
       • No .NET solution, project, global.json or SDK pin. Those come in slice 0 (ADR-0002/0003/0004).

   11. releases: <descriptor> in Varve's shape (format: 1, version, title, date, basis, summary).

       • basis names issue 165, rust-final (tag object d0cf1f1…, commit 70395df), and the edition: sdlc: edition 1, owl:versionIRI <https://decision-driven-design.dk/ns/sdlc/1>, hash pending until decision-driven-design tags it (D1.20).
       • The summary says no Rust release follows rust-final. The tool's last Rust release is v0.7.0.
       • No accepted-by: that line is yours. The version is question 4.

   12. docs(traceability): 2026-11-03-issue-165-rust-removal.md, in Writ's shape. It holds:

       • the prompt, verbatim;
       • the tool;
       • what was read, with SHAs;
       • the approved plan;
       • the commits;
       • the checks and their results;
       • deviations, with reasons.

       The model field is question 2.

   3. Gate, reported in the PR

   • gates.yml is green on the head.
   • Every SHA's verification is read through the API and pasted in.
   • git ls-tree -r --name-only HEAD is pasted in. It should list only:
     • AGENTS.md, CLAUDE.md, README.md, LICENSE, NOTICE;
     • docs/decisions/ (twelve ADRs, the collected file, README.md);
     • docs/traceability/…;
     • releases/…;
     • .github/workflows/gates.yml;
     • eng/gates/*.
   • The description says the removed tree stays readable at rust-final, and that MIT governs everything there.

   4. decision-driven-design: one commit, signed, Basis: DDD-dec-72, not merged by me

   In applications/sdlc/product-cli/product-definition.md:

   • Header: "Draft 4 adds D1.16 to D1.24" becomes "… D1.16 to D1.25". The sentence "D1.24 supersedes D1.23." becomes "D1.24 supersedes D1.23, and D1.25 adds step 0 to the order of work."
   • Table:
     • the rust-final row becomes **met**: tag object d0cf1f1ec40eb55c271b8d4dadfefcd260c03312;
     • a new row follows it: | D1.24 | the Rust tree removed from main | product-cli | … |, either met with the merge SHA or in review with the PR number (question 5);
     • the README row is unchanged.
   • Chapter 7: step 0 goes in as the new first item, verbatim from the brief.
   • I run python3 scripts/ci.py green after pip install -r scripts/requirements.txt.

   5. Disposition: executed only after you approve this list

   PRs: close unmerged, and delete no branch. These are #143 and #154 to #164 (12 PRs). Each gets this comment:

   Closed unmerged under D1.24: the Rust tree left main in #, and this branch's work stays readable at rust-final and on its branch. The ledger is Writ's authority graph now (definition chapter 8); writ import reads .decisions/ once, at the tag.

   Issues: close as not carried (30). Each gets a comment citing D1.24 and chapter 8, and is closed not_planned.

   • Ledger, keys, namespaces (28): I3: mailto: and bare addresses parse to one identity; files and hashes keep the bare form #64, I5: Revocation becomes its own signed entity; acceptances are immutable #66, I7: Verbs speak keys; supersede in one act carrying the key #68, I11: ledger review --diff <ref> — cited decisions awaiting acceptance #72, I12: ledger import --from docs/decisions/*.md (the interim set files) #73, I13: accept --commit — opt-in signed, signed-off commit #74, I14: History export — ledger:Commit and prov:wasInformedBy #75, I15: Analyzers' reader compatibility with the ledger export (tracking) #76, Four format 1 change-sets carry revisit_if; §3.7 calls that a schema fault and format_faults has no row for it #81, Signed grants and grant acceptances (D5 b) #82, rotate-genesis: replace the store's genesis grant #83, accept refuses in a namespace without a policy #84, accept, accept --batch and the inbox read authority from the union of branch and base #94, Retiring a landed entity that fails L011 or A006, by a valid revocation; the inbox offers revoke and re-accept #95, Readiness check: a PR that adds a decision awaiting acceptance is red #101, Key lifecycle across namespaces, part 1: a key is bound once per namespace; a close ends the key #104, Key lifecycle across namespaces, part 2: rotate/revoke every namespace in one act; notice for a split state #105, The dsse check orders acts by timestamp where the ssh check uses landing order (D6) #106, and Load every store from ns/<ns>/; refuse flat paths at the verified commit #144 to Re-lay out this repository's store and regenerate its exports #153.
   • Design systems and the How (2): Design-system coupling: scope AIO coverage to the contexts a UI step targets #60 and Reification check ignores the bound design-system manifest (two disconnected representations) #61.

   Issues: propose re-filing (2). I re-file nothing myself and leave both open for you.

   • Decider logic: branching outcomes (one command, alternative emitted events) #58, Decider branching outcomes. It belongs to step 2, the logic media type's specification page and suite, because choosing an emission by condition is a grammar question. It is exercised at step 6, the simulator. Its "every declared emitted event is produced by some scenario" belongs with W3 coverage.
   • Value objects: persist attributes and link them to the entities/events/commands that use them #59, value objects as elements. It belongs to step 4, nodes and validate. The typing needs an edition answer at step 1: a field typed by a value object, via sdlc:fieldType/sdlc:Field (DDD-dec-64 P-3). The "unused value object" finding is a W4 shape for decision-driven-design (G0 (resumed): bootstrap the registry from code #50).

   6. Questions

   1. The never list. I don't hold the Product-Cli project prompt, only this session's prompt. Unless you paste its constraints, I'll draft the list from:

      • this prompt's Rules;
      • chapter 7's Constraints;
      • chapter 8's "Not in scope" and "No authority, ever";
      • W10;
      • ADR-0006 and ADR-0007.

   2. The model in the traceability record. Writ's shape names the model, but this session may write no model identifier into anything pushed. I propose to use ADR 0008's own provision: the record states the tool will not write it, and you fill it in.

   3. Real red runs. The planted cases need commits that break the rules on purpose (no Refs, no sign-off, a fake model id such as gpt-planted-0), plus a malformed ADR, an edited ADR byte and a root Cargo.toml. The commits are still signed with this key. The signature case is signed but committed as planted@example.invalid, so GitHub reports it unverified. My proposal:

      • seven branches planted/<check> off the PR head;
      • one draft PR to main each, closed after its red run;
      • the run links pasted in the PR;
      • branches kept.

      That needs your permission to push those branches. The alternative is selftest evidence only.

   4. The descriptor's version. It must follow v0.7.0. I propose releases/v0.8.0-preview.1.yaml, with nothing cut until slice 0 brings a release path. Or would you rather start the rewrite at v1.0.0-preview.1?

   5. The decision-driven-design PR's single commit. If that PR opens before your merge here, updating the row afterwards means a second commit, because I won't rewrite the branch. I propose to open it right after your merge, with the row met and the merge SHA, in one commit. If you want it open earlier, I'll mark the row "in review" and add the update as a second commit.

   ---

   Generated by Claude Code
2. Hafeok

   added 3 commits that reference this issue on Nov 3, 2026

   docs(traceability): the relicensing confirmation, as an addendum

   ...

   d4ea57b

   docs(traceability): the licence boundary, in the addendum

   ...

   a9df5c4

   Refs #165

   ...

   53bd547
3. Hafeok commented on Nov 3, 2026

   

   Hafeok

   on Nov 3, 2026 – with Claude

   CollaboratorAuthor

   More actions

   Outcome

   • D1.24: remove the Rust tree from main #166 merged. main was fast-forwarded to 53bd54758ba71f7a810f91ddf3a6c83d5e653145. Its 15 commits all verify on GitHub (valid), and gates.yml is green on the head.

   • Disposition, executed as approved:

     • PRs: Record ruling 102: what the genesis holder's revoke names #143 and Load every store from ns/<ns>/; refuse flat paths at the verified commit (issue 1) #154 to Close-out: namespaces, layout and authority (issues 1 to 10) #164, 12 in all, closed unmerged, each with a comment citing D1.24 and rust-final. All 12 branches are kept.
     • Issues closed as not carried (not_planned), each with a comment citing D1.24 and chapter 8. 30 in all:
       • I3: mailto: and bare addresses parse to one identity; files and hashes keep the bare form #64, I5: Revocation becomes its own signed entity; acceptances are immutable #66, I7: Verbs speak keys; supersede in one act carrying the key #68, I11: ledger review --diff <ref> — cited decisions awaiting acceptance #72 to I15: Analyzers' reader compatibility with the ledger export (tracking) #76, Four format 1 change-sets carry revisit_if; §3.7 calls that a schema fault and format_faults has no row for it #81 to accept refuses in a namespace without a policy #84, accept, accept --batch and the inbox read authority from the union of branch and base #94, Retiring a landed entity that fails L011 or A006, by a valid revocation; the inbox offers revoke and re-accept #95, Readiness check: a PR that adds a decision awaiting acceptance is red #101, Key lifecycle across namespaces, part 1: a key is bound once per namespace; a close ends the key #104 to The dsse check orders acts by timestamp where the ssh check uses landing order (D6) #106, and Load every store from ns/<ns>/; refuse flat paths at the verified commit #144 to Re-lay out this repository's store and regenerate its exports #153: the ledger, keys and namespaces;
       • Design-system coupling: scope AIO coverage to the contexts a UI step targets #60 and Reification check ignores the bound design-system manifest (two disconnected representations) #61: design systems and the How.
     • Left open, proposed for re-filing:
       • Decider logic: branching outcomes (one command, alternative emitted events) #58: step 2, the logic grammar, exercised at step 6;
       • Value objects: persist attributes and link them to the entities/events/commands that use them #59: step 4, with an edition question at step 1.

   • decision-driven-design: mindovermachine-dev/decision-driven-design#57, one signed commit, da453f1, verified. Its contents:

     • the rust-final row met;
     • the "Rust tree removed from main" row met at 53bd547;
     • step 0, D1.25;
     • the D1.21 lift-map correction.

     It carries Basis: DDD-dec-72, and scripts/ci.py passes all gates. It waits for your merge.

   This issue stays open for you to close.

   ---

   Generated by Claude Code
4. Hafeok

   added 2 commits that reference this issue on Nov 3, 2026

   product-cli definition: D1.24 met, D1.25 adds step 0, D1.21 lift map …

   ...

   a052ed9

   product-cli definition: D1.24 met, D1.25 adds step 0, D1.21 lift map …

   ...

   799cbe8
5. Hafeok commented on Nov 3, 2026

   

   Hafeok

   on Nov 3, 2026

   CollaboratorAuthor

   More actions

   Done: #166 fast-forwarded main to 53bd547; definition updated in decision-driven-design #57.
6. Hafeok

   closed this as completedon Nov 3, 2026