Project update: 15 November 2026. GitHub change #15: merged into the repository. The underlying protocol remains draft and unaudited.
A Rust command now reconstructs annotated version tags from Secure Net's recorded package history.
Why we made this change
Good release discipline should allow contributors to identify exactly which code corresponds to each version. The tagging tool reconstructs known version points without overwriting tags that already exist. The implementation notes also explain that pushing tags requires suitable repository permissions, so creating tags locally does not prove they are published remotely.
The engineering record
The original pull request records the following technical scope and evidence. Some forward-looking notes in the record reflect the state of the work when the request was opened, rather than its status today.
Adds cargo run -p secure-net-tools -- tag. It gives every version in package.json's history an annotated tag vX.Y.Z at the last commit that carried that version, and leaves existing tags alone. It works like Commonveil's release.mjs --tag. The README says to run it after each release and then push the tags.
I checked it by deleting my hand-made tags and recreating them with the tool: all ten (v0.1.0 to v0.7.0) came out identical.
The tags themselves need pushing from a clone with tag-push rights: this session's git proxy refuses tag pushes (HTTP 403).
The wider direction
The Comutability approach is open source with human accountability. AI can help research, design, write code and test it, but a merged change is not the same thing as an independently audited product. Secure Net is explicitly described as a draft in its public README. Its use in a sensitive situation should wait for qualified cryptographic review.
What happens next
Keep tag creation and tag-push permissions under human control, with documented checks before any public release announcement.

