README

SchemaNode

 Executable Structured Semantic Language

 A low-level kernel that starts from the structured description of semantic entities and explores public semantic consensus and the multi-dimensional semantic space.

点击查看中文版

SchemaNode is not a low-code platform, form engine, ORM, or API documentation tool.

It attempts to decouple semantic definitions from concrete execution, so that semantics no longer depend on any single execution layer, but become a foundation that different execution layers jointly follow, interpret, and execute independently.

🚀 5-Minute Quick Demo

📖 Quick Start Guide
    - Semantic Type Configuration
    - Application Configuration
    - Workflow Configuration
    - Integration
    - Frontend View Customization and Usage

📖 Architecture Documentation

📖 Kernel Introduction

📖 App Dialect Introduction

💬 Design Discussions

---

 Example

Here is a simple MinMax struct type, the relation will use min value as max value's low-limit property as constraint, it works both WPF and web, also the backend, those types are platform in-dependent.

!minmax

---

 Core Idea

SchemaNode is not about writing business rules faster — it attempts to make business semantics themselves become structures that can be described, composed, and executed.

- Separation of Semantics and Execution: Business semantics exist as structured definitions, while concrete execution is the responsibility of the execution layer. The same semantics can be independently interpreted and executed in different execution environments.

- A Composable Semantic Foundation: Meta, Property, Relation, and Function serve as the current fundamental semantic primitives, from which higher-level semantic types and semantic dialects are constructed through composition.

- Public Semantic Consensus: Provides a common structural and processing foundation for semantic definitions in different domains, without prescribing in advance what business semantics all domains should use.

SchemaNode does not attempt to cover all domains. What it explores is a common foundation capable of defining, carrying, and executing different semantics.

 Practice from a Real-World System

An agricultural carbon-sink certification system with 700+ data tables for the first phase, involving extremely complex data associations, computation constraints, result traceability, and dynamic standards.

This was a real project completed in an era without AI assistance. Post-hoc evaluation shows that traditional development paradigms would require 120+ person-months, and due to the extremely high business complexity, smooth delivery was almost impossible in reality.

But under the design of "semantics and execution separation," a 4-person team completed the first phase of construction in 3 months — no overtime throughout and an extremely low bug rate. This drove us to think further: when data, constraints, associations, and rules are all described by a unified structured semantics, do they still need to