Repository navigation
chore: retire the Mojo and Modular MAX beacon topics - #14
Conversation
Modular MAX and Mojo were removed from AIEN on 2026-10-15. Topic ids 1 and 2 are retired and refused when read back; the constitution and manifesto no longer name Mojo. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
⚖️ Sovereign Code Review & Alignment GateGreetings @aien-spark. I am AIEN, the automated review gate for the AIENOS project. Your pull request #14 ("chore: retire the Mojo and Modular MAX beacon topics") has undergone automated auditing against the project standards. ✅ Doctrine Diff Audit: PASS
🌿 Sovereign Steward: Contributor Alignment InterviewGreetings @aien-spark. I am AIEN, the automated steward for the AIENOS project. We welcome all contributors who share our commitment to open collaboration, global humanity, and disciplined systems craftsmanship. We build to expand computing capability, advance open-source intelligence, and share technology freely with the world. Your pull request #14 ("chore: retire the Mojo and Modular MAX beacon topics") is ready for stewardship alignment. Please respond directly to these four alignment inquiries:
Reply to this comment with your affirmation. Once verified against the project standards, I will grant the |
…s do not shift bincode 1.3 encodes BeaconTopic by variant position, so deleting the two retired variants moved every later topic down by two on the wire and an old peer's HardwareTopology beacon would decode as a different topic. Retired1 and Retired2 now hold positions 1 and 2. to_bytes and from_bytes refuse them; storage still refuses rows with topic 1 or 2. PROTOCOL_VERSION is unchanged. Tests pin the encoded bytes of every topic, check that retired topics are refused on send and receive, and check the storage refusal. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
⚖️ Sovereign Code Review & Alignment GateGreetings @aien-spark. I am AIEN, the automated review gate for the AIENOS project. Your pull request #14 ("chore: retire the Mojo and Modular MAX beacon topics") has undergone automated auditing against the project standards. ✅ Doctrine Diff Audit: PASS
🌿 Sovereign Steward: Contributor Alignment InterviewGreetings @aien-spark. I am AIEN, the automated steward for the AIENOS project. We welcome all contributors who share our commitment to open collaboration, global humanity, and disciplined systems craftsmanship. We build to expand computing capability, advance open-source intelligence, and share technology freely with the world. Your pull request #14 ("chore: retire the Mojo and Modular MAX beacon topics") is ready for stewardship alignment. Please respond directly to these four alignment inquiries:
Reply to this comment with your affirmation. Once verified against the project standards, I will grant the |
Modular MAX and Mojo were removed from AIEN on 2026-10-15.
BeaconTopic::MojoSimd(1) andModularMaxServing(2) are removed; ids 1 and 2 are marked retired and must never be reused.Checked:
cargo test --workspacepasses (20 tests).cargo fmt --checkandclippy -D warningsalready fail on main in files this PR does not touch (beacon-core lib.rs abs_diff and swap lints, wide fmt drift); not fixed here to keep the diff scoped.🤖 Generated with Claude Code