What an .ospec contains
An .ospec is a structured specification containing the product model and supported presentation settings. It can describe components, connections, views, tables, requirements, evidence, feature scopes, theme and arrangement. Stable IDs connect records across those representations.
The filename extension identifies the intended use, but the reader validates the content. Legacy .atlas files remain supported under the compatible contract. Unknown optional metadata is preserved through supported full-file round trips; unsupported required capabilities are rejected explicitly.
Opening a file is local processing
The public reader parses your imported specification in your browser. Importing it does not upload the file to a 1view application database, and the free reader needs no account or connected agent endpoint. Your own agent performs source analysis in the environment you give it.
Local processing does not make the specification harmless to share. It may contain private service names, architecture, source references or other sensitive details. Review what your agent includes, exclude secrets, and use an appropriate channel when handing the file to someone else.
Browser storage is a convenience, not your archive
When available, browser storage keeps the imported product and local presentation changes so you can return to them. Storage may be unavailable, cleared or separated by browser profile and site origin. A different device will not automatically have your file.
Use File → Export .ospec for a durable portable copy. Keep it with the source revision and any review notes. Export before clearing site data or replacing a browser copy that contains arrangements or edits you want to retain.
A viewing link is not a hosted file share
A route can describe the selected product, view, feature or object. It does not contain or upload your private specification. A recipient following a link to a local product still needs a compatible copy of that file in their own reader.
For a handoff, send the exported file through your chosen channel and describe the feature or record to inspect. Recipients can open it locally. Links to the built-in fictional examples work directly because those example files are publicly hosted.
Preserve the complete explanation
Exporting while a feature is selected keeps the complete product, not only the visible subset. Feature layouts and whole-product arrangements remain distinct. Moving an object changes its presentation; it does not change the component’s responsibility or erase unrelated records.
When importing a replacement, read the preview and save the current copy if needed. After a source change, regenerate or update the specification and review its evidence; the reader does not automatically synchronize it. Return to the three-step workflow whenever you need to create a fresh account of a project.
Explore a fictional example, or open your own .ospec file locally.
Open 1view →