Home /Modules/impl/SST.SYMBOLS.md

SST.SYMBOLS.md

impl/nordshrift/SST.SYMBOLS.md · 139 line(s) · markdown

SST Symbol Contract

NS-SST-0001 — SST Symbol Resolution Contract

An SST class or other named declaration is a compiler symbol, not merely text metadata.

Identity

The canonical identity is <package>.<symbol>.

Examples: sst.SLPackage, sst.SSTSymbol, nordshrift.NordshriftSymbol, vm.SleelaVMCompilerManager.

Short names are never sufficient for cross-package resolution.

Lifecycle

declared -> resolved -> emitted

A declaration that cannot resolve remains unresolved and is a compile diagnostic. An ambiguous reference is never silently selected.

Authority

The canonical filesystem-backed /lib collection and sleela::library::Index are authoritative. SST does not maintain a second package or symbol registry.

Symbol kinds

The normative kinds are: class, interface, function, field, constant, variable, module, package, type.

Compile path

.sst -> SST symbol table -> Nordshrift resolver -> /lib Index -> Nordshrift symbol table -> .sleela -> SLeeLa compiler

The SLeeLa classes in /lib/sst and /lib/nordshrift are the source-level contracts; impl/nordshrift/sst_symbol.* is the native resolution boundary.

Library class vocabulary (informative mirror)

The sections above are normative: /lib and the shared `sleela::library:: Index` are the single source of truth, and neither SST nor Nordshrift keeps a second registry. The list below is an informative snapshot of the package-qualified class vocabulary those layers resolve against, generated from lib/LIBRARY.SYMBOLS.md by tools/generate-vocab-appendix.py. It is a reading aid only; it carries no authority and must be regenerated (never hand-edited) when /lib changes.

<!-- GENERATED by tools/generate-vocab-appendix.py from lib/LIBRARY.SYMBOLS.md. Do not edit by hand; re-run the tool. -->

This appendix mirrors the 10995 package-qualified class symbols across 90 /lib package families, as recorded in the authoritative manifest lib/LIBRARY.SYMBOLS.md. It is informative: /lib and the shared sleela::library::Index remain the single source of truth, and nothing here constitutes a second registry. Each entry is resolvable as <package>.<ClassName>. Large auto-generated families (> 40 classes) are summarized by count and facade; smaller families list every class.