Diagnostic 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 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:
- A unique diagnostic code.
- 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
- Critical Failure: Vault Empty: Thrown when the Obsidian data vault is missing or empty.
- Content Validation Error: Validation failures on frontmatter metadata or required Markdown syntax.
2. Graph & Link Integrity
- Broken Link Detected: Detection of dead or orphaned links between files in the vault.
- Actions 404 Not Found: Failures to resolve dynamic routes or action handlers.
3. Module Resolution
- Module Load Failure: Failed imports of vertical-slice modules.
- Duplicate Module ID Detected: Constraint on module ID uniqueness.
- Circular Dependency Detected and Unresolved Module Dependency: Validation checks on the module dependency graph — see also Module Dependency Resolution for how the graph and load order are built.
- Core is not a module: Infraction of vertical-slice rules (prohibiting treating the core as a standard module).
- Hook Kind Mismatch and Hook Server Flag Ignored: Consistency checks on the
hooks:manifest key (logic hooks vs. UI/action zones).
4. Keys & Hotkeys (Launcher & Bindings)
- Duplicate Keyboard Shortcut and Launcher Trigger Collision Detected: Conflicts between global hotkeys or launcher trigger sequences.
5. Media Pipeline
- press.images — incomplete config: Incomplete or missing media outputs detected during processing.
6. Standard APIs & Clients
- CLI Reference: Developer framework CLI options.
- Core API Reference: HTTP REST API endpoints and payload schemas for standard.garden.
- Client CLI Reference: User command line interface specifications.
- Deep Linking Reference: Text fragments and Obsidian deep link integration protocols.