named

named is the service discovery registry daemon for EriX.

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

Technical requirements are tracked in the EriX requirements, conventions, and project documentation.

See:

• docs for design documents, specifications, and development plans.
• Related architecture repositories for kernel, services, libraries, drivers, and integration tooling.

Purpose of This Repository

This repository implements the EriX name service daemon. Its purpose in EriX is to provide the name service role through explicit IPC and startup authority.

Functionally, it implements the daemon runtime, state model, IPC handling, and validation tests. The repository keeps the implementation, interface contracts, tests, and documentation for that behavior in one reviewable ownership boundary.

The maintained responsibilities are:

• implement the name service runtime and state model
• validate startup authority before accepting IPC requests
• handle bounded service operations through the assigned endpoint set
• keep service behavior, tests, and authority invariants documented

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, deterministic, reproducible, authority-explicit, security-first, and self-hosting oriented.

This repository follows the project roadmap and the validation rules documented in its own roadmap.

Status

• Service discovery is fully implemented.
• Integrated with rootd orchestration.
• Validated by integration scenarios covering:
  • Registry registration
  • Service lookup
  • Concurrent access patterns
  • Error conditions when service is unavailable

Build and test

cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test --all-targets --all-features

Dependencies

• lib-bootstrap
• lib-capabi
• lib-ipc
• ipc-syscall-x86_64

No third-party crates are used.

Build and Test Modes

This repository supports additive runtime and integration feature gates.

• *-runtime and *-runtime-phase* features select production bootstrap/runtime behavior.
• *-integration-smoke remains available for synthetic end-to-end validation paths.
• *-integration-force-fail remains test-only and MUST NOT be enabled for runtime appliance builds.

Compatibility aliases are kept so existing scenario feature names continue to compile while the runtime naming becomes canonical.

Governance Principles

named governance is scoped to bounded service-name registration and resolution.

The scoped governance rules are:

• It publishes only explicit registered service endpoints.
• It must reject duplicate, malformed, or unauthorized registrations.
• It keeps lookup semantics deterministic and bounded by the registered namespace.
• It must not be used to discover private providers that are intentionally boot-wired.

Authority Boundaries

• named operates only through startup-assigned service capabilities.
• New authority must be represented in bootstrap/capability validation and integration tests before use.

Contact

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

No decisions are considered valid without documented rationale.

Maintainers can be reached via email: admin@erikinkinen.fi.