Rust\u00a0.me is now installable.<\/p>\n
cargo add this-me<\/p>\n
That line brings in the Rust implementation of the\u00a0.me semantic kernel: hash-chained memory, path grammar, operators, derivations, secrets, proofs, snapshots, runtime events, receipts, and a small\u00a0CLI.<\/p>\n
Links:<\/p>\n
Crate on crates.io<\/a>API docs on\u00a0docs.rs<\/a>Rust\u00a0.me\u00a0docs<\/a>GitHub repo<\/a><\/p>\n .me is not just a data structure. It is a different way to think about application state.<\/p>\n In a normal stack, one idea usually becomes five\u00a0pieces:<\/p>\n ALTER TABLE friends ADD COLUMN is_adult BOOLEAN; Then the frontend repeats it\u00a0again.<\/p>\n In\u00a0<\/strong>.me, the goal is different:<\/strong> write the meaning once, keep the relation alive, and let the system explain how the value resolved.<\/p>\n .me<\/p>\n use this_me::kernel::{Kernel, Value};<\/p>\n fn main() -> Result<(), Box<dyn std::error::Error>> { A\u00a0.me kernel has two important layers:<\/p>\n The current projection: <\/strong>the latest value at each semantic\u00a0path.The memory log:<\/strong> an append-only hash chain of what happened.<\/p>\n Reads are fast because they hit the current projection. History remains available because every memory is\u00a0chained.<\/p>\n .me does not require a schema migration before you can say something.<\/p>\n me.postulate(“friends.ana.age”, 18_u64)?; Selectors preserve the plural\u00a0shape:<\/p>\n me.postulate(“items[sku-001].price”, 100_u64)?; And the parser preserves expressions:<\/p>\n “items[price > 90].name”<\/p>\n [] is not just an array. It is grammar for plurality.<\/p>\n Rust\u00a0.me includes the core operators:<\/p>\n @ identity Example:<\/p>\n me.claim_identity(“jabellae”)?; That is structural privacy.<\/strong> The value exists for the owner projection, but it is absent from the public projection.<\/p>\n Kernel is the semantic core. For apps, daemons, gateways, or embedded systems, use KernelRuntime.<\/p>\n use this_me::runtime::{runtime_receipt_to_json, KernelRuntime}; fn main() -> Result<(), Box<dyn std::error::Error>> { This is the host\u00a0shape:<\/strong><\/p>\n load kernel That makes it suitable for HTTP, WebSocket, local apps, Raspberry Pi, vehicle computers, robots, or a future monad.ai\u00a0host.<\/p>\n Install the\u00a0CLI:<\/p>\n cargo install this-me<\/p>\n Write\/read with persistent state:<\/p>\n me –state \/tmp\/me-state.json write profile.name ‘”Jabellae”‘ Without –state, the kernel is ephemeral. With –state, it persists.<\/p>\n You can also bind identity and expression:<\/p>\n me –who jabellae –secret ‘whatever’ about ‘x > 10’<\/p>\n And prove that\u00a0branch:<\/p>\n me –who jabellae –secret ‘whatever’ The seed stays private. The proof signs a branch-scoped message.<\/p>\n Rust\u00a0.me was compared against the TypeScript\u00a0.me kernel using a mirror suite: same machine, same operation shapes, same measured percentiles.<\/p>\n The important results:<\/p>\n Sustained mutation p95 The important part is not \u201cRust magically wins.\u201d The first Rust benchmark found a real gap: lazy mutation was still walking subscribers at write time. Run #002 fixed it by using source path versions and stale-on-read checks.<\/p>\n That is the\u00a0.me\u00a0lesson:<\/p>\n a write states a fact Wrong question, but useful comparison.<\/p>\n PostgreSQL is a mature relational database. It gives you SQL, indexes, transactions, joins, constraints, replication, and decades of production hardening.<\/p>\n .me is doing a different job.<\/p>\n PostgreSQL asks:<\/p>\n Where is this row? .me asks:<\/p>\n What does this path mean? So no, Rust\u00a0.me is not \u201cPostgres but\u00a0faster.\u201d<\/p>\n It is closer to a semantic runtime where state, derivation, privacy, proof, and reactivity live in one language.<\/p>\n For classic relational workloads, use Postgres.<\/p>\n For local-first semantic memory, reactive paths, explainable derivations, cryptographic identity, and embeddable runtime state,\u00a0.me is a different category.<\/p>\n Expect a small kernel, not a full app framework.<\/p>\n Expect paths instead of\u00a0schemas.<\/p>\n Expect derivations instead of duplicated business\u00a0logic.<\/p>\n Expect explain() instead of guessing where a value came\u00a0from.<\/p>\n Expect public and private projections as part of the structure, not as a legal promise after the\u00a0fact.<\/p>\n Expect Rust\u00a0.me to become the lower-level runtime ground: the version you can embed closer to the\u00a0machine.<\/p>\n .me is a framework where your session is your database, your language is your schema, and privacy is structural.<\/p>\n Rust makes that shape smaller, stricter, and closer to the\u00a0metal.<\/p>\n GitHub – neurons-me\/.me: Here we’re codependently creating .me while it concurrently creates us.<\/a><\/p>\n How to Rust .me<\/a> was originally published in Coinmonks<\/a> on Medium, where people are continuing the conversation by highlighting and responding to this story.<\/p>","protected":false},"excerpt":{"rendered":" And what to expect\u200a\u2014\u200ame.whatever(what) Rust\u00a0.me is now installable. cargo add this-me That line brings in the Rust implementation of the\u00a0.me semantic kernel: hash-chained memory, path grammar, operators, derivations, secrets, proofs, snapshots, runtime events, receipts, and a small\u00a0CLI. Links: Crate on crates.ioAPI docs on\u00a0docs.rsRust\u00a0.me\u00a0docsGitHub repo .me is not just a data structure. It is a different […]<\/p>\n","protected":false},"author":0,"featured_media":225093,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-225092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-interesting"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/225092"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=225092"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/225092\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/225093"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=225092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=225092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=225092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
UPDATE friends SET is_adult = age > 18;
CREATE TRIGGER …
SELECT …<\/p>\nStart With A\u00a0Kernel<\/h3>\n
let mut me = Kernel::new();
me.postulate(“profile.name”, “Jabellae”)?;
me.postulate(“wallet.income”, 100_u64)?;
me.postulate(“wallet.expenses”, 40_u64)?;
me.derive(“”, “wallet.total”, “wallet.income – wallet.expenses”)?;
assert_eq!(me.read(“wallet.total”), Some(&Value::from(60_u64)));
Ok(())
}<\/p>\nPaths Are\u00a0Meaning<\/h3>\n
me.whatever(what)<\/h4>\n
me.postulate(“friends.luis.age”, 17_u64)?;<\/p>\nThe path is the structure.<\/h4>\n
me.postulate(“items[sku-002].price”, 80_u64)?;<\/p>\nOperators<\/h3>\n
_ secret scope
~ noise boundary
__ pointer
= derivation
? query \/ collect
– remove \/ tombstone<\/p>\n
me.secret(“wallet”, “owner-secret”)?;
me.postulate(“wallet.balance”, 100_u64)?;
assert!(me.read(“wallet.balance”).is_some());
assert!(me.read_public(“wallet.balance”).is_none());<\/p>\nUse The Runtime For Real\u00a0Hosts<\/h3>\n
use this_me::storage::JsonFileStore;<\/p>\n
let store = JsonFileStore::new(“\/tmp\/me-state.json”);
let mut runtime = KernelRuntime::load(store)?;
let receipt = runtime.write_with_receipt(
“apps.fulltrailer.home.count”,
3_u64,
)?;
println!(“{}”, runtime_receipt_to_json(&receipt));
Ok(())
}<\/p>\n
execute write or me:\/\/ command
save snapshot
return result
return runtime events<\/p>\nCLI<\/h3>\n
me –state \/tmp\/me-state.json read profile.name<\/p>\n
about ‘x > 10’
prove local.netget ‘{“nonce”:”n-1″}’<\/p>\nBenchmarks<\/h3>\n
Rust: 0.0165 ms
TypeScript: 0.0286 ms
Rust\/TS: 0.57xLazy mutation at fanout 5,000
Rust: 0.0025 ms
TypeScript: 0.0053 ms
Rust\/TS: 0.47xEager mutation at fanout 5,000
Rust: 55.3975 ms
TypeScript: 99.7792 ms
Rust\/TS: 0.56xSecret lazy derivation p95
Rust: 0.0286 ms
TypeScript: 0.5689 ms
Rust\/TS: 0.05x<\/p>\n
a fresh read resolves whether a relation changed<\/p>\nIs This Faster Than PostgreSQL?<\/h3>\n
What query returns this set?
How do I keep schema, triggers, cache, backend, and UI synchronized?<\/p>\n
What relation produced this value?
Who can see it?
Can I prove this memory chain?
What changed, and who should react?<\/p>\nWhat To\u00a0Expect<\/h3>\n