Quickstart

Last updated 1 day ago

From an empty account to code you can navigate by business meaning.

You will need: a Mobioos account, a supported IDE, and the documents that describe your product.You will end up with: a Domain Context linked to your code, in Fusion and in your editor.

1. Create your organization

Sign up at mobioos.ai and create your organization. It is the top level container: everything you build lives inside it.

2. Choose your plan

Payment comes once your organization exists, and is handled by Stripe. Plans and what each one includes are on the pricing page.

3. Create a project

The project is your working container. It brings together one or more Domain Contexts, the repositories they map to, and the settings they inherit.

4. Create a Domain Context and feed it

A Domain Context is an instance of an ontology: the semantic structure of your domain, applied to your project.

Open Contents and upload what explains your product: specifications, diagrams, data, recordings, written knowledge. Mobioos builds the model from those documents. Upload up to 20 files at a time, 100 MB each.

This is the step that shapes everything downstream. The more material you give it, the sharper the model.

5. Connect your tools

In Project settings, open Service Connections and connect the tools your factory already runs on. Fusion polarizes their data onto your Domain Context. See Connectors.

6. Install Forge and link your project

Code mapping happens in your editor, on your machine.

  1. Install the Forge VSIX extension in a supported IDE

  2. Click the Mobioos icon in the status bar, sign in, and select your organization or your personal workspace

  3. In the Forge sidebar, click Link a project, then select your team, your project, and your repository

Your Domain Contexts load into the sidebar.

7. Scan and map

Open Indexing settings next to a Domain Context. Choose your indexing strategy, embedding model, analysis model and vector storage, or keep the defaults to get going. Then open Indexing status and click Start indexing.

When it finishes, the scan has formed your first Code Parcels through inference. Review them, correct what needs correcting, and add Markers wherever you know better. See Code scanning and mapping.

You can now open a business rule and land on the code that implements it.