fbcond

fbcond is the framebuffer console service 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 fbcon service daemon. Its purpose in EriX is to provide the fbcon 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 fbcon 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.

Feature model

• fbcond-runtime: base daemon behavior
• fbcond-runtime-phase3-framebuffer: framebuffer console mode
• integration aliases (fbcond-integration-*) map to runtime behavior, with optional force-fail test gating

Build and test

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

Validation Note

The host/test QUERY_CAP fallback remains cfg-scoped and fbcond now keeps only the direct kind-aware local-cap helper in runtime code, so runtime/release builds stay warning-free.

Governance Principles

fbcond governance is scoped to framebuffer console rendering and readback service behavior.

The scoped governance rules are:

• It uses only startup-assigned framebuffer, font, and console control authority.
• It keeps rendering state bounded and deterministic for display and test readback.
• It validates console IPC before mutating screen or history state.
• It does not own input policy or device-driver authority.

Authority Boundaries

• fbcond 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.