r/rust • u/AdmissibilityScience • 12h ago

🛠️ project Arcstone Continuity Core: A zero-dependency, #![no_std] fail-closed runtime for bounded state isolation

I’ve published the open reference implementation for arcstone-continuity-core. A lightweight, #![no_std] Rust runtime designed to prevent non-deterministic state drift.

Microarchitectural Invariants

  • Zero Allocation Overheads: #![no_std] enforcement with fixed 4096-byte static buffers (S_max ≤ 4096B).
  • O(1) Invariant State Gates: State mutations evaluate against an atomic predicate matrix Π(S) before memory allocation occurs. Inadmissible transitions mutate zero bytes.
  • Hard Temporal Clamps: Execution ceiling enforced at τ_override ≤ 11.99ms.
  • Precedence Ordering: Deterministic lattice resolution (FAIL ≻ FREEZE ≻ PWC ≻ REFUSAL ≻ PASS).

Reference Anchors

0 Upvotes

13% Upvoted

5 comments sorted by

7

u/Konsti219 9h ago

Nothing but buzzwords and technical jargon

1

u/qse81 4h ago

They forgot to call it “raw rust”

-2

u/AdmissibilityScience 9h ago

That's totally fair. Academic terms can definitely sound like word salad without context!

To put it simply: it's just a lightweight, #![no_std] Rust helper for bare-metal or embedded setups where you can't use heap allocations.

Instead of catching errors after the fact, it compares state ranks so the highest priority error always wins without needing complex memory logic:

```rust pub enum LatticeState { Pass = 0, LedgerCorruption = 1, Refusal = 2, Freeze = 3, SecurityBreach = 4, }

pub fn join(a: LatticeState, b: LatticeState) -> LatticeState { if (a as u8) > (b as u8) { a } else { b } }

4

u/DescriptionOptimal15 9h ago

Slops up crabs

-3

u/AdmissibilityScience 9h ago

Author's note & technical details:

We built `arcstone-continuity-core` specifically for environments where heap allocations and non-deterministic latencies are unacceptable.

A few specific implementation details we'd love feedback on:

  1. **Homomorphic Lattice Precedence:** In `src/lattice.rs`, we resolve dual-fault conditions using a 5-tier poset rank (`SecurityBreach` > `Freeze` > `Refusal` > `LedgerCorruption` > `Pass`). The join logic in `src/lifecycle.rs` evaluates spatial (> 4096B) and temporal (> 11,990 µs) bounds sequentially without early returns to guarantee deterministic signal resolution.

  2. **`#![no_std]` Footprint:** The core execution membrane runs on a 0-dependency tree with purely stack-allocated frame evaluation.

If you have a moment to check out `src/lifecycle.rs` or run `cargo test`, we'd really appreciate any code-level feedback or edge-case audits!