Technical brief — HexaOS Portal
This localized note explains the scope and checks associated with HexaOS Portal.
Read →EDITORIAL CONTENT
Blog
Project news, architecture decisions and technical evidence published without exposing sensitive data.
Maintenance and non-regression — Verification method — Start and run HexaAcademy
Analysis HexaOS 3.0.0-rc1. Subject : Start and run HexaAcademy. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Start and run HexaAcademy
Analysis HexaOS 3.0.0-rc1. Subject : Start and run HexaAcademy. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Start and run HexaAcademy
Analysis HexaOS 3.0.0-rc1. Subject : Start and run HexaAcademy. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Start and run HexaAcademy
Analysis HexaOS 3.0.0-rc1. Subject : Start and run HexaAcademy. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Languages, keyboards and accessibility
Analysis HexaOS 3.0.0-rc1. Subject : Languages, keyboards and accessibility. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Languages, keyboards and accessibility
Analysis HexaOS 3.0.0-rc1. Subject : Languages, keyboards and accessibility. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Languages, keyboards and accessibility
Analysis HexaOS 3.0.0-rc1. Subject : Languages, keyboards and accessibility. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Languages, keyboards and accessibility
Analysis HexaOS 3.0.0-rc1. Subject : Languages, keyboards and accessibility. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Languages, keyboards and accessibility
Analysis HexaOS 3.0.0-rc1. Subject : Languages, keyboards and accessibility. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Waydroid and Android environment
Analysis HexaOS 3.0.0-rc1. Subject : Waydroid and Android environment. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Waydroid and Android environment
Analysis HexaOS 3.0.0-rc1. Subject : Waydroid and Android environment. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Waydroid and Android environment
Analysis HexaOS 3.0.0-rc1. Subject : Waydroid and Android environment. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Waydroid and Android environment
Analysis HexaOS 3.0.0-rc1. Subject : Waydroid and Android environment. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Waydroid and Android environment
Analysis HexaOS 3.0.0-rc1. Subject : Waydroid and Android environment. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Wine, Bottles and Windows applications
Analysis HexaOS 3.0.0-rc1. Subject : Wine, Bottles and Windows applications. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Wine, Bottles and Windows applications
Analysis HexaOS 3.0.0-rc1. Subject : Wine, Bottles and Windows applications. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Wine, Bottles and Windows applications
Analysis HexaOS 3.0.0-rc1. Subject : Wine, Bottles and Windows applications. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Wine, Bottles and Windows applications
Analysis HexaOS 3.0.0-rc1. Subject : Wine, Bottles and Windows applications. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Wine, Bottles and Windows applications
Analysis HexaOS 3.0.0-rc1. Subject : Wine, Bottles and Windows applications. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Limitations and next validation — Flatpak, AppImage and permissions
Analysis HexaOS 3.0.0-rc1. Subject : Flatpak, AppImage and permissions. Editorial intent : make the unknown visible and prepare the next step without announcing its result. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Verification method — Flatpak, AppImage and permissions
Analysis HexaOS 3.0.0-rc1. Subject : Flatpak, AppImage and permissions. Editorial intent : turning the subject into reproducible controls with expected results. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Point of controlled advancement — Flatpak, AppImage and permissions
Analysis HexaOS 3.0.0-rc1. Subject : Flatpak, AppImage and permissions. Editorial intent : describe what is established, what remains open and what is still necessary. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Choice of architecture — Flatpak, AppImage and permissions
Analysis HexaOS 3.0.0-rc1. Subject : Flatpak, AppImage and permissions. Editorial intent : present the compromises, the boundaries of responsibility and the reasons for the division. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →Maintenance and non-regression — Understand the role — Flatpak, AppImage and permissions
Analysis HexaOS 3.0.0-rc1. Subject : Flatpak, AppImage and permissions. Editorial intent : explain the issues, vocabulary and dependencies before proposing an action. The document specifies the evidence, the limits and the next check. Purpose of the R2 file : define the controls to be replayed after a change in source, configuration, or artifact.
Read →