Master Plan
An umbrella company for the electromechanical engineering gaps between collaborators. Five funded ventures, one unfunded design lab, one published budget. This sheet states the plan. Nothing on it is for sale.
§ 01 / Premise materials doctrine
Named for a material property
Elastic Engineering is an umbrella company. It fills the electromechanical engineering gaps between collaborators — the work that falls between a clinic's physics team and its service vendor, between a production line and the integrator who has moved on, between a finished design and the tooling required to build it. Where two capable parties meet and neither owns the joint, we take the load.
The name is not borrowed from software. An elastic material deforms under load and returns to form when the load is removed. Pushed past its elastic limit, it takes a permanent set: it keeps, forever, the shape of the worst thing that ever happened to it.
We design against permanent set. We conform to the customer's problem without taking a set from it — every engagement should leave the company in its original shape, ready for the next load. And we size the tool to the job, because force beyond what the problem requires is exactly how a part crosses its yield point. The doctrine is mechanical, and it is testable on every job we take.
§ 02 / The ladder allocation of funds
Each rung's output is the next rung's tooling
Elastic runs five funded ventures and one unfunded design lab, ordered as a ladder. Revenue enters at the top rung and funds the mission stepwise: no rung spends money the rung above it has not already earned, and every rung's output becomes tooling for the rung below.
| Rung | Venture | Alloc | Function |
|---|---|---|---|
| R1 | Service | 75% | Revenue engine. Funds every rung below. |
| R2 | miniFactory | 20% | Makes components — including its own. |
| R3 | Robotics | 4% | Non-humanoid material handling. |
| R4 | Sentinel | 0.8% | EM-wave detection, all wavelengths. |
| R5 | Thinktank | 0.2% | Field-engineer training. |
| — | Aerospace | 0% | Design lab. Drawings only. |
Allocations sum to 100.0%. Aerospace spends nothing by design.
R1 Service 75%
Field service under contract for complex electromechanical systems. The business is designed as a circular loop: field events flow into the CRM, and the CRM schedules the next field event — one system of record, closed on itself. Wearables are built to remove the administrative half of the job; the engineer narrates while working, the loop is designed so reporting writes itself, and the audit trail gets denser instead of thinner. Service is designed to host every Elastic software product in production, and it is the revenue engine that funds everything below it. Detail sheet: EE-DOC-101.
R2 miniFactory 20%
A compact factory that contains, within itself, the ability to make all of its own components. Build one and it can produce the parts for the next — self-replicating in the plain mechanical sense. Its near-term work is the fixtures, spares, and tooling that Service consumes; its long-term work is closing the loop in § 03.
R3 Robotics 4%
Non-humanoid machines for diverse material handling. Nothing here walks or shakes hands; these machines grip, lift, index, and convey, with shapes chosen by the load rather than by the operator's reflection. Built from miniFactory output, deployed inside Service contracts.
R4 Sentinel 0.8%
Electromagnetic-wave detection sensors across all wavelengths: WiFi, visible, infrared, ultraviolet, X-ray. One sensing discipline stretched across the spectrum, from the router band to the treatment vault. Sentinel instruments are designed to feed the Service audit trail.
R5 Thinktank 0.2%
A school for the intellectual training of field-engineering candidates. Field service needs people who can hold a whole system in their head at a customer site, alone, at 02:00; the Thinktank exists to produce them. Its graduates will staff the rungs above it.
— Aerospace 0%
An unfunded design lab. Problem statement: convert excess motion and thermal energy into human transportation energy. It spends nothing and accumulates drawings until the ladder can afford to build them.
§ 03 / Bill of materials closed loop
Four purchased inputs; everything else, made
Elastic purchases exactly four things. Everything else the company uses, it makes — and miniFactory exists to close that loop.
| Item | Input | Source |
|---|---|---|
| 001 | Human power | Purchased — hired, then trained (R5) |
| 002 | Compute | Purchased |
| 003 | Sensors | Purchased — until R4 supersedes |
| 004 | Raw metals / substrate-level chemical compounds | Purchased |
| — | Everything else | Made in-house (R2) |
This is the eco of the operation, stated in engineering terms rather than pledges: a closed industrial loop. What we refuse to buy we must learn to make, and what we make we can trust, repair, and audit. The fewer inputs that cross the company boundary, the fewer failure modes arrive by delivery truck.
§ 04 / The far goal 0% of budget
A number a skeptic can check
The far goal is a space elevator. The prerequisite is stated plainly: perfect collaboration across the entire engineering market — vendors, competitors, standards bodies, customers — and that is decades away. Every section above this one is practice for it.
There is also a material prerequisite, and it has a number. A carbon-tether space elevator needs a tether material with a specific strength around 48 MYuri — about 48 MPa per kg/m³ of density. The best mass-produced materials today sit far below that line: Zylon and T1000-class carbon fiber reach the 3–4 MYuri class. Laboratory carbon-nanotube samples have exceeded the threshold, but only at millimeter scale.
When a skeptic can check the number, the goal stops being rhetoric. Until the material exists, the elevator is a direction, not a line item.
0% of budget. 100% of direction.
§ 05 / Why we are cheap to believe no novel science
We bill for implementation, not discovery
Elastic does not bill for novel science. The operating doctrine is wise implementation of existing technology: proven components, arranged carefully, maintained relentlessly. That is where uptime comes from, and uptime is the product.
The customer is a sole focus, not a segment list: the holder of a service contract on a machine with strict downtime limits. Their revenue depends on the machine returning to form; ours depends on making it do so. The incentives align before any contract is signed.
And the budget percentages in § 02 are published on purpose. A public allocation is the honesty mechanism: drift is visible, anyone can compare the plan to the spend, and holding us to the number requires no trust — only arithmetic.
§ 06 / Status + contact no solicitation
Forming — Sunnyvale, California
Status: forming · Sunnyvale, CA · domain live
Elastic Engineering is forming in Sunnyvale, California. The domain is live. The first products — the Graph Generator and monitoring / QA tooling for field service — are in design. This document states a plan; it offers nothing and solicits nothing.
If part of this sheet intersects a problem you own, open a conversation.
End of sheet · EE-DOC-001 · Rev A · Supersedes: none. This document is replaced, not amended.