5.1 Reference Overview

This section indexes all fatal error codes, system validation checks, and diagnostic protocols built into the Standard framework.


The Principle of Documented Errors

One of the core laws of Standard (Standard Law 4.1) dictates that every critical system error must be self-documented.

When a compiler, a content-validation script, or the vault loader encounters a blocking anomaly, it does not simply output an opaque stack trace. Instead, it throws an exception containing:

  1. A unique diagnostic code.
  2. A direct hyperlink to the corresponding documentation page on stnd.build.

This allows the developer or editor to instantly understand the cause of the failure and follow the documented resolution procedure.


Classification of System Diagnostics

Diagnostics are grouped into several quality-control categories:

1. Vault Integrity

3. Module Resolution

4. Keys & Hotkeys (Launcher & Bindings)

5. Media Pipeline

6. Standard APIs & Clients

Are you absolutely sure?

This action cannot be undone.