User-owned coordination
UbU’s long-term model fits local authority over identity, data, planning context, and disclosure. The user should decide what leaves the device, what is shared with a community, and what becomes evidence for coordination.
A full calendar and a full life aren't the same thing. UbU is a planning kernel that turns messy real-world inputs into explicit, inspectable, recalculable plans — modeling not just your tasks, but your dependencies, your constraints, and your actual human capacity.
Everything is public and open source. The design is the source of truth; the demo, the automation, and its artifacts all derive from it.
Public design notes, decisions, and open questions — the documents every other repository derives from.
github.com/UbU-project/ubu-design
A Python-only, CLI-only demo built for ETHConf NYC. Frozen schema and golden fixtures in place; modules generated one reviewed ticket at a time.
github.com/UbU-project/ubu-phase0-demo
A bounded, auditable loop that uses Codex and local Ollama models to propose, score, and select reviewable design-question patches — never mutating the repo directly.
github.com/UbU-project/model-committee
The storage repository holding the reviewable artifacts — selected patches, commit messages, reviews, and logs — produced by model-committee runs.
github.com/UbU-project/model-committee-artifacts
UbU is preparing its own Phase 0 release. The project's work lives as GitHub issues. UbU imports those issues as Tasks, builds a planning request, applies dependency and affect constraints, and shows what fits into the next four hours — honestly labeling what it does and does not yet model.
ubu-phase0 demo UbU Phase 0 Demo Data source: live GitHub Repository: UbU-dummy/ubu-design Imported Tasks 3 (each carries source_ref + authority_source) Affect Profile energy medium · stress low · mood calm Planning Window today · next 4 hours Calendar Preview Time Task Source Affect 09:00-09:30 Write Phase 0 contract profile github_event ▆▆▆ 09:30-10:00 Freeze schema module github_event ▃▃▃ 10:00-10:30 Generate acceptance fixtures github_event ▆▆▆ Claim Register Summary legitimized: 3 · deferred: 0 probability_quality: not_estimated (Phase 1 will populate) coverage_estimate: - (Phase 1 will populate)
Representative offline-fixture output, per PHASE0_DEMO_SCRIPT.md. Phase 0 is deliberately concrete, not broad — it shows a real planning loop and is honest about the parts Phase 1 will fill in.
For at least one Task, the demo must visibly show:
UbU-dummy/ubu-design, optionally tagging ubu:duration:60m, ubu:priority:high, or ubu:depends-on:#N.ubu-phase0 refresh to re-fetch the issues.ubu-phase0 demo — and the new issue appears as a Task in the next preview.--offline reproduces the full loop deterministically from a fixture.UbU does not need Ethereum in Phase 0. The reason Ethereum people should care is that UbU points toward user-owned coordination graphs, selective disclosure, capability-aware delegation, and task-centered markets that can settle through many rails.
Instead of searching for “plumber near me,” the plan knows: this repair requires one hour, a wrench, a part, and someone with verified sink-repair capability. Settlement can happen underneath the task.
UbU’s long-term model fits local authority over identity, data, planning context, and disclosure. The user should decide what leaves the device, what is shared with a community, and what becomes evidence for coordination.
Tasks can point to skills, tools, techniques, completion evidence, and selective-disclosure reputation without requiring a centralized marketplace to own the whole relationship.
Task completion can be paired with fiat, Ethereum, privacy-preserving payment, time-banking, barter, local credit, or community scrip — without making the payment rail the whole product.
The demo is intentionally narrow. It is meant to make the first planning loop inspectable, reproducible, and honest about what is not modeled yet.
source_ref and authority_source.UbU helps you see the coherence between who you say you are and what you actually do — at every scale, from personal (nutrition, assets, time) to community (peer teaching, resource sharing, Associations) to global (marketplace interoperability). It makes Resource, Skill, and Technique explicit, compartmentalizes what flows where, and lets communities govern themselves. Your data stays yours; authority flows outward from you.
Audience cuts below are starting points, not scripts — combine them for people who wear more than one hat (a cypherpunk founder, an academic who maintains FOSS), and watch which framing actually lands.
"See what's actually wasting your time and money — gear you own but never use, meals you plan but never cook, skills you say matter but don't practice. Build real capability with visible progression. Teach and learn from people you already know. No algorithm optimizing you."
"True multi-layer federation — independent networks that interoperate without merging into one graph. No pooled corpus. Compartment policy is a hard product boundary, not advisory. Super-connectors bridge contexts by choice; local authority is preserved at every scale. And we're honest that cloud is leak-minimization, not a zero-leak claim."
"Marketplaces emerge from genuine peer exchange instead of a forced platform. Settlement is pluggable — Ethereum, fiat, time-banking, barter scrip. No network-capture trap; communities thrive standalone. Revenue from value, not lock-in, because there's no pooled corpus to monetize."
"The Technique library is crowdsourced and contributor-owned. Your project or tool library coordinates with zero external dependencies. Global coordination is an opt-in bridge, not a forced registry. And UbU runs UbU — you can watch the planning model work on a real project, live."
"Work-life balance as a data primitive instead of a slogan — coordination that respects modeled capacity and focus, with the worker as a planning participant who has standing, not a node to optimize. Organizational introspection without surveillance: see bottlenecks and unsustainable commitments without monitoring individuals.
"Task-driven markets, not search-driven markets — the plan says what's needed before the user searches, and Ethereum settles it underneath. Pseudonymous skill profiles and selective-disclosure reputation without doxxing. A Delegation Substrate maps cleanly to escrow, deposits, and programmable agreements."
"Compartments as a case study in schema-enforced data-boundary control, with inference-resistance as an explicit design goal — policy behavior must not become an inference channel back to raw state. Local-first sync with no canonical server; the sync-sovereignty invariant as a testable property; cryptographic substrate left agnostic."
"Multi-agent planning that combines individual Objectives, capability, and affect constraints into group Plans without reducing humans to optimization nodes. Capability modeling (skills that rust, unlock, transfer). Revealed preference inferred from what people keep, use, and trade — without pooling raw data."
"Your calendar says one thing; your choices say another. UbU makes the gap visible — no judgment, just honest feedback. Own your stuff or let it go. Be part of something without your community being absorbed into a platform. Your data stays yours, always."
UbU is being developed in staged proofs, from a narrow CLI planning loop toward local-first planning, synchronization, and eventually multi-user coordination.
| Phase | Status | What it proves |
|---|---|---|
| Phase 0 | Current demo | GitHub issues become Tasks and then a constrained Calendar Preview. |
| Phase 1 | MVP target | Single-user local planning kernel with a one-task-at-a-time user experience. |
| Phase 2 | Future | Multi-device sync, compartments, and local-first replication. |
| Phase 3 | Future | Multi-user coordination, Associations, and structured delegation. |
Why every productivity tool ever built is a map — when what you need is a GPS.
You have a to-do list. Maybe several. A calendar, probably color-coded. Apps for tasks, apps for notes, apps for habits. You are, by every available measure, organized.
And yet — you still sit down on a Sunday afternoon and have no idea what to actually do.
That feeling is the whole problem. And solving it is what UbU is about.
Think about the difference between a map and a GPS.
A map is extraordinary. It contains everything — every road, every landmark, every possible route between here and anywhere. But a map doesn't know where you are. It doesn't know where you're going. It shows you the world, but it cannot tell you what to do next. That's still entirely on you.
A GPS knows where you are. It knows where you're going. It calculates a route in real time, accounts for conditions, and when you miss a turn — as you will — it doesn't give up on you. It recalculates. It adapts. It gives you one instruction: turn left in 400 meters.
Every productivity tool ever built is a map. A sophisticated map, perhaps a beautiful one, but still: a map. It holds your tasks, displays your schedule, shows you the territory. The actual navigation — the constant daily question of what do I do right now — is still entirely on you.
UbU is built to be a GPS for your life.
It takes in everything relevant to your situation — your goals, your ongoing work, your commitments, how much energy you have today, even the fact that you barely slept last night — and figures out what you should do next. Not "here are all your tasks." One clear answer: this, now, here's why. And when things change — a deadline moves, an appointment runs long, your afternoon falls apart — it recalculates.
That's a real shift. But it's only the beginning. Because a GPS for your life needs to know something that a GPS for your car doesn't: whether you're actually capable of taking the route it's suggesting — and whether everything you need is actually in place.
Consider something simple. You want to fix the leaky faucet. That task has lived on your list for six weeks. Your calendar has plenty of open Saturday morning slots. So why hasn't it happened?
Because you don't have the replacement part. Because you watched a repair video two years ago but aren't sure you remember how. Because somewhere between "I should do that" and actually doing it, there's a gap that no calendar has ever learned to close.
A GPS that suggested a route you couldn't physically drive would be useless. A GPS that didn't know you were nearly out of gas would get you stranded. UbU works the same way. Before it routes you toward a task, it checks: do you actually have what you need? If the replacement part isn't in your possession, "fix the faucet Saturday" isn't a plan — it's a wish. So UbU schedules something earlier in the week: get the part. If you don't own the right wrench, it might suggest borrowing one from a local tool library rather than buying something you'll use once.
Then there are skills. Skills, critically, rust. You learned this repair a few years ago and haven't touched plumbing since. UbU knows that, and it weighs whether a refresher makes sense — or whether your time, confidence, and the consequences of getting it wrong point toward hiring someone instead.
But here's where it gets genuinely exciting: UbU doesn't just flag the skill gap and leave you there. It connects you to a worldwide library of guides, tutorials, and step-by-step techniques — contributed and vetted by people who've done exactly what you're trying to do. Not a firehose of search results. Not ten competing YouTube videos of varying quality. The right one, matched to your current level. If you've done basic plumbing before, you get the intermediate guide. If this is truly your first time, you get something that won't assume knowledge you don't have yet. You're never overwhelmed. You're equipped. And when you follow the guide and finish the job, that skill is now part of you — available the next time something needs doing, building a foundation for things that weren't possible before.
Take something you do every single day: eating. Most people don't fail at eating well because they lack discipline — they fail because deciding what to cook, from what's already in the fridge, before it spoils, at the end of a draining day, is its own small planning problem nobody ever solved for them. UbU treats a recipe the way it treats any other route: ingredients you need, a skill or two it calls for, and an outcome on the other side. It knows what's in your kitchen and what's about to turn, builds a meal around it, and folds the missing items into a single grocery run instead of three. And it meets you where your cooking skill actually is — the simple version if you're starting out, something more ambitious once you've built a repertoire. Because eating connects to moving, the same model can close a loop your separate apps never could: what you take in from meals and what you spend in exercise, weighed against a week that's realistic rather than aspirational. A high-stress week on no sleep earns a simpler dinner and a shorter workout — not the identical regimen handed to everyone who downloaded the same app.
The real depth of this idea shows up not with faucets, but with the parts of life that actually keep people up at night.
Take children. If you're a parent, you carry a mental load that no app has ever come close to modeling. The permission slip that needs to go back by Thursday. The pediatrician appointment that requires taking a half-day from work, which cascades into rescheduling a meeting, which cascades into prep you now have to do the night before. The science project your child mentions Wednesday evening, due Friday. The soccer practice that moved this week, which means dinner plans changed, which means the grocery run needs to happen differently than planned.
These aren't separate tasks. They're a web of dependencies, and the web shifts constantly. A calendar shows you Thursday. UbU understands that Thursday's open slot is the last window before the permission slip deadline — and surfaces it before it slips your mind. When the science project appears Wednesday night, UbU doesn't just add it to a list. It looks at what's realistic before Friday, checks whether the materials are already in the house, and maps out what can actually happen tonight versus tomorrow morning.
The GPS recalculated. You didn't have to hold all of that in your head.
The same logic applies to the slower, quieter things — the relationships that matter but don't come with deadlines. You want to stay close with a sibling you rarely see. That's not a task with a due date. It's an intention. And intentions, without some structure around them, gradually fade into guilt and distance. UbU treats relationship maintenance as real planning. It finds a moment in your week that's genuinely calm — not just available in the calendar sense, but unhurried enough that you can be present. It surfaces the right time and makes the step small enough to take.
This is what it means to navigate, rather than just to have a map.
There's a particular kind of exhaustion that comes not from your tasks, but from the interruptions between them. Your phone buzzes during a meeting for a coupon you'll never use. It stays silent at lunch when your cousin's family news comes through. It wakes you at 2am for a marketing email, and you sleep through the one message that actually mattered.
The tools that promise to fix this — Do Not Disturb, Focus modes — are blunt switches. On or off. You set them by hand, you forget to turn them off, and the one time something urgent arrives, they bury it alongside the noise. A switch that silences everything is barely different from turning the phone off entirely — and that quiet question, why even keep it on?, is one those tools never really answer.
UbU treats interruptions the way it treats everything else: as a decision that depends on your actual situation. Who is this from, and how much does it matter? But also — and this is the part nothing else can do — what are you doing right now, and what do you actually want to protect? A low-priority note from a colleague during a meeting can wait; a high-priority one from the same colleague shouldn't. Your cousin's message is welcome at lunch and unwelcome at 2am. Your child, or your partner, should always be able to reach you. And none of that should depend on which app the message happened to arrive through — email, text, a call, a chat — because you don't experience interruptions one app at a time. You experience them as your attention, taken or protected.
Here's the catch, and it's the whole reason this is hard: your phone can know a meeting is on your calendar, but it cannot know whether you're deep in concentration, drained from a long morning, or that lunch turned into a conversation you don't want broken. No sensor reads your inner state. Only you do. So UbU doesn't pretend to detect it — it works from what you tell it and what it learns alongside you, the two refined together over time. That's what makes it less like a switch and more like a smart home that turns the lights on as you walk into the room: it predicts, it prepares, it adjusts, and as a focus block nears its end and a break is due anyway, it eases up — letting more through as the cost of the interruption falls. You stop managing your own settings. You get your attention back.
Now, there's something important to say about how UbU actually works — because it's almost certainly not what you'd assume.
We live in an era where "AI-powered" has become shorthand for "a computer makes decisions and you go along with them." Every app, every platform, every device is gathering information about you, feeding it upward to corporations and, increasingly, to employers. Your calendar data tells your company when you're focused. Your fitness app tells an insurer how healthy you are. Your browsing tells advertisers what you're afraid of. You are, without quite choosing it, continuously monitored.
UbU is built on the opposite principle. Your data — your goals, your schedule, your capabilities, your family's needs, your health, your emotional state — should live under your control, on your own devices or other storage you explicitly choose. UbU is designed for local-first operation, privacy-safe synchronization across your trusted devices, and narrow, policy-governed use of external tools only when you authorize it. It is not sold out from under you. It is not used to build a profile of you that anyone else can access or purchase. Your employer cannot see it by default. No platform can mine it. No algorithm is trained on your private life without your knowledge. And the flip side of that control is real: because the data is genuinely yours, you stay free to share or even sell your own information if you ever decide to — UbU's job is to make sure that's always your choice, never something taken from you by default.
And crucially: UbU is not running your life. This is not a system that makes choices for you and expects compliance. The planning intelligence is yours to direct. You set the goals. You define what matters. You approve what happens. UbU is a tool — a powerful one, but a tool — not an authority. Think of it less like an AI assistant and more like a very capable notebook that can also think: it organizes what you give it, reasons about it on your behalf, and presents you with options. The decisions remain yours, always. You are the navigator. UbU is the instrument that makes navigation possible.
For anyone who is rightfully skeptical of the direction technology has been heading — the surveillance, the manipulation, the slow erosion of autonomy — UbU is something different. It was designed to give power to the person using it, not to extract value from them.
There's a quiet consequence of building it this way. Because UbU runs on the device already in your pocket — no data center, no subscription to a remote brain, no fleet of servers someone has to pay for — it can reach people the big systems have no reason to serve. The most capable personal AI is being built for people who can pay for it. UbU is built to give a version of that same capability to anyone with a modern phone, including the people large companies will never find profitable enough to bother with. Self-governance shouldn't be a luxury good.
As you use UbU and act on its plans, something accumulates: capability. Skills sharpen with practice. Things that once required looking up become second nature. Things that were previously out of reach — too complex, too uncertain — gradually come within reach. Every capability you build is a door. Every door opens more.
UbU tracks this. It knows what you can do confidently, what you're close to being able to do, and what a small investment would unlock. The worldwide library of guides and techniques grows with you — not pulling you toward content that earns someone else's revenue, but surfacing what genuinely fits where you are right now. Fix enough things around the house and a whole category of repairs opens up. Build a cooking repertoire and eating well stops being a project. Learn the basics of a subject you've always avoided and suddenly a range of decisions you used to find intimidating become straightforward. The point isn't to rank or score you. It's that growth is real, and most tools behave as though you're exactly the same person you were on the day you first opened them. You're not. UbU shouldn't pretend you are.
None of this has to be solitary — and that's not a sentimental aside, it's the point. Nobody runs their life alone; we borrow, teach, lend, and lean on each other constantly. So the same capability you build becomes something you can give. You can teach a friend a technique you've mastered, lend a tool you own, or learn a repair from someone two streets over who's already done it — peer to peer, with you deciding exactly what's shared and what stays yours. Small circles like that knit into something larger on their own: a building, a neighborhood, a maker crew, a tool library. The same model that coordinates your kitchen can coordinate a group, and a single person who happens to bridge two of them carries only what they choose to carry across — never the whole private picture on either side. What grows out of that, eventually, is a way for people to find the skills and resources they need from each other rather than from a search box and a stranger's algorithm. But it grows outward from you. You are always the origin, never the product.
And UbU watches the things you own as closely as the things you do. The bike in the corner, the bread machine, the second set of tools — the honest question was never "do I use this," but "is keeping it worth what it quietly costs me," counting the value it sheds over time, the space it eats, the upkeep, and the low background weight of unused stuff. A thing you will truly never touch isn't neutral; it's a slow leak you could close by selling it or passing it on. But there's a third answer a decluttering app can't give you: a technique that earns the thing its place — store it so it stops degrading, maintain it so it holds value, or finally fold it into your week so it does what you bought it to do. Underneath all of it is one quiet job. You tell UbU who you mean to be; it watches what actually flows through your life — what you add, what changes, what you let go — and shows you, gently, where the two have drifted apart. The goal you set against the gear that proves you've stopped pursuing it. The meals planned against the ones that never happened. Not to scold you, and never to quietly edit your goals behind your back, but to hand the gap back to you so you can choose: build the capability, revise the goal, or keep the thing and own the cost honestly. Reconciliation, not judgment — across everything coming in and everything going out.
The deeper purpose is simple to say, and genuinely hard to build.
Most people have goals they've carried for years. Not because they're lazy or undisciplined. Because there is always a gap between "I want that" and "I know how to get from here to there." That gap is filled with unclear dependencies, missing resources, unexamined tradeoffs, and the quiet exhaustion of not knowing where to start — made worse by the knowledge that every app you try is watching you while it pretends to help you.
We have technology that can write symphonies and explain black holes. We still don't have software that can take "I want to get my life together" and turn it into a plan that actually works — one that respects your privacy, builds your capability over time, connects you to the knowledge of people who've been where you are, and never mistakes being organized for being empowered.
And there's a version of this future already arriving that's worth naming plainly. The next generation of AI assistants will be able to listen, watch, and eventually read every sensor on your phone — and from that flood of data they will be able to do many of the things UbU does. But they will do it by consuming you: pulling your whole life into someone else's model, on someone else's servers, for someone else's purposes. That's the brute-force path to a helpful assistant, and it is very likely to become the default simply because it is the easiest thing to build.
UbU is the other path. The same destination — a system that genuinely helps you run your life — reached by the opposite means: your data stays yours, the reasoning stays inspectable, and the goal stays your goal. It is the more elegant solution, and elegance here is not a flourish. It is the difference between being helped and being harvested. Whether that path exists at all, while the easy one is so close, is part of why UbU is being built now.
UbU will help you plan out your life. It models your situation honestly, reasons about what's actually possible, and helps you see the route — your route, on your terms, with your data staying yours. It won't make decisions you haven't sanctioned. But it will do what no map has ever done: figure out where you are, figure out where you're going, and tell you — clearly, with reasons, adapted to who you actually are right now — what to do next.
That's what UbU is building.
UbU is at the transition point where the design is coherent enough to begin implementation, but early enough that contributors can meaningfully shape the architecture. The immediate next step is modest: build the bootstrap tool that helps the project finish becoming buildable — the first practical path toward UbU running UbU.
Early contributors enter through bounded paths. Small, correct, reviewable work is worth more than sweeping architectural enthusiasm.
If you coordinate autonomous technical teams — FOSS, Ethereum, protocol, privacy, infra — we want to hear one precise example of a coordination failure your tools never modeled.
[email protected]