No description
Find a file
Fábio Coutada 5606440114 docs: rewrite testing guidelines — accurate, comprehensive, actionable
Major rewrite of TESTING_GUIDELINES.md based on audit of actual codebase:

Key corrections:
- uos-target.py is a target-definition validator, NOT a test orchestrator
- No in-kernel test harness exists (only inline smoke tests)
- No CI boot testing (only build verification)
- No kernel code coverage (only tool-level coverage)
- uos-cover tools ARE operational with 11 test files

New content:
- Current state vs planned state clearly separated
- Host-side testing (pytest) documented with examples
- Firmware testing with uos-check.sh documented
- Code coverage workflow with uos-cover tools
- Test environment requirements
- Risk-based test prioritization (P0-P3)
- Test categories (smoke, functional, regression, performance, stress, security)
- 5-phase roadmap: CI boot tests → test harness → coverage in CI → MC/DC → perf
- Appendices with file locations, CI status, common commands

Document now accurately reflects what exists and provides actionable guidance.
2026-07-12 16:38:36 +01:00
.aurelio ci: add aurelio mirror action 2026-07-11 18:59:05 +01:00
.claude feat: implement core IPC, resource partitioning, health management, and RISC-V architecture parity enhancements. 2026-07-09 21:04:10 +01:00
.forgejo/workflows ci: add aurelio mirror action 2026-07-11 18:59:05 +01:00
docs docs: rewrite testing guidelines — accurate, comprehensive, actionable 2026-07-12 16:38:36 +01:00
docs-extracted feat(docs): extract RVS PDF manuals and regenerate index 2026-07-06 23:16:33 +01:00
kernel refactor: remove mycelium-tfw-extension to centralize in mycelium repo 2026-07-12 15:34:58 +01:00
src feat(import): Complete PikeOS 5.0 ecosystem import from devvm-arch 2026-07-06 21:01:41 +01:00
tools feat(docs): extend extraction script to support arbitrary base directories 2026-07-06 23:16:27 +01:00
xsd/src feat(import): Complete PikeOS 5.0 ecosystem import from devvm-arch 2026-07-06 21:01:41 +01:00
.gitignore feat(kernel): add Stage 1 bare-metal hypervisor skeleton for QEMU ARM virt 2026-07-06 22:51:56 +01:00
.gitmodules refactor: remove mycelium-tfw-extension to centralize in mycelium repo 2026-07-12 15:34:58 +01:00
AGENTS.md feat(universalisos): PikeOS-style Phase B/C device drivers + Phase D microkernel 2026-07-09 09:10:53 +01:00
AURELIO_INTEGRATION.md feat(phase-a): complete PikeOS 5.0 context switching implementation 2026-07-07 23:44:30 +01:00
AUTOSAR_CPP.md docs(analysis): Complete PikeOS 5.0 ecosystem analysis and Aurelio integration 2026-07-06 22:12:02 +01:00
BLOCK_DRIVER_IMPLEMENTATION.md feat(universalisos): PikeOS-style Phase B/C device drivers + Phase D microkernel 2026-07-09 09:10:53 +01:00
BUILD_ENVIRONMENT.md feat(repository): Initialize Universalisos repository with core documentation 2026-07-06 17:54:22 +01:00
COMPONENTS.md feat(phase-a): complete PikeOS 5.0 context switching implementation 2026-07-07 23:44:30 +01:00
HYPERVISOR.md feat(phase-a): complete PikeOS 5.0 context switching implementation 2026-07-07 23:44:30 +01:00
IMPORT_GUIDE.md docs(import): Add comprehensive PikeOS import guide 2026-07-06 18:01:34 +01:00
IMPORT_SUMMARY.md feat(import): Complete PikeOS 5.0 ecosystem import from devvm-arch 2026-07-06 21:01:41 +01:00
LICENSE feat(repository): Initialize Universalisos repository with core documentation 2026-07-06 17:54:22 +01:00
README.md feat(phase-a): complete PikeOS 5.0 context switching implementation 2026-07-07 23:44:30 +01:00
RISCV_PIKEOS_PARITY_PLAN.md feat: implement core IPC, resource partitioning, health management, and RISC-V architecture parity enhancements. 2026-07-09 21:04:10 +01:00
UNIVERSALISOS_PIKEOS_ANALYSIS.md analysis: comprehensive UniversalisOS vs PikeOS 5.0 parity assessment 2026-07-08 00:04:05 +01:00
UNIVERSALISOS_VS_PIKEOS_5.0.md feat(phase-a): complete PikeOS 5.0 context switching implementation 2026-07-07 23:44:30 +01:00
XSD_WORKFLOW_ANALYSIS.md feat(phase-a): complete PikeOS 5.0 context switching implementation 2026-07-07 23:44:30 +01:00

Universalisos - Type-1 Hypervisor Foundation

Universalisos is our safety-critical type-1 hypervisor foundation for cyber-physical systems, created from zero based on PikeOS architecture. This project imports the complete PikeOS ecosystem to serve as the reference architecture and codebase for Aurelio cyber-physical brain development.

🎯 CURRENT STATUS: Complete PikeOS 5.0 Parity Strategy

Strategic Objective: 100% PikeOS 5.0 Functional Parity 🎯

Universalisos has completed Stage 1-5 of the type-1 hypervisor implementation, providing:

  • Exception handling and system calls (Stage 2)
  • Priority-based scheduler framework (Stage 2)
  • Memory management with ARMv7 MMU (Stage 3)
  • VM context switching (Stage 3)
  • Device virtualization framework (Stage 4)
  • ARMv7 GIC interrupt controller (Stage 4)
  • Guest OS boot framework (Stage 5)
  • I/O virtualization (Stage 5)

Current Implementation: 15-20% of PikeOS 5.0 (framework foundations) Target: 100% PikeOS 5.0 functional parity within 15 months via Paths A+B+C parallel execution 🚀

📊 CRITICAL REFERENCE DOCUMENTS

🌟 UNIVERSALISOS_VS_PIKEOS_5.0.md - PRIMARY ROADMAP & COMPARISON

  • Comprehensive feature analysis across 11 major categories
  • Detailed implementation percentages and completion estimates
  • 6-36 month roadmap for reaching 40%, 60%, 80%, 90%+ PikeOS compatibility
  • Architecture alignment assessment (85% PikeOS pattern compliance)
  • Strategic recommendations for maximizing ROI
  • Production deployment guidance for cyber-physical systems

This document is ESSENTIAL for:

  • All architectural decisions and implementation priorities
  • Feature completeness assessment and gap analysis
  • Roadmap planning and milestone tracking
  • Integration strategy with PikeOS patterns
  • Development team coordination and progress tracking

Other Key Documentation:


Strategic Objectives

  • Type-1 Hypervisor: Safety-critical embedded systems foundation
  • AUTOSAR C++ Compliance: MISRA C++, MISRA C, DAL-B, DAL-A (avionics), ISO26262
  • Aurelio Integration: PikeOS codegen workflow → Aurelio implementation patterns
  • IP-XACT Architecture: Agent components as IP Cores with standard interfaces
  • Airship Control Foundation: Type-1 hypervisor for cyber-physical simulation control

Repository Structure

universalisos/
├── kernel/                     # Universalisos type-1 hypervisor implementation (C++)
├── src/                        # PikeOS source code import
├── test/                       # PikeOS test framework source code
├── docs/                       # Complete PDF documentation
├── ide/                        # Eclipse-based IDE source code (XSD → C generation)
├── xsd/                        # XSD schema files for C/C++ code generation
├── UNIVERSALISOS_VS_PIKEOS_5.0.md # **PRIMARY ROADMAP DOCUMENT** ⭐
├── AGENTS.md                   # Agent integration and development coordination
└── README.md                   # This file

Project Status

Current Phase: Complete PikeOS 5.0 Parity Strategy — Parallel Paths A+B+C Execution

The PikeOS 5.0 ecosystem import is complete. Universalisos has implemented a comprehensive hypervisor foundation through 5 development stages, establishing framework patterns that follow PikeOS architecture. The project now aims for complete PikeOS 5.0 functional parity through an ambitious parallel development strategy.

Development Strategy: Paths A+B+C in Parallel (15 months)

  • Path A (Complete PikeOS Core): 12-15 months, 100% PikeOS core functionality
  • Path B (Advanced Virtualization): Integrated into Path A for complete parity
  • Path C (Aurelio Integration): 6-9 months, agent acceleration across all components

Implementation Progress: See UNIVERSALISOS_VS_PIKEOS_5.0.md for detailed comparison analysis and roadmap planning.

Development Environment Setup

See BUILD_ENVIRONMENT.md for detailed setup instructions.

Required Toolchains:

  • GCC cross-compilers (ARM, target architectures)
  • CMake and Ninja build systems
  • AUTOSAR build tools and code generation utilities
  • XSD processing tools and validators
  • Eclipse IDE for XSD workflow analysis

Documentation

📋 Core Documentation

Hypervisor Kernel (C++)

The kernel/ directory contains the actual Universalisos type-1 hypervisor implementation, written in C++. The kernel has completed 5 development stages:

cd kernel
make
make run

See kernel/README.md for details.

Source Material

Source Location: Nextcloud cloud.portugalfuturista.org/s/devmm-arch

Contents:

  • PikeOS source code
  • Test frameworks
  • PDF documentation
  • Eclipse IDE source code (XSD → C generation)
  • XSD schema files

Safety-Critical Standards

Universalisos follows strict safety-critical coding standards:

  • AUTOSAR C++: Automotive software architecture compliance
  • MISRA C++: Motor Industry Software Reliability Association guidelines
  • MISRA C: C programming compliance
  • DAL-B: Design Assurance Level B (avionics systems)
  • DAL-A: Design Assurance Level A (critical avionics systems)
  • ISO26262: Functional safety for road vehicles

License

MIT License - See LICENSE file for details

Integration with Ecosystem

Universalisos integrates with:

  • nervura-electrica: Infrastructure platform and hosting
  • replica-omnisciente: Agent orchestration and mega-brain foundation
  • Aurelio: Compiler, gateway, and cyber-physical brain platform

Note: This repository is actively being populated with PikeOS ecosystem content. Documentation and implementation details are being added incrementally during the import process.

Implementation Status: Stage 5 Complete (15-20% of PikeOS 5.0 functionality) Next Phase: Complete PikeOS 5.0 Parity via Parallel Execution (15 months) Strategic Value: Framework foundations provide 85% PikeOS architecture alignment; agent acceleration enables 40-50% faster development for complete parity.

Timeline Summary:

  • Month 1-6: Core foundations + Agent framework + XSD processing pipeline
  • Month 7-12: Complete core functionality + Advanced features + Agent acceleration
  • Month 13-15: Complete API parity + Tooling integration + Certification preparation

Agent Acceleration Impact: 40-50% faster development across all PikeOS component categories through automated testing, validation, and XSD code generation.