Define
Create the system, units, commands, functions and supporting application structures.
HSK development keeps application structure, validation, configuration, inspection and KUMO composition inside the same ecosystem. The development process follows the organization defined by the language instead of introducing a separate model for each application area.
Create the system, units, commands, functions and supporting application structures.
Connect HCONF configuration and HSKON application data where the project requires them.
Check language structure, declarations, references, types and supported operations before execution.
Use Kagami Kensho for interactive inspection and diagnostic validation output.
Execute the validated HSK application or provide its KUMO routes and views.
The source defines the application through systems, units, commands, functions, stages, sequences, types and native control flow. The same structural model is preserved from the first file to the complete application.
Validation examines the HSK application before execution begins. Unsupported structures, unresolved references and incompatible operations are stopped before the application continues.
Kagami Kensho (Runtime Inspection & Validation) provides HSK-specific inspection through interactive and diagnostic modes.
Routes, pages, metadata, themes, forms and error views remain part of the HSK application and are composed by KUMO.
Structured application data, renderer definitions and theme information are represented through HSKON.
Application and service configuration is organized through compact HCONF files.
Report levels communicate application state, while validation and inspection provide detailed information during development.
DEVELOPMENT COMMANDS
HSK provides direct application execution together with Kagami Kensho inspection modes. These commands remain connected to the same source and validation rules used by the application.