# STN013411 evidence boundaries and usage-rights context

releaseId: `20260919-v35`
knowledgeVersion: `2026.09.19-v35`
branch: `64`
track: `stn013411-symbology`

## Evidence hierarchy

Use the strongest available source for the question being answered.

### Semantic meaning / visual symbol

For entries present in the published visual catalogue, `iNGs_STN013411_plus.pdf` version 5.0 is a useful reviewed baseline. It distinguishes symbols "v zmysle STN 01 3411" from symbols "nad rámec STN 01 3411".

Do not call an entry normative merely because it lives in a similarly named library. `STN013411_plus` explicitly contains non-STN additions.

The visual/resource catalogue is sufficient for the published symbol meanings and `L/G/B` resource mappings it actually shows, including the table-6 `x` family rule. It is **not** sufficient evidence for broader STN 01 3411 drawing rules such as color policy; keep those unresolved until the primary standard or explicit project evidence is available.

### Current physical resource files

The current CEL/RSC snapshot supplied to GRAPHICO is newer than the 2012 PDF. For questions such as "which four resource files are currently maintained?" or binary identity checks, the supplied snapshot and its hashes are stronger evidence.

The KB does not claim that the 2012 PDF is a complete transcription of every current 2025 resource. Maintainer evidence says later evolution was additive and already defined entries were not changed incompatibly; therefore entries documented by the PDF can remain useful, while newly added resources may be absent from that PDF.

### MSet usage

An MSet source/example proves that a resource name was actually used by an instruction. It does not by itself prove that the resource belongs to the STN normative layer; classify STN versus `plus` separately.

## No silent semantic promotion

Keep these statements distinct:

- "STN 01 3411 defines this map symbol."
- "The STN013411 MicroStation resource set implements this symbol."
- "The plus library adds this practical symbol."
- "A particular MSet instruction uses this resource."

A correct resource name can still be the wrong professional choice for a project standard.

## Distribution/use context

GRAPHICO maintainer evidence records an operational agreement in the MSet/iNGs ecosystem: customers obtaining iNGs_Geo or MSet are granted the right to use this shared symbol resource set as supporting resources for those products.

Treat that as product-usage context, not as a general-purpose public redistribution licence. This KB does not grant or define rights to redistribute, resell, modify or relicense the CEL/RSC libraries outside the applicable product/customer arrangement.

The AI Hub publishes knowledge about the resources, not the binary CEL/RSC files themselves.

## Personal-name minimization

Public MSet KB provenance should avoid unnecessary full personal names. Where a current iNGs vendor contact must be identified for evidence continuity, use the compact form **`PB (iNGs)`**. Multiple modules referring to the same confirmation are cross-references to one provenance item, not multiple independent pieces of evidence.

## Fail-closed rule

If an exact symbol meaning, STN/plus classification, current resource name or target-workspace availability is not established by the published track/reference or user-supplied authoritative evidence, do not guess. Ask for the relevant catalogue/resource evidence or leave the item explicitly unresolved.