Code scanning and mapping

Scanning turns your Domain Context into a map of your code. Forge reads your source, forms Code Parcels, and attaches each one to the context object it implements. A business concept stops being a description and becomes a precise place in the codebase.

IP Proof: your code stays on your machine

Scanning and mapping run inside the Forge VSIX extension, in your editor, with models and storage you choose. Mobioos does not connect to your repository, and source code is never sent to the Mobioos Fusion SaaS.

For teams that cannot send source code to a third party, this settles the first question before anyone asks it.

Code Parcels

A Code Parcel is the code associated with one context object, treated as a single unit. It can be a word, a line, a block, a file or a folder, and it can span several repositories and branches within the same project.

That granularity matters because business concerns rarely follow folder boundaries. One feature might be a few lines in one service, a validation in another, and a processing step in a third repository. A Code Parcel brings them together without asking your architecture to mirror your business model.

Inference and Markers

Code Parcels are built two ways, and they work together.

Inference is the process by which Mobioos AI selects code to form Code Parcels. During scanning, the ontology behind your Domain Context guides what the AI looks for, so a business framework is in place before the first line is read. Each inferred link carries a confidence score and appears under its context object in the Forge sidebar.

Markers are code you select by hand and attach to a context object.

A single Code Parcel can mix both. When an inference is wrong, correct it. When it is partly right, refine it. When you know something the scan could not, add a Marker. The mapping reflects what your team knows, not only what an algorithm found, and every correction is kept for everyone working on the Domain Context.

Controlling what is scanned

Two files, both working like .gitignore:

.mobioosignore excludes files and folders. Edit it from Ignore list in the indexing settings, or right click in your editor's explorer.

.mobioosinclude restricts scanning to what it lists. Empty means the whole codebase. On a large repository, starting with one bounded area gets you a usable map faster.

Running a scan

Open Indexing settings next to a Domain Context, then Indexing status, then Start indexing. A progress bar tracks the run.

Scans re-run according to the launch mode you set in Forge: On Save, On Demand, or Periodic. These settings are visible read only from Fusion and changed in the extension.

Languages

No language restriction. Forge maps the code you have, whatever it is written in.

Several repositories, several projects

A project can bring several repositories together, and a Code Parcel can span them. The reverse works too: several projects can point at the same codebase, so you can map the same code from different angles, one project per functional area, per team, or per migration you are preparing.

Volumes

Repository size and volume limits depend on your plan. See the pricing page.