docs: closed networks shipped — drop the "awaiting implementation" claims#18
Merged
Conversation
…aims `docs/NETWORK-TYPES.md` opened with "Status: design — not yet implemented" and the README's doc-index line repeated the framing. That hasn't been true since PR #12 landed on main and got bundled into v0.1.2: NetworkKind + Role types in `crates/myownmesh-core/src/network_state.rs`, signed `network_state_*` wire frames, engine-side authority enforcement on every inbound frame, and a `closed_network_governance.rs` integration test covering the ratify + deny flow end-to-end. Rewrite the NETWORK-TYPES status block to point at the actual implementation surfaces and keep the design rationale that follows intact. Update the README doc-card subtitle to match.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/NETWORK-TYPES.mdstill opens with "Status: design — not yet implemented." and the README's doc-index line atREADME.md:262repeats the framing. That hasn't been true since #12 landed and got bundled into v0.1.2:crates/myownmesh-core/src/network_state.rsdefinesNetworkKind::{Open, Closed},Role::{Member, Controller, Owner}, and signed-transition primitives under themyownmesh-network-state-v1:domain tag.crates/myownmesh-core/src/protocol/; the engine enforces authority on every inboundnetwork_state_*frame and drops quorum-violating proposals with a diag entry.JoinedNetworkexposes the propose / sign / deny / split surface (crates/myownmesh-core/src/handle.rs:292).tests/closed_network_governance.rsexercises the ratify + deny lifecycle end-to-end.Rewrites the NETWORK-TYPES status block to point at the actual implementation surfaces (with relative links so the doc still reads inside the repo and on GitHub), preserves the design rationale that follows, and updates the README doc-card subtitle to match.
Found via the myownmesh.net rewrite — the landing page was sourcing the "closed networks unimplemented" claim from these docs and was wrong as a result (see mrjeeves/myownmesh.net#3).
Test plan
grep -rn "awaiting implementation\|design — not yet implemented" --include="*.md" .returns no hits.crates/myownmesh-core/src/network_state.rsfrom the rendered MD opens the file).README.md:262reads "(role tiers, signed transitions, split + recovery)" not "(awaiting implementation)".Generated by Claude Code