Expand description
CoreShift Core is the low-level Linux and Android foundation crate for the CoreShift ecosystem.
CoreShift Core keeps direct kernel, libc, and procfs interaction in one
place so higher layers can stay policy-oriented:
- CoreShift Core: low-level Linux and Android primitives
- CoreShift Engine: daemon and plugin runtime
- CoreShift Policy: policy logic and product behavior
This crate is intentionally policy-neutral. It provides mechanisms such as
spawning, epoll, inotify, procfs inspection, and signal helpers. It
does not make daemon lifecycle or product decisions for callers.
§Core Guarantees
Core adheres to strict architectural invariants to ensure stability:
- No policy: Primitives only; no allowlists, retry plans, or fallbacks.
- No hidden threads: Work is performed on the caller’s thread.
- No global state: Stateless execution; no global mutable configuration.
- No scheduler: Provides reactor primitives but does not own execution.
Public primitive modules:
crate::android_propertyfor direct Android system property accesscrate::fsfor filesystem probes and readaheadcrate::procfor procfs helperscrate::signalfor signal and shutdown helperscrate::uidfor ownership lookupscrate::spawnfor explicit process spawningcrate::reactorfor fd readiness primitivescrate::inotifyfor watch/decode helperscrate::unix_socketfor Unix domain socket primitivescrate::iofor explicit drain helpers
ⓘ
use coreshift_core::Daemon;ⓘ
use coreshift_core::ForegroundResolver;Re-exports§
pub use error::CoreError;
Modules§
- android_
property - error
- Shared low-level error types.
- fs
- Filesystem-oriented low-level helpers.
- inotify
- Raw inotify helpers.
- io
- Buffered process I/O helpers.
- log
- Backend-agnostic logging facade.
- proc
- Procfs and process-introspection helpers.
- reactor
- Asynchronous event reactor.
- signal
- Signal and shutdown helpers.
- spawn
- Process spawning and lifecycle management.
- uid
- Ownership and UID lookup helpers.
- unix_
socket - Low-level Unix domain socket primitives.