Try a product before analyzing yours
Open the Meridian Commerce example to see the complete experience. It is a fictional commerce system with cloud services, private infrastructure, databases, queues and feature views. You can explore it without an account or a file of your own. Its content is a demonstration, not a claim about a real deployment.
Start with Architecture. Select a service, inspect its relationships, then visit Data or Behavior. The representations share the same underlying records, so you can keep following the same idea across layers.
1. Give your agent the instructions
On the homepage, choose Copy agent prompt. Paste the prompt into a coding agent that has authorized access to your project. You can also download the instruction file and give it directly to the agent. The browser reader does not inspect your repository or run the analysis for you.
The instructions define staged analysis, source accounting, evidence, validation and explicit prohibitions on changing the analyzed project. Tell the agent which repository and source revision are in scope, and identify anything it must not access.
2. Get one .ospec file
Your agent investigates the project and produces an .ospec file. That file describes entities, relationships, diagrams, requirements, evidence and presentation settings. Ask the agent to validate it and report unresolved gaps before delivering it.
A structurally valid specification can still miss an important service or misinterpret a flow. Review the source revision, coverage notes and uncertain findings. A partial result with explicit gaps is more useful than a confident diagram built on guesses.
3. Open the file and choose a question
Choose Open .ospec, or drop the file onto the homepage. Review the import preview and open the specification. If a product already exists in browser storage, the preview explains the replacement and offers a way to preserve the previous copy.
Choose a concrete question: where does a request go, how does a feature work, or which tables depend on this one? Use the layer controls and right-hand artifact list to reach a relevant object. The anchor icon centers it in the working plane.
Save what you want to keep
Arrangements and browser copies are retained locally when browser storage is available. Use File → Export .ospec to keep a portable copy, especially before clearing browser data or changing devices. Exporting from a feature view retains the complete product specification.
Next, learn how to read a technical architecture or follow one feature end to end.
Explore a fictional example, or open your own .ospec file locally.
Open 1view →