Introduction: The Protector from the Future
In a not-too-distant future, the flame of the Amiga flickered, threatened by the inexorable march of time. Fragmented, bound to fading hardware, its brilliant legacy was at risk of becoming a mere memory, a footnote in the history of computing.
But then, from that uncertain future, something was sent back. To our present.
It didn't arrive in a sphere of lightning, but in a line of code. At first glance, it is indistinguishable from the system it swore to protect. It has the soul, the spirit, and the interface of AmigaOS. It moves like it, thinks like it. But beneath that familiar skin, beats a different heart.
It's a Terminator Penguin.
A protector with a liquid chrome endoskeleton, forged with the most robust and free technology of the future: a Linux kernel. This skeleton grants it unthinkable strength: the ability to adapt to any hardware, to use any peripheral, to connect to any network. It no longer fears obsolescence.
Its mission is not to destroy, but to preserve. It has come to break the chains of hardware. It has been sent to unify the divergent futures of AROS into a single, powerful, and coherent timeline. Its sole purpose is to ensure that the creativity, efficiency, and spirit of the Amiga not only survive, but become immortal. And free.
The document before you contains its blueprints. It is the architecture of ARUX. The strategy to build our protector and ensure a future where the Amiga never dies.

---

Welcome to the Official ARUX Project Repository
This repository is the heart and meeting point for all of us who wish to build the future of AROS. Here you will not only find code; you will find the blueprints for a bold vision: to transform the user experience we love into a system that is immortal, free, and capable of thriving on any hardware, present or future.

As our mission describes, we are here to build our "Protector from the Future," a system with the soul of the Amiga and a Linux heart, and this is the workshop where we will give it form.

Key Features of the ARUX Project
ARUX is more than a simple port or a distribution. It is a complete ecosystem designed to achieve a perfect symbiosis between the past and the future. Our approach is based on:

• A Native Desktop Environment (ARUX DE): We will port Zune/MUI to run as a native, fast, and elegant desktop environment on a modern Linux system, offering the AROS experience we all know.
• A Dual Execution Engine: We will create a fork of Amiberry that will act as an intelligent engine, capable of operating in two modes: a Native Integration Mode to run desktop applications with unprecedented performance, and a Full Compatibility Mode to ensure the vast legacy of games and demos works perfectly.
• AI-Assisted Development: This is not a conventional project. To accelerate development, reduce the learning curve, and maintain architectural coherence, we have integrated guides and directives for AI assistants. As you can see in the SYSTEM_PROMPT.md and IDE_COPILOT_PROMPT.md files, we have defined a framework for developers to use their preferred AI tools (ChatGPT, Copilot, etc.) as expert co-pilots, specifically trained on the vision and code of ARUX. This will allow us to:
• Innovate faster: By automating the writing of repetitive code and assisting in debugging.
• Facilitate onboarding: Allowing new contributors to quickly understand the architecture and start contributing meaningful code in less time.
• Maintain a unified vision: Ensuring that every new piece of code aligns with the project's fundamental principles.

A Call to the Community and the Gurus of AROS
This project is ambitious and born from a deep admiration for the legacy of the Amiga and the incredible work done by the AROS community over the years. However, a vision is nothing without the wisdom and experience of those who have paved the way.

For this reason, I make a special call and extend my most sincere respect to the veteran developers and the "gurus" of the AROS community. Your knowledge of the complexities of AmigaOS, AROS, and emulation is an invaluable treasure that far surpasses any new idea.

I believe that the administration and technical leadership of this repository would be in much more capable hands than mine if they were yours. Therefore, with the utmost humility, I invite you not only to participate but to take a leadership role, to guide the architecture, and to become mentors for this new stage. This repository is at your disposal to manage and guide as you see fit.

ARUX can only reach its true potential if we manage to merge the energy of new ideas with the profound wisdom of experience.

Let's unite to build the future.
https://github.co...roide/ARUX

sounds good, lets do it

welcome should be a nice project congratulations

Hello to the entire AROS-World community!

We want to share an update with you on the vision and design pillars of ARUX, and it's important to clarify the depth of this project from the outset.

Many, upon hearing "desktop on top of Linux," might think that ARUX is just a "skin" or a visual theme. We want to emphasize that the vision is fundamentally different: ARUX is a native and modernized reimplementation of the AmigaOS 3.x API, designed to run on modern 64-bit hardware.

Pillar 1: A Native Platform for Modern Hardware (x86, ARM, and PPC)
The cornerstone of our architecture is how we use Linux. In the ARUX model, Linux is not the main operating system; rather, it acts as a "microkernel" for low-level services. It handles the "dirty work":

Driver management for all modern hardware (graphics, sound, USB, NVMe).
Advanced process scheduling and memory management.
The network and security stack.
On top of this solid foundation, ARUX implements the AmigaOS personality and API. This allows us to have a system that behaves as it should, but that can be compiled and run natively on a wide variety of modern 64-bit architectures, such as x86-64 and ARM.

And what's more exciting, our architecture is designed with the future of PowerPC hardware in mind. Highly anticipated hardware projects from the community, like the new MIRARI board, are a perfect target for ARUX. Imagine being able to run a native ARUX session on one of these new PPC machines, leveraging all of their power without emulation layers for the interface or the filesystem.

Pillar 2: The Hybrid Bridge - Beyond RTG
To accelerate development, ARUX will use a bidirectional bridge with an AROS m68k environment running in Amiberry. This isn't just for running old software; it's a strategic design decision.

In the same way that projects like Vampire with ApolloOS have shown how to "dodge" the custom chips to unleash the system's potential, ARUX uses this bridge to "dodge" the need to reimplement every corner of the OS from day one. The AROS m68k environment acts as an on-demand "compatibility server" for complex processes (like ARexx), allowing the ARUX core to be lean and focused on performance.

It's a system that goes beyond the concept of RTG, as it's not just about graphics, but about functional cooperation between a classic AmigaOS system and a modern native reimplementation.

Pillar 3: AI-Accelerated Development and the ARUX SDK
As previously mentioned, the development of the native ARUX libraries will be massively accelerated by our "MCP" system, which uses AI to translate the AROS source code into high-quality drafts for the native ARUX API.

All this work will culminate in the ARUX SDK. This development kit will allow programmers to port their existing applications, recompiling them to run as first-class citizens on any supported architecture, with access to all the memory, speed, and peripherals that modern hardware can offer.

ARUX is not Linux with an Amiga theme. ARUX is a modern, native AmigaOS platform that uses Linux as its Hardware Abstraction Layer (HAL) and microkernel. It is a path to ensure that our favorite OS API and philosophy not only survive, but thrive on existing hardware and on future wonders like MIRARI.

We hope you find this vision as exciting as we do.

Thanks for reading and for your continued support!

Regards

@GDroid
It is endearing to see that you seem to have the notion that no-one ever thought of such a thing before.

You might want to point your AI to Anubis and/or ARIX (or better yet, do some real world investigative detective work)

regards

https://code.goog...anubis-os/
https://github.co...halsc/ARIX
https://www.patre...t-22186659
https://www.patre...n-22600790
https://ae.aroswo...opic=156.0

Nice work @matteo

A side note with regards to Arix.

Those links are referring to the second iteration of Arix which uses another approach.

The first Arix was truly a hybrid mix and more in line with what direction Anubis was suppose to go and has/had more in common with what GDroid is proposing.

It is truly a miss that the original aros-exec forums are not publicly accessible/archived.

Instead idea's seem to re-iterated and discussed over and over again (and probably will be until the end of time).

That is not a problem perse but from those past projects people could learn why and how they failed (that is if you can even say they failed because that is really in the eye of the beholder. Fact is that those projects do not exist (in public) anymore).

magorium, a 64-bit compilation of wbXcli is planned for the future, thank you!

Yes, a 64bit version of wbXcli is (still) in the pipeline.

However, core Free Pascal developers do not seem to wish to acknowledge ABIv11 (which is the only working 64-bit AROS implementation), so I need to fork the Free Pascal compiler. And a fork I can do with the next release of Free Pascal (3.2.4) which is in the making for the last 4 years or so (thus please don't hold your breath).

In theory a fork can of course be done at any given moment but I opted against that as there are many (other) things still wrong with both the current compiler as well as the support for AROS (both issues will be heavily improved from the newly to-be-released compiler).

Thanks magorium!