Future Systems
Sketch the distant coast while still learning to sail.
Notes and experiments around AI infrastructure, automation, and communities built for people.
Not a product roadmap. A horizon file.
Future Systems is the drawer labeled someday — kept open on purpose. AI infrastructure shaped like a research commons. Automation that expands human capability. Communities and cities designed with care instead of extraction.
It is deliberately unfinished. Writing it down keeps the compass calibrated while Lemon Tree earns the distance.
“Dreams without warehouses become daydreams. Warehouses without dreams become warehouses.”Horizon note
What "later" still asks for "now."
Even far work needs near discipline.
- 01
Studio strength
Lemon Tree proves it can learn, ship, and fund ambition without mythology replacing math.
- 02
Research literacy
Hands-on intuition with models, tooling, and infrastructure economics — not slides alone.
- 03
Coalition building
Find the people who want civic-scale systems for the right reasons, and practice building with them.
- 04
First public experiments
Small, legible prototypes of the bigger thesis — local, useful, and hard to dismiss as vapor.
Ideas that keep returning.
AI research commons
Compute and expertise allocated toward causes, not only wallets — a center that feels closer to a library than a casino.
Automation with dignity
Robots and agents that absorb drudgery so people can do more caring, making, and governing — never the reverse.
Cities as systems art
Places like Omnia: designed for shared knowledge, health, movement, and contribution. Speculative, but studied.
Patience is a tactic, not an excuse.
This page will stay thin longer than the studio pages. That is honesty, not neglect.
Between now and then: read widely, prototype narrowly, talk to builders who have already bled on related problems, and refuse to confuse a mood board for a foundation.
Rules for touching the horizon file.
Earn the right to scale
Big systems inherit the ethics of their early habits. Practice fairness when the room is still small.
Prefer open over opaque
Communities deserve inspectable mechanisms — documentation, contribution paths, and clear stewardship.
Keep a tether to making
Abstract futures rot without concrete builds. Always have something running nearby.
The adventure is penciled in.
When the near work creates enough leverage, this chapter thickens. Until then it remains a lantern: visible, warm, and patiently ahead.