Your work has an address you chose

A project in Symphony is bound to one ground you declare — a single machine, your own network, or our hub. It stays there.

Being able to reach a server and belonging on it are two different things, and they are easy to collapse into one. We keep them apart deliberately: where your work lives is a decision you made, not a consequence of what your network can see.

Offline means offline

When the ground you chose is unreachable, Symphony stops and tells you — it does not fall back to a copy somewhere more convenient.

That is inconvenient, and it is the point. A boundary that gives way under pressure is not a boundary; it is a default that has not been tested yet. The only time it matters is the time it would have given way.

What you give up without it

You lose the ability to answer a simple question: where did our work sleep last night? Not through carelessness — because the system was built so the answer changes with the network. That is an awkward thing to explain to your own legal team, and a worse thing to explain to a customer.

The line we will not cross

Across this category, moving your work and its history between tools and machines is sold as convenience. It is the same mechanism by which a boundary dissolves.

We looked at building it and wrote down a refusal instead. It is a permanent record in our own system, not an unbuilt roadmap item — which is why we can point at it rather than just say it.

What we are not claiming

That every control enforcing this is finished. Some of it is still design. What we will say today is the posture: a project lives on one declared ground, and it does not widen because a network appeared.