| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
All checks were successful
CI / markdown (push) Successful in 3s
Restore the completed contribution template so new repositories use main dependency declarations and explicit frozen CI sources. Preserve the reviewed feature tree and the original work branch. #12 |
||
| .github | ||
| .editorconfig | ||
| .gitignore | ||
| .markdownlint-cli2.yaml | ||
| ARCHITECTURE.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| ROADMAP.md | ||
| rustfmt.toml | ||
| SECURITY.md | ||
EriX Meta Repository
This repository contains the shared policy files and repository templates 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
Meta provides the contribution, review, security and clean-room templates shared by EriX repositories. It also provides documentation formats, issue and pull request templates, and common repository configuration.
Component repositories copy the shared policy files unchanged and specialize the documentation formats. Integration owns cross-repository verification and fleet inputs.
The maintained responsibilities are:
- maintain the canonical contribution, review, licensing and clean-room files
- provide documentation, issue, pull request and configuration templates
- keep template content independent of component implementations
- point every repository's contribution guide to the canonical permissive
generative AI policy in
docs, without requiring attribution trailers
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
The non-normative planning archive is maintained separately. It does not define product APIs, runtime architecture, repository templates, or governance requirements.
Governance Principles
meta maintains the shared repository templates and clean-room contribution
policy. Organization-wide checks run in
Integration.
The scoped governance rules are:
- It defines organization-wide expectations without replacing component-specific implementation contracts.
- Shared governance and issue/PR templates remain byte-identical across repos; only component README, ARCHITECTURE and ROADMAP content is specialized.
- Contribution, licensing, and review policy must remain clear, auditable, and clean-room compatible.
- Generative AI assistance is permitted under the canonical policy in
docs; contributors retain complete responsibility and neitherSigned-off-bynorAssisted-byis mandatory. Cryptographic commit signatures remain required. - Project-wide policy changes require documented rationale before component repositories adopt them.
- CI runs
markdownlint-cli2across every Markdown policy, template, and workflow-support document in the repository. - CI jobs skip pull requests between branches of the same repository because push CI already covers them. Fork pull requests and other triggers still run.
Policy Boundaries
metasupplies templates; component repositories own their implementations, and Integration owns cross-repository checks and repository inventories.CONTRIBUTING.mdlists the canonical shared file set. Review changes here and propagate identical paths and contents to every repository, including new ones.- README, ARCHITECTURE and ROADMAP use shared formats with component-specific content; do not copy their placeholders into component documentation.
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.