← Futures
Speculation · 5–20 years · AMP and Fractal Engine

The twin that outlives the account

Escherbridge

Speculation. Not a roadmap, not a delivery date.

This is speculation. It is not a roadmap and it is not a promise. The horizon is somewhere between five years and twenty, which is a polite way of saying we do not know, and we are not going to pretend a quarter.

The habit today is a digital twin that lives in someone else’s account. The model of the building is real enough to demo. The exit is a project. Papers on the public record already describe the trap: vendor-specific platforms, a cloud that is hard to leave, and an edge that the suite was not built to reach. Our own engine is a mirror, and the README says so. A coordinate is rounded. A forecast is a guess with a confidence on it.

The version worth wanting is quieter. The site keeps a local record. Peers can sync it without a single host being the building. A query can leave for a spreadsheet or a warehouse the operator already has. When the contract ends, the hashes and the files are still the operator’s. AMP is the runtime that has to keep working beside the place. Fractal Engine is the memory that has to admit it is a likeness. Both are incomplete relative to that picture. AMP’s public kit is a spatial SDK and a live creator house, not a finished export story. Fractal Engine is alpha, with plugin admission that fails closed and signature fields that are still zeros.

If that picture arrives, it will look boring. A town, a feeder, or a floor will have a twin that still opens on a Tuesday after the login does not. The coordination problem will not have been solved by a larger dashboard. It will have been solved by the record surviving the account. We do not have a year for that. We have the direction, and the gaps written down.