Authority-free POSIX ABI types, constants, layouts, and error contracts for EriX.
  • Rust 58%
  • Python 27.7%
  • C 14.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Erik Inkinen 60bb85361f
All checks were successful
CI / markdown (push) Successful in 2s
CI / test (push) Successful in 53s
feat: Integrate the integer C compatibility boundary
Merge the approved bounded integer C boundary onto current main while retaining its freestanding, ownership and ABI checks alongside the main workflow. Resolve the additive workflow conflict and remove the duplicated identical evidence allowance.
2026-11-13 00:19:23 +02:00
.github feat: Integrate the integer C compatibility boundary 2026-11-13 00:19:23 +02:00
docs feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
include/erix feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
scripts feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
src feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
tests feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
.editorconfig Initial commit 2026-09-12 07:49:10 +02:00
.gitignore feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
.markdownlint-cli2.yaml Initial commit 2026-09-12 07:49:10 +02:00
ARCHITECTURE.md feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
Cargo.toml feat: Define checked compatibility identifiers and query codecs 2026-10-30 18:44:13 +02:00
CODE_OF_CONDUCT.md Initial commit 2026-09-12 07:49:10 +02:00
CONTRIBUTING.md Initial commit 2026-09-12 07:49:10 +02:00
LICENSE Initial commit 2026-09-12 07:49:10 +02:00
README.md feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
ROADMAP.md feat: Define and validate the integer C compatibility boundary 2026-10-30 18:44:14 +02:00
rustfmt.toml Initial commit 2026-09-12 07:49:10 +02:00
SECURITY.md Initial commit 2026-09-12 07:49:10 +02:00

EriX POSIX ABI Library

lib-posixabi provides authority-free compatibility metadata and explicit wire codecs for EriX. Callers supply every byte buffer. A decoded identifier is data and cannot grant access to a native resource.

Purpose of This Repository

This library defines checked scalar domains, descriptive identity pairs and compatibility message bodies. Use the checked values for metadata and c_abi for the separate x86_64 raw integer C declarations. Use MessageV1 and parse_message_v1 for the version-query codec. The crate uses no_std and has no dependencies.

See ARCHITECTURE for invariants, the wire contract for byte layouts and adapter obligations, integer C contract for the owned header and independent probes, and ROADMAP for implementation status and remaining ABI work. The broader design is maintained in the canonical compatibility phase.

Clean-Room Policy

Implementation and fixtures are original EriX-authored material. No external code, Rust crates, generated implementation templates, or test corpora are included. Standard references and design provenance are recorded in the focused contracts. Follow CONTRIBUTING for contribution requirements.

License

This repository is licensed under the ISC License.

Development Model

Development follows EriX's security, reliability, and performance priority order. Codecs make no implicit resource acquisitions and retain no global state.

Run cargo fmt --all -- --check, strict Clippy, tests, and warning-denied builds and rustdoc. CI also builds the library for x86_64-unknown-none to check its freestanding no_std surface. The C contract documents explicit compiler inputs for the independent integer layout and call probes. Keep every authored code file below 1,000 physical lines and document invariants and public interfaces with rustdoc.

Governance Principles

The repository follows canonical EriX contribution, clean-room, security, immutable dependency, and signed-commit policies. Component-specific wire contracts and validation evidence belong here; shared policy text stays aligned with meta.

Policy Boundaries

Compatibility metadata cannot broaden native capability authority. Parsing a receipt count cannot authenticate delivery or retire transferred capabilities; the wire contract names the future transport adapter's responsibilities.

Contact

Use repository issues for design and implementation discussion. Report security concerns privately through SECURITY.md.