EriX Meta Repository

This repository contains shared governance, contribution rules, and process documents for the EriX operating system project.

EriX is a clean-room, capability-based microkernel operating system written entirely in Rust.

All technical requirements are defined in:

• Requirements & Conventions Document
• Self-Hosting Milestones

See:

• docs for design documents, specifications, and development plans.
• Architecture repositories (kernel, bootloader, etc.)

---

Purpose of This Repository

This repository defines:

• Contribution policy
• Clean-room enforcement rules
• Licensing rules
• Review process
• Issue and PR templates
• Organizational governance

It contains no executable system components.

---

Clean-Room Policy

EriX follows a strict clean-room philosophy:

• No external source code may be copied.
• No external Rust crates are allowed.
• No code generation tools that embed third-party code.
• All code must be authored within the project.

Violations will result in rejection of the contribution.

---

License

All EriX repositories are licensed under the ISC License.

---

Development Model

EriX development is:

• Modular (one repo per major component)
• Deterministic
• Reproducible
• Authority-explicit
• Security-first
• Self-hosting oriented

See docs/phases/README.md for the system development phase structure.

---

Governance Principles

• Kernel remains minimal and policy-free.
• All services belong in user space.
• Capabilities are first-class authority objects.
• Unsafe Rust must be minimal and documented.
• Determinism is preferred where feasible.

---

Contact

Development occurs in EriX organization and discussions happen in issues and design documents.

Discussions should occur via issues or design documents.

No decisions are considered valid without documented rationale.

You can also reach out to maintainers via email: admin@erikinkinen.fi.