neo-core is the Rust-first Core domain for Neo: Soul + Heart.
Current status: neo-core v0.1.0 is the frozen v0 foundation snapshot.
neo-core is not a daemon, app, runtime, or central Core brain. It is the family boundary that groups the Soul and Heart systems as a pure Rust library workspace.
This repository only owns:
- public contracts and domain types
- Soul evaluation of meaning, identity, principles, boundaries, alignment, and evaluation intensity
- Heart processing of emotional and motivational impact into conditions, pressure, and inner-direction impulses
- test fixtures for downstream consumers
This repository does not own:
- daemon or runtime orchestration
- database or persistence infrastructure
- desktop, Tauri, or UI code
neo-core is a Rust workspace with four crates:
neo-core-contracts: shared Soul, Heart, CoreState, and CoreEvent contractsneo-soul-engine: identity, boundaries, coherence, and Soul feedback evaluationneo-heart-engine: Heart processing, pressure/recovery logic, and Heart impulsesneo-core-testkit: fixtures and helpers for tests and simulations
neo-core-contractsdefines the shared vocabulary used across Soul and Heart.neo-soul-engineevaluates meaning, principles, boundaries, purpose relevance, and alignment.neo-heart-engineprocesses internal affective state into conditions, pressure, and impulses.neo-core-testkitprovides fixtures and scenario helpers for sequence-level validation.
- Neo Core is the family boundary for Soul and Heart.
- There is no Core brain. Soul and Heart are the real systems.
- Soul is the active evaluator of meaning, alignment, boundaries, and purpose relevance.
- Heart is the active processor of pressure, motivation, recovery, and inner direction.
CoreStateis only a combined snapshot of Soul + Heart.- Neo Daemon will be a separate runtime target that consumes
neo-core. - Neo Desktop will communicate with the daemon, not directly with
neo-core. - Neo v0 may contain minimal versions of all layers, but this repository only owns Soul and Heart.
- Soul evaluates meaning, principles, boundaries, and alignment.
- Heart processes emotional and motivational state into conditions and impulses.
- Neo Core is only the family boundary.
CoreStateis only a snapshot.
Contracts first. Targets later.
The goal of this v0 slice is to stay pure, compile cleanly, and provide meaningful Soul/Heart behavior without introducing runtime targets.
neo-core v0 is validated at two levels:
- single-event transitions that prove the mechanics of Soul evaluation and Heart processing
- multi-event scenarios that validate trust-building, boundary pressure, recovery, mixed signals, and low-energy behavior over time
These are the rules that make neo-core reliable enough for downstream systems:
- Soul must retain a valid identity and at least one meaningful principle
- Soul evaluation must stay deterministic for the same Soul and event
- neutral events must not produce heavy moral or boundary feedback
- Heart values must always remain within valid bounds
- recovery must move Heart gradually toward baseline rather than away from it
- low energy must suppress over-eager engagement
- high stress must surface protective or stabilizing behavior
cargo run -p neo-heart-engine --example core_tickcargo run -p neo-heart-engine --example core_signal_flow
neo-core is validated through:
- single-event tests for mechanics
- scenario tests for behavior over time
- invariant tests for foundation guarantees
Run the full suite with:
cargo testneo-core v0.1.0 is the first frozen foundation line:
- Soul evaluates meaning, principles, boundaries, and alignment.
- Heart processes emotional and motivational state into conditions and impulses.
- Neo Core is only the family boundary.
CoreStateis only a snapshot.
Future changes should land in new versions rather than mutating the meaning of this snapshot.
neo-mindshould consumeSoulEvaluationResultandHeartProcessResult.neo-daemoncan later host Soul, Heart, and Mind as runtime systems.neo-desktopshould communicate with the daemon rather than directly withneo-core.
cargo fmt
cargo test
cargo clippy --workspace --all-targets -- -D warnings
cargo run -p neo-heart-engine --example core_signal_flow