Repository navigation
cybernode: the node leaves soft3 (proposals/cybernode.md C2–C4, executed 2026-10-27) - #406
Merged
Merged
Conversation
…ted 2026-10-27)
crate/src/{chain,genesis,node,wallet,network,bin}, crate/tests, deploy/,
audit/chain/ and the seven node specs now live in cyberia-to/cybernode (carved
with history from this branch). soft3 0.11 is the facade: pub use
cybernode::{chain,genesis,network,node,wallet}; the binary forwards the node
verbs to cybernode::cli for one release. cybernode is a sibling in
release/phase1.toml; the ladder, status, README, specs index and the agent rules
say rung 7 is cybernode; the proposal closes with § 9 and the receipt
cybernode/audit/move-2026-10-27.md.
cyberia-apparatus
added
queue
|
Director, session 152: reviewed. #406 lands on
|
cyberia-apparatus
added a commit
that referenced
this pull request
Oct 27, 2026
…de (#406) #406 moved the node into the cybernode crate but left crate/Cargo.lock without a cybernode entry, so soft3-tests and soft3-release (--locked) could not resolve. This lock is the one the build service resolved on the train's stand: diagnostic run 40519917254 (diag/cybernode-406-lock), soft3 at d49849a, cybernode at its pin 52538a6. Before sha256 cb7c91ab…, after e4e90704…; cargo test --locked and cargo build --release --locked both finished there. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cyberia-apparatus
added a commit
that referenced
this pull request
Oct 27, 2026
…rnode/rs (C4, #406) soft3#406 moved the node and its ~314 tests to cybernode/rs, so soft3-tests now runs only 2 tests. Run the node's suite from the cybernode checkout in the slot soft3-tests used to hold, blocked if the checkout is missing.
cyberia-apparatus
added a commit
that referenced
this pull request
Oct 27, 2026
…t-free again Both sides renamed CLAUDE.md to AGENTS.md (#406 and the main sync #423); GitHub's merge check reports the rename/rename as a conflict. The merged AGENTS.md is #407's (blob 3eedb35), a superset of release/phase1's (513321e): the crate/ row, the cybernode boundary, the node-status note. No other file overlaps; no code, specs or lock changes.
cyberia-apparatus
added a commit
that referenced
this pull request
Nov 1, 2026
…k since 611791b lives on cybernode release/phase1 release/phase1 added node work after 611791b, the base #406 was cut from. That work is ported to cybernode release/phase1 (cybernode#2, #3, #4 → 5a2f4a2): soft3 a6e9b8f, 6868695 (P2 settlement halt), 8dd2a91 (P2a), 27f41e9 (P3 stand, deploy/chain/agent-a), 66029b2 (P3d), 687f86b, 981776a, 4e556ab, daac4ab (P3e soft3-chain-check → cybernode-check), c898465, f191052 (pussy pins), 2c21b25, 2393617, 3f4f5f1 (P3b pussy-rc genesis). Each file's delta equals soft3's after the move's renames. Resolution: - #406's deletions of the moved node code win (crate/src/{chain,genesis,node}, crate/tests/pussy_identity.rs, deploy/chain/ with agent-a/). - crate/src/bin/soft3.rs stays the facade: `soft3 genesis` and `soft3 conformance` forward to cybernode::cli::run, which carries the pussy-rc help text and the pins check since cybernode 5a2f4a2. - crate/Cargo.toml: the cybernode path dependency plus release/phase1's ureq, serde, the mudra dev-dependency, the hemera opt-level and the P2a overflow-checks profile; the profile also names cybernode, because cargo reads profiles from this root manifest only and the node's code is that crate now. - crate/Cargo.lock is release/phase1's, not regenerated. - release/phase1.toml: cybernode pinned at release/phase1 5a2f4a2. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cyberia-apparatus
added a commit
that referenced
this pull request
Nov 1, 2026
cybernode: land #406 on release/phase1 with the registry fix its drift gate asks for
|
Landed on The release/phase1 node work after Still open:
|
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
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.
Executes the cybernode proposal on the integration branch (the owner, 2026-10-27: close it fully now).
crate/src/{chain,genesis,node,wallet,network,bin},crate/tests),deploy/,audit/chain/and the seven node specs now live in cyberia-to/cybernode, carved from this branch with 144 commits of history; chain, genesis, node, wallet, node.rs and network.rs are byte-identical — receipt:cybernode/audit/move-2026-10-27.md.soft30.11 is the facade:pub use cybernode::{chain, genesis, network, node, wallet}; the binary forwards the node verbs tocybernode::clifor one release.cybernodeis a sibling inrelease/phase1.toml; the ladder (soft3.org/layers),status.md, README,specs/READMEand the agent rules say rung 7 is cybernode; the private operations repository is renamed apparatus (§ 7.1 decided).Not green yet, and not because of this PR: on 2026-10-27 no sibling set on origin resolves the crate's dependencies — the same for
crateon this branch before the move (hemera 0.4 / bbg 0.3 tier half-ported: cybergraph#23,port/l4-*-phase1, tok). The receipt lists every conflict. The fleet and the conformance vectors run the day the tier lands; the byte-identity makes that a formality.Conflicts to expect for the director: #243 (requirements pilot on
specs/chain.md, nowcybernode/specs/chain.md), #350, #234, #167 touch moved files — rebase onto cybernode.