# STN013411 in MSet authoring releaseId: `20260919-v35` knowledgeVersion: `2026.09.19-v35` branch: `64` track: `stn013411-symbology` ## Default shared-set rule The STN013411/STN013411_plus set is a shared practical symbology resource for MSet/iNGs workflows, but it is **not universally mandatory**. Use this precedence rule: 1. **A directive/project-specific symbology set wins.** If the instruction is for a standard that supplies its own cells/line styles, use that explicit resource contract. 2. **Otherwise the shared STN013411/STN013411_plus set is the normal practical default** when its resources are available. 3. If neither a project-specific contract nor this shared resource set is verified, do not invent a cell or custom line-style name. Examples of domains that may prescribe their own resource sets include Jednotná železničná mapa, Digitálna technická mapa Bratislavy and map standards for motorway/road infrastructure. Their dedicated resources take precedence over the generic shared set. GRAPHICO confirms that MSet 2026 examples use the shared set where no special project resource set is required. ## When the user authorizes Starter Standards / STN resources If the user explicitly allows the shared MSet Starter Standards / STN013411 resources, do not remain artificially resource-free when the published catalogue already resolves a suitable symbol or line family. Use the exact semantic mapping from this track/reference. For an **illustrative/demo directive**, the authoring assistant may choose a reasonable concrete semantic subtype itself when that choice is not safety- or project-critical. Example: for a generic `elektrorozvod v obci` demo, choosing the NN family `6.602x` as one representative distribution feature is acceptable when the task does not require engineering completeness. If it chooses an overhead example, the family resolves to `lc=6.6025`; for an underground example, to `lc=6.6026`. It should state the chosen subtype, not ask the user to select every minor resource variant. For a **real project/engineering-specific directive**, the project standard and user-supplied contract still control the required network class and resources; do not invent NN/VN/VVN classification where that distinction materially matters. When a known family uses the catalogue placeholder `x`, resolve the requested/chosen line kind to the concrete suffix (`5`/`6`/`7`/`8`) before emitting `lc=`. Never emit `lc=...x`. ## Prefer line styles for continuous network features Where the catalogue offers both `L x` and `G ` for the same network meaning, current GRAPHICO/iNGs MSet practice strongly prefers the **custom line style** for normal continuous network drawing. Use the Graphic Cell alternative only when a local rotated symbol is intentionally preferable, when the line representation does not meet the task, or when a project-specific convention says so. This is an authoring preference, not a reclassification of the catalogue and not a universal MicroStation rule. ## MSet command relationship MSet instruction commands commonly select these resources through ordinary active-resource setters. Examples: ```text ac=6.120_ ``` selects the Point Cell resource `6.120_`. ```text ac=6.120 ``` selects the Graphic Cell resource `6.120`. A custom line-style resource is selected by its exact line-style name, for example: ```text lc=2.24 ``` The surrounding placement tool is a separate authoring decision. Resource selection does not by itself guarantee that the correct placement tool/state is active; apply the normal Instruction Author semantic/context check. ## Choosing B versus G The semantic symbol may have both Point (`B`) and Graphic (`G`) representations. The directive author chooses the representation according to intended placement behavior. Do not encode a universal rule such as "all utility symbols are Point Cells" or "always use Graphic Cells for map symbols". Relevant factors include: - whether active MSet/MicroStation symbology should be inherited at placement time, - whether the cell should preserve the symbology stored in its library definition, - desired view/orientation behavior, - desired snap behavior, - the professional convention of the particular directive. Load `reference.microstationCells` for the Bentley-documented Point/Graphic behavior before making this choice when the user has not already specified it. ## Example: active symbology matters If the directive intentionally establishes color/line style/weight immediately before a cell placement and expects the symbol to inherit those active attributes, a Point Cell is the relevant representation because Bentley documents its symbology as coming from the active settings at placement time. A Graphic Cell is different: its color, line style and line weight are determined by the cell definition when created. Therefore a sequence such as `co=...;wt=...;ac=` must not be assumed to recolor/reweight the cell merely because those setters precede `ac=`. This is general MicroStation behavior, not a special STN rule. ## Restricted-client retrieval rule For an STN task, retrieval is **progressive**, not all-or-nothing: 1. Prefer the published STN Markdown modules/resource catalogue and the general MicroStation cells reference. 2. If the MicroStation cells Markdown cannot be opened, try the explicit `microstation-cells.txt` transport before calling that host knowledge unavailable. 3. If any required STN Markdown source cannot be opened, use the validated `stn013411-bundle.txt`. That bundle intentionally contains the four STN modules, the STN resource catalogue **and** the general Point/Graphic Cell reference. 4. Once that STN bundle is release/version/integrity validated, do not require a second successful fetch of the same embedded cells reference for the same answer. 5. If the validated catalogue/bundle explicitly resolves the requested symbol, use the exact evidenced resource name. A failed alternate URL is not a reason to hide a resource that has already been authoritatively resolved. 6. Fail closed only for the specific fact that remains absent or unverifiable after the applicable transports have been tried. Example: if the task asks for an above-ground hydrant that should inherit active directive symbology, the validated STN material establishes `Hydrant nadzemný (B) -> ac=6.120_`, while the embedded/general cells reference establishes why `B` / Point Cell is the relevant behavioral choice. The exact resource name may therefore be returned even if the standalone cells Markdown URL itself was unavailable. ## Evidence-aware authoring examples Historical source instructions supplied to the MSet.AI project contain real resource usage such as: - `Hydrant nadzemný (B)` -> `ac=6.120_` - `Hydrant nadzemný (G)` -> `ac=6.120` - `Orná pôda` -> `ac=3.019` in one drawing workflow, - `Plot drevený` -> `lc=2.103`, - `Plot drôtený` -> `lc=2.123`, - `Ohradný múr` -> `lc=2.163`. These examples prove real MSet ecosystem usage and naming. They do not override a newer project-specific instruction or guarantee that every target workspace has the resources attached. ## Resource availability remains explicit Before delivering an instruction that depends on STN013411 resources, establish one of: - the target workspace already includes the shared libraries, - the user/project confirms they are available, - the package/deployment explicitly provisions them. If resource availability is unknown, state the dependency instead of fabricating a fallback name.