.me
.me
Own your knowledge graph.
Agents, notes, relationships, wallets, groups, and secrets β unified in one reactive tree.
Getting Started
Clone the Github Repository: run the following command in your terminal.
git clone https://github.com/neurons-me/.me.git
Once cloned, select your preferred language and run the corresponding setup command:
Command<br>Status<br>Documentation
Typescript<br>cd .me/Typescript && npm install
node.js Docs β‘
Python<br>cd .me/Python/<br>Not Available<br>Pip Docs π
Rust<br>cd .me/Rust/<br>Not Available<br>Rust Docs
Demos ππππππππππππππππ
π€βπ€ Robots that Understand Context π€βπ€ β β Same object, different meaning. β
ποΈπ‘ Smart City ποΈπ‘ β¬ββ¬ βΆ β΄ β A full city reacting in real time as interconnected nodes. β
πππ Hemisphere Scale πππ β 1 million nodes with cross-domain reactive updates. β
β‘β‘β‘ Extreme Fan-Out β‘β‘β‘ β One write instantly updates 100k dependents. β¬ββ¬ β
β¬ β View all demos β
Syntax
.me uses an infinite proxy β any path you write becomes a node in the graph.<br>No schema. No migrations. No declarations upfront.
me.city.population = 700_000<br>me.city.name = "Veracruz"
// derived β recomputes automatically<br>me.city.density = () => me.city.population / me.city.area
// context-aware<br>me.robot.canProceed = () => me.robot.canLift && !me.robot.needsHumanReview
// stealth β structurally invisible to outside observers<br>me.wallet["_"].balance = 1000
// explain any value<br>me.explain("city.density")<br>// β { value: 3500, expression: "population / area", dependsOn: [...] }
// query across the graph<br>me.robots[r => r.canProceed === true].name
Write anything. Chain anything. The kernel figures out the dependencies.<br>If it changes, everything that depends on it updates β automatically.
β΅ Why .me?
Structural Privacy β Private data is structurally invisible (not just hidden by rules).
Full Explainability β Every derived value can explain exactly how it was computed.
Subjective Reality β Same graph, different views per agent.
Local compute makes memory an OS primitive.
Cloud makes it a service.
Even with 100,000 nodes needing a simultaneous recompute, youβre looking at about 62 microseconds per node (6252ms / 100k) for the full propagation. Thatβs incredibly consistent.
The same object can mean completely different things depending on context β and everything updates automatically when something changes.
Real Performance
.me uses true O(K) reactivity β when a value changes, only its actual dependents update. Not the whole graph.
1 million nodes in memory
1 sensor changed β exactly 6 dependent nodes recomputed
Time to propagate: 0.256ms
K=6 out of 1,000,000 β the rest of the graph is untouched
Scale the graph to 10 million nodes β if your change has 6 dependents, it still takes the same time.<br>Data that thinks. Logic that explains itself.
π Own your intelligence.
suiGn<br>MIT License Β© 2025 Β· neurons.me