Design Philosophy
Minyu is built around the five core architectural characteristics found in most business systems: a structured data model, a rule engine enforcing correctness and access, views for interacting with information, integration capabilities, and data processing. Its purpose is to standardize and stabilize as much of this foundation as possible—through declarative configuration where feasible and straightforward extensibility where custom logic is required—delivering a cost-efficient, predictable base for building internal systems.
Data Model
Every business system begins with a representation of entities and relationships. Minyu treats the data model as the system’s foundation: it defines everything else, including forms, search structures, scheduling logic, and the GraphQL API.
The platform provides tools for defining tables, attributes, and relations while automatically generating keys, indexes, constraints, and type-safe schemas. Because the model is declarative and centralized, the entire system updates instantly when structure changes.
This ensures that the complexity of the domain is expressed directly in the schema, not hidden across UI logic or duplicated API definitions.
Rules and Logic
Rules determine what is allowed, visible, or valid. In Minyu they are expressed declaratively, follow relationships of arbitrary depth, and are evaluated uniformly across UI, API, imports, and scheduling.
Instead of embedding logic in custom code or scattered validations, Minyu centralizes constraints and state logic in one engine. This allows complex conditions—structural, conditional, temporal—to be defined without programming.
The outcome is predictable enforcement across all system entry points.
Views and Interaction
Minyu’s interaction model is entirely data-driven. Views are constructed from data patterns (time, classification, numeric values, relations) rather than predefined “modules.” Because views are linked to the structure itself, they remain reusable and consistent across domains.
Forms, lists, calendars, explorers, and charts are generated automatically from the model and rules. Navigation follows relations directly, preserving context, and enabling multi-view workflows for high-throughput users.
This ensures a stable, predictable interface that adapts to the data, not the other way around.
Data Exchange and Integration
Business systems rarely operate alone. Minyu provides a complete, model-driven integration layer:
- imports that preserve relational integrity
- exports with full relationship context
- GraphQL schema auto-generated from the model
- event notifications for deep relational changes
Because all integration points are derived from the same schema and rules, external systems always interact with consistent, validated data.
Data Processing
Some operations—billing logic, logistics, payroll, payments—are domain-specific and unpredictable across organizations. Minyu does not attempt to generalize or embed these processes. Instead, it focuses on the structural backbone that all systems share while providing clean integration surfaces for the specialized pieces that belong elsewhere.
This keeps the system lean, maintainable, and predictable, and avoids the complexity trap where no-code systems attempt to replace domain-specific engines.
Conclusion
Minyu’s design philosophy is simple but rigorous: make the five invariant characteristics of business systems declarative, centralized, and consistent, and allow domain-specific processes to plug into that foundation. This produces a system that is stable under complexity, adaptable over time, and efficient for organizations that need control without building everything from scratch.