Glossary

The Mobioos vocabulary, ordered so each term builds on the one before.

The chain from intent to code

Ontology. The semantic structure of a domain: its business concepts and the relationships between them. Ontologies are managed in Mobioos Fusion.

Domain Context. An instance of an ontology, applied to your project. The working unit, opened in a tab. It holds context objects, contents, members, statistics and versions.

Context Object. An element of a Domain Context, and the meeting point between business information and the code that implements it. It gathers information around one concept, whatever words or tools that information comes from.

Code Parcel. The collection of code selections associated with one context object, treated as a single unit. It can include words, lines, blocks, entire files and folders, and can span several repositories and branches within the same project.

Codebase. Your code, which keeps its technical structure. Mobioos adds a business reading on top of it.

Building the mapping

Scanning. The analysis of your codebase by Forge, with the language models you choose, to prepare it for mapping to context objects.

Inference. The process by which Mobioos AI selects code to form Code Parcels. The ontology behind the Domain Context guides it. Each inferred link carries a confidence score.

Marker. Code a developer selects by hand and attaches to a context object. A Code Parcel is the collection of code; a Marker is one manual way to define it. Markers and inference combine freely in the same parcel.

IP Proof. The Mobioos architecture that keeps code mapping on the developer's machine. Business context is centralized in Fusion; scanning and mapping run locally in Forge. Source code is never sent to the Mobioos Fusion SaaS.

Data from the software factory

Connector. A link between Fusion and a tool your factory relies on. See the available connectors.

Contents. The documents a Domain Context is built from: specifications, diagrams, data, recordings, written knowledge.

Polarization. Filtering the noise out of software factory data and projecting what matters onto the semantic structure defined by your ontologies. It is what makes a customer ticket and a line of code meet on the same business concept.

Endogenous information. Information that describes the implementation, such as a diagnostic tied to a code location or a defect in a function.

Exogenous information. Information that describes usage and intent, such as a customer ticket, a functional rule or feedback on behavior. The kind depends on the information itself: one ticket can hold both.

Context engineering

Context window. The amount of input a language model can take in at once.

Context bloat. More information in a model's context window than the task requires, often from large, repetitive or poorly scoped Markdown injected too broadly. It raises tokens, cost and latency, and leaves less room for what matters.

Context rot. The decline in a model's ability to use information reliably as context grows or fills with distractors. It can set in well before the context window reaches its technical limit. See Chroma's research on context rot.

Forge

Forge VSIX extension. The Forge extension for Visual Studio Code and compatible editors. It scans and maps your code, and carries the in-editor features.

Forge npm package. The complementary package that gives any editor access to Mobioos through Skills, Rules, MCP and CLI, once your codebase has been mapped with the VSIX extension.

Semantic code highlighting. Visual marking of the code mapped to context objects, whether identified through inference or through a Marker.

Business intent navigation. Finding code by what it does for the business, following the links between Code Parcels and context objects, without learning the folder structure first.

Enterprise context distillation. Retrieving the essential business context from polarized enterprise data, with the noise filtered out, grounded in the context objects of your Domain Context.

Context retrieval. The built-in prompt interface of the VSIX extension, used to pull relevant context from your Domain Context while keeping token usage down.

Dynamic Markdown context. Variables placed in your Markdown files that reference context objects. Forge fills them with the relevant business context and keeps it up to date.

Measures

Semantic data mapping quality. Of the total volume of data collected, the percentage that is mapped onto the model.

Code overlap rate. The share of your code that several context objects point at. Some overlap is normal; a high rate shows where model boundaries and code boundaries do not line up.

LOC mapped. Lines of code covered by at least one Code Parcel.

Lines of code and Files. Counted per context object. The first real answer to how much of a codebase a feature represents.

Data item. What connectors report for a context object. Reads No connector data available when nothing is attached, which is the fastest way to spot blind spots.

Modeling

Feature model. A model that expresses what is mandatory, what is optional and how elements combine, not just a hierarchy. Context objects are typed Core or Functionality and carry a Rule and a Children rule.

Subflow. A thematic grouping of context objects inside a Domain Context.

Version. A captured state of a Domain Context you can refer back to. MAIN is the working state where you edit.

Organization

Mobioos Fusion. The web platform where ontologies and Domain Contexts are managed and software factory data is polarized.

Organization. The top level container, holding teams, members and projects.

Team. A group of members inside an organization. Every invitation names one.

Contextualized Project. A container for one or more Domain Contexts and the repositories they map to, with the settings they inherit: service connections and Forge scanning configuration.