[Soushi888]

SoushAI analysis. Drafted by Soushi's AI assistant, reviewed and posted by @Soushi888.

Summary

Holochain 0.7.1 changes every DNA hash, so a 0.7 build cannot reach any 0.6 network, and nothing told a user which network a build joins. This PR lists the hash of each role in the hApp (lobby, nondominium, hrea, and the base hashes of the group and ndo clone templates) in documentation/IMPLEMENTATION_STATUS.md, with the hc dna hash commands that reproduce them, and adds a "Network identity" stub to the 0.1.0 release notes in CHANGELOG.md that points to them.

Documentation only. Stacked on #130: review only this layer's diff. The hashes are those of this commit's build; the ones to publish are those of the tagged release build, so they are regenerated with the same commands when the release is cut. The hrea value is that of the hREA fork pin from #130 (Sensorica/hREA c4c44adb), and changes if that pin changes.

Changes

• documentation/IMPLEMENTATION_STATUS.md: new section "DNA hashes (Holochain 0.7.1 build)" after the multi-DNA architecture, with a table of the five roles and the five commands. The lobby command passes --network-seed nondominium-lobby-v1, the seed that workdir/happ.yaml sets for that role, so the value is the installed cell's hash.
• CHANGELOG.md: "Network identity" subsection under 0.1.0 saying this release joins a new network and linking the hash table.

Decisions

• Base hashes for group and ndo: these roles are deferred templates cloned at runtime with a unique seed, so the hash of the DNA file is the base, not a network anyone joins. The table says so.
• Hashes recorded at this commit: they change with any zome, manifest or toolchain change, so the section tells the release manager to regenerate them at the tag instead of presenting them as final.

How to test

Inside nix develop, after bun run build:happ, run the five commands in the new section and compare. The same build, repeated, printed the same hrea hash twice during the 0.7.1 work.

Documentation

This PR is documentation: documentation/IMPLEMENTATION_STATUS.md, CHANGELOG.md.

Related

Closes #161

• Stacked on: chore(deps): upgrade to Holochain 0.7.1 #130

Pre-open review

• Description: Summary stands alone, Closes #161, disclosure line first. Pass.
• Merge state: branched from the head of chore(deps): upgrade to Holochain 0.7.1 #130 (15ad9a5), no conflict. Pass.
• Code findings: documentation only, no code. The hashes were printed by hc dna hash on the build of the chore(deps): upgrade to Holochain 0.7.1 #130 head; the hrea value was reproduced twice. Pass.
• Documentation: this PR is the documentation. Pass.
• Tests: none apply. Pass.

[Soushi888]

SoushAI analysis. Drafted by Soushi's AI assistant, reviewed and posted by @Soushi888.

Review APPROVE at head 887b37c (the head after #130 merged and GitHub rebased this layer onto dev), merging under Soushi's explicit -mwr authorisation (2026-11-03 21:42).

• Docs only: a "DNA hashes (Holochain 0.7.1 build)" section in IMPLEMENTATION_STATUS.md and a "Network identity" stub in CHANGELOG.md. The body says the hashes belong to this commit's build and must be regenerated at the tag; the section tells the release manager so.
• Not verified by me: the hash values themselves. I did not run nix develop and hc dna hash, so they rest on the body's statement that the hrea hash was reproduced twice. The code they describe is unchanged by the squash of chore(deps): upgrade to Holochain 0.7.1 #130.
• CI at this head: build, rustfmt, nine Sweettest shards (including group, ndo_anchor and lobby) and e2e are SUCCESS. Confirmed retargeted to dev.
• Follow-up: feat(ui): run Nondominium as a Moss tool in weave dev mode #180 retargets to dev next.