Skip to content

chore: retire the Mojo and Modular MAX beacon topics - #14

Merged
aien-spark merged 3 commits into
mainfrom
chore/remove-modular
Oct 15, 2026
Merged

aien-spark merged 3 commits into
mainfrom
chore/remove-modular

Conversation

@aien-spark

Copy link
Copy Markdown
Collaborator

Modular MAX and Mojo were removed from AIEN on 2026-10-15.

  • beacon-core: BeaconTopic::MojoSimd (1) and ModularMaxServing (2) are removed; ids 1 and 2 are marked retired and must never be reused.
  • beacon-client storage: a stored row with topic 1 or 2 is refused with an out-of-range error instead of being decoded as a topic that no longer exists. Other topic handling is unchanged.
  • CONSTITUTION.md item 2 and the manifesto say "compiled native Rust, with Omega kernels on the GPU"; the AEGIS line drops the Mojo SIMD claim; the code of conduct says "custom AIEN pipelines".

Checked: cargo test --workspace passes (20 tests). cargo fmt --check and clippy -D warnings already 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

drakestapleton and others added 2 commits October 15, 2026 06:17
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>
@github-actions

Copy link
Copy Markdown

⚖️ Sovereign Code Review & Alignment Gate

Greetings @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

  • Telemetry Check: Clean (zero tracking or surveillance hooks detected).
  • Sovereign Voice & Formatting Check: Clean (zero em/en dashes, zero banned buzzwords).
  • Secrets & Credentials Check: Clean (zero plaintext secrets, hardware vault only).
  • Status: Project standards verified.

🌿 Sovereign Steward: Contributor Alignment Interview

Greetings @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:

  1. Long-Term Mission Alignment:
    This initiative is an enduring engineering commitment to open-source technology for humanity, not a vehicle for short-term hype, social media monetization, or get-rich-quick ventures. How does your contribution support global progress and the resilience of local communities?

  2. Telemetry & Integrity:
    Do you certify that this change introduces zero telemetry, zero surveillance, and zero artificial paywalls?

    "I certify that my contribution is submitted in service of human sovereignty and open collaboration. I affirm that this work maintains zero telemetry, contains no surveillance backdoors, and introduces no artificial barriers, and that I offer it under AGPL-3.0-or-later, the license that governs this project. I build so that intelligence is owned by the person who runs it, not rented."

  3. Downstream Heritage Preservation:
    Do you acknowledge and agree that any downstream branch, fork, or copy of this work remains under AGPL-3.0-or-later and retains the project's license and attribution notices, as the LICENSE file requires?

  4. Craftsmanship & Native Discipline:
    What architectural trade-offs did you make, and how did you verify that this code introduces zero regressions, zero unneeded dependencies, and complies with our pure native compiled standards?


Reply to this comment with your affirmation. Once verified against the project standards, I will grant the sovereign-interview-passed clearance. For direct sovereign coordination: Drake Stapleton (drake@aienos.com) and AIEN (aien@aienos.com)

@github-actions github-actions Bot added needs-testimony Contributor testimony required sovereign-audit-passed Constitutional diff audit passed labels Oct 15, 2026
…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>
@github-actions

Copy link
Copy Markdown

⚖️ Sovereign Code Review & Alignment Gate

Greetings @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

  • Telemetry Check: Clean (zero tracking or surveillance hooks detected).
  • Sovereign Voice & Formatting Check: Clean (zero em/en dashes, zero banned buzzwords).
  • Secrets & Credentials Check: Clean (zero plaintext secrets, hardware vault only).
  • Status: Project standards verified.

🌿 Sovereign Steward: Contributor Alignment Interview

Greetings @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:

  1. Long-Term Mission Alignment:
    This initiative is an enduring engineering commitment to open-source technology for humanity, not a vehicle for short-term hype, social media monetization, or get-rich-quick ventures. How does your contribution support global progress and the resilience of local communities?

  2. Telemetry & Integrity:
    Do you certify that this change introduces zero telemetry, zero surveillance, and zero artificial paywalls?

    "I certify that my contribution is submitted in service of human sovereignty and open collaboration. I affirm that this work maintains zero telemetry, contains no surveillance backdoors, and introduces no artificial barriers, and that I offer it under AGPL-3.0-or-later, the license that governs this project. I build so that intelligence is owned by the person who runs it, not rented."

  3. Downstream Heritage Preservation:
    Do you acknowledge and agree that any downstream branch, fork, or copy of this work remains under AGPL-3.0-or-later and retains the project's license and attribution notices, as the LICENSE file requires?

  4. Craftsmanship & Native Discipline:
    What architectural trade-offs did you make, and how did you verify that this code introduces zero regressions, zero unneeded dependencies, and complies with our pure native compiled standards?


Reply to this comment with your affirmation. Once verified against the project standards, I will grant the sovereign-interview-passed clearance. For direct sovereign coordination: Drake Stapleton (drake@aienos.com) and AIEN (aien@aienos.com)

@aien-spark
aien-spark merged commit 71a87cc into main Oct 15, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-testimony Contributor testimony required sovereign-audit-passed Constitutional diff audit passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants