# iNGs_Geo integration - known limitations and evidence gaps

Status: **published / evidence-aware integration knowledge**

## Compatibility boundary

- **MicroStation through 2024**: explicitly covered by the published iNGs_Geo 11.70 manual.
- **MicroStation 2026**: current vendor operational confirmation from PB (iNGs), 2026-09-06; not an updated compatibility table in the 11.70 manual.
- **MicroStation 2025**: no explicit written confirmation in the current evidence set. Do not infer it solely from 2024 and 2026 evidence.

## `ig_preber` versus `ig_preberprvok`

Current MSet source uses:

```text
ig_preber 1 1 1
```

The current vendor manual documents:

```text
ig_preberprvok 1 1 1
```

and the full parametrized form of `ig_preberprvok`.

The manual does not document `ig_preber` as a separate alias. A historical/backward-compatible alias is plausible but **not proven**.

Current rule:

- keep the discrepancy visible;
- do not promote `ig_preber` as a documented alias;
- do not declare current MSet wrong until vendor clarification or current runtime evidence exists;
- keep this one point non-blocking for the rest of the integration track.

## Parametrized versus launch-only commands

Section 15.4 defines exactly 12 parametrized tools. Do not generalize that every `ig_*` launch command accepts parameters.

Current MSet also uses `ig_hektsiet` and `ig_legenda`. The manual documents them as command-line launch commands, but not as section-15.4 parametrized tools. Treat them as launch-only evidence and do not invent parameters.

## Availability / detection gaps

The current evidence does not define a supported MSet-side API/key-in for reliably detecting whether iNGs_Geo is installed, configured for the active Bentley environment or already loaded. It also does not establish exact failure behavior when an `ig_*` command is issued while unavailable.

Do not invent detection logic. If MSet later implements a supported detection mechanism, document it from current MSet source/spec/runtime evidence.

## Installation-path boundary

The 11.70 manual gives typical 64-bit paths for the Bentley environments documented at the time. Do not treat those paths as universal MicroStation 2025/2026 installation locations without separate current evidence.

## Runtime-verification boundary

The 2026 vendor confirmation establishes successful current operation of iNGs_Geo 11.70 with MicroStation 2026 as a product combination. It does **not** prove separate runtime testing of every documented `ig_*` command and parameter combination.

Keep evidence classes distinct:

- vendor-documented syntax = **documented**;
- overall 11.70 + MicroStation 2026 combination = **vendor operationally confirmed**;
- individual 2026 command/runtime claims = only when actually tested or explicitly confirmed.

When new evidence arrives, correct the smallest affected claim rather than widening or redesigning the whole track.