About
Maximize humanity's long-term ability to understand, build, survive, and flourish.
That sentence is the whole brief. Understand, build, survive, flourish. Each verb rules out a different failure: ignorance, helplessness, extinction, and a species that merely persists.
Long horizon by default
Most of what ME cares about does not pay back inside a quarter. An operating system, a volumetric display, power electronics, and orbital observation all take years before they are worth anything. Planning for that horizon means accepting slow milestones and refusing to inflate what exists today.
It also means planning shallowly on purpose. ME writes down the branch, the question, and the next demonstrable step, then stops. Deeper design happens when a branch is genuinely blocked without it, not because a document template asked for a five year plan.
Why so many fields
Breadth is not ambition for its own sake. The problems ME wants to solve keep crossing branch lines.
The blockers are elsewhere
A display needs materials. A robot needs power electronics. A satellite service needs compute. Narrowing to one field means waiting on the others forever.
Results transfer
Sensing work for a wearable feeds prosthetics. Command routing built for a projector is the same routing a robot needs. Work done once should count more than once.
The mission is not narrow
Understanding, building, surviving, and flourishing are not one discipline's job. A company scoped to one field would be scoped to a fraction of the mission.
Broad roadmap, narrow active scope
The principle that keeps breadth from becoming chaos.
The roadmap is allowed to cover everything ME intends to reach. The active set is allowed to hold only what a small team can actually finish. A project enters the active set when its next milestone is small enough to demonstrate, and leaves it when that milestone is met or the question turns out to be premature. Everything else stays on the map, written down, waiting, and costing nothing.
ME OS
The computing base. Agent execution, permissions, memory, and recovery belong to the operating system rather than to each application.
Carl
The agent layer. Products integrate against an interface boundary, so the model behind it can change without rewriting anything.
Research tools
Simulation, measurement, data capture, and experiment tracking, shared by every branch instead of rebuilt per project.
Manufacturing
Distributed automated production. Commodity inputs are bought, not made, when making them adds no strategic value.
Interfaces should be multimodal
One input channel suits one kind of body on one kind of day. ME intends its interfaces to accept several, so a person can use whichever works for them without asking for an exception to be made.
Wearable and muscle sensing
ResearchBracer based inertial and optical tracking, with surface electromyography as a research question. An input channel, not a medical device.
Eye tracking
ConceptGaze as a pointing and selection channel, particularly where hands are occupied or unavailable.
Voice
ConceptSpoken instruction through the same command path every other surface uses, so a voice command is neither more nor less privileged than a keypress.
Switches and adaptive controllers
ConceptSupport for existing switch inputs and adaptive controllers rather than requiring ME specific hardware.
Brain computer interfaces
ResearchA long horizon research interest, well outside anything ME is building. Mentioned because designing input paths that assume hands would foreclose it.
- Any control surface goes through the same command path, so a new input method does not need every application rewritten
- Calibration at first use and continuous adaptation, because people and conditions differ and change
- Text, contrast and motion settings respected rather than overridden
- No claim, express or implied, that any ME system diagnoses, treats or assists with a medical condition
None of these input devices exists. They are design intent, and ME makes no medical or health claim about any of them.
Public and internal
This site
This site. Static, read only, no accounts, no internal data.
Internal systems
A separate authenticated command center, planned but not built. It will live on its own host and share nothing with this frontend.
Criticism is welcome and useful. Tell ME what is wrong with this.