What does the name casial-core mean?

casial-core is short for Context-Casial-Xpress Core. 'Casial' is a semantic handle for the substrate's role: causal-adjacent, concurrency-aware context handling that preserves the relationships an agent needs to reason coherently across loops.

What does casial-core actually do?

It provides the Rust-side substrate primitives — durable context structures, anchor handling, and concurrency surface — that Context Grapple Gun and Ubiquity build on. Treat it as the engine layer, not the user-facing surface.

How does casial-core relate to Ubiquity?

Ubiquity is the governance substrate as an architectural whole. casial-core is one of the foundational crates that makes Ubiquity's runtime semantics expressible in Rust. Other surfaces (CGG, ubiquity.toml, estate seeding) sit above it.

Where can I find casial-core?

casial-core is indexed on lib.rs under the Prompted LLC org. The canonical entry point is lib.rs/crates/casial-core; the source lives under github.com/prompted365.

← Prompted LLC

Canonical · Rust Crate·Shipped

casial-core

casial-core is the Rust crate that provides substrate machinery for Ubiquity. The name is short for Context-Casial-Xpress Core — a concurrency-aware kernel for durable context, anchors, and substrate-side primitives. It is the engine beneath Context Grapple Gun and the seed of Ubiquity's runtime surface.

What casial-core provides today

casial-core's shipped surface is the Rust substrate machinery for durable context handling and anchor primitives. It is the layer where substrate-side semantics — anchor identity, ray projection, warrant state — become concrete code.

Engine layer. Read the source under the Prompted365 GitHub org for the current API; prefer the crate over secondary descriptions of its behavior.

What casial-core is not

casial-core is not a general agent framework, not a prompt library, not an async runtime replacement, and not yet a stable public API. The crate moves with the substrate; pin a version if you depend on it downstream during pre-release.

Relationship to the rest of the stack

casial-core → Context Grapple Gun → Ubiquity → Sovereign Estates. The crate is at the base of the abstraction ladder. Application surfaces compose upward; governance semantics compose downward through the primitives the crate exposes.

This is

A Rust crate published under the Prompted LLC org.
The substrate machinery layer — durable context, anchor primitives, concurrency surface.
The engine beneath Context Grapple Gun.
A building block of the Ubiquity governance runtime.

This is not

A general-purpose AI framework or agent SDK.
A prompt-engineering library.
A drop-in replacement for tokio, async-std, or any general async runtime.
A finished public API surface — versioning will move quickly during pre-release.

Frequently asked

What does the name casial-core mean?: casial-core is short for Context-Casial-Xpress Core. 'Casial' is a semantic handle for the substrate's role: causal-adjacent, concurrency-aware context handling that preserves the relationships an agent needs to reason coherently across loops.
What does casial-core actually do?: It provides the Rust-side substrate primitives — durable context structures, anchor handling, and concurrency surface — that Context Grapple Gun and Ubiquity build on. Treat it as the engine layer, not the user-facing surface.
How does casial-core relate to Ubiquity?: Ubiquity is the governance substrate as an architectural whole. casial-core is one of the foundational crates that makes Ubiquity's runtime semantics expressible in Rust. Other surfaces (CGG, ubiquity.toml, estate seeding) sit above it.
Where can I find casial-core?: casial-core is indexed on lib.rs under the Prompted LLC org. The canonical entry point is lib.rs/crates/casial-core; the source lives under github.com/prompted365.