Migration and legal notes
How ROST should handle companies arriving from another operating-system framework without overusing protected third-party marks.
Some customers will arrive with experience in EOS, the Entrepreneurial Operating System. ROST can help them migrate their operating data, but ROST should not present itself as an EOS product, EOS-compatible product, certified EOS tool, or substitute copy of EOS materials.
Public-language rule
Use ROST vocabulary in product surfaces:
- Compass
- Responsibility Graph
- Seat
- Charter
- Steward
- Cascade
- Signal
- Friction
- Sync
If a public page needs to mention EOS, do it only to identify the source framework a customer may be migrating from. Keep the mention factual, limited, and accompanied by a non-affiliation statement.
Do not copy
Do not reproduce proprietary worksheets, templates, diagrams, branded meeting agendas, certification language, tool names as product primitives, or long expressive text from third-party materials.
Safe migration framing
Accept user-provided files as input. Translate their concepts into ROST structures. Explain the result in ROST language. Link to this note when a migration flow needs to clarify that ROST is independent and not affiliated with EOS Worldwide.
Agent guidance
Agents should not teach EOS as EOS. They should use ROST's method. When a user asks about a migration from EOS, agents may say that ROST can import and translate familiar operating-system artifacts into Compass, Responsibility Graph, Charters, Cascade, Signal, Friction, and Sync.