Occam4 Engine

Avoid implementing the same change in several places

When a business field changes but data, screens, validation and agent tools diverge, defects follow. Occam4 is the Giz foundation for composing these elements around declarative models. Separate ownership of models, screen editing and server execution without maintaining duplicate copies of the same state.

Five core architectural building blocks

Occam4 operates on model-driven principles, deriving all user interfaces and runtime contracts deterministically from single-source-of-truth models:

• Data Models:
  • Responsibility: Declaratively define business fields, data relationships, type constraints, and primary source mappings
  • Connected Result: Strictly uniform read projections and safe, atomic transactional inputs across all interfaces
• View Models:
  • Responsibility: Hierarchical composition of forms, data grids, ECharts visualizations, pivot tables, and dashboard layouts
  • Connected Result: Responsive, dense enterprise user interfaces optimized for mobile and desktop screens
• Server Actions:
  • Responsibility: Type-safe input validation, multi-tier authorization (ACL/ACE), and transactional state machine transitions
  • Connected Result: Fully verified execution paths with strictly contained side effects and zero duplicate logic
• Content Governance Contracts:
  • Responsibility: Author-reviewer separation, cryptographic revision hashing, immutable revisions, and single-click restoration
  • Connected Result: Fully auditable, compliant public web presence and internal enterprise knowledge repositories
• Tool & Agent Contracts:
  • Responsibility: Define parameter schemas, permission boundaries, and structured output projections for AI agents
  • Connected Result: Autonomous AI task execution adhering strictly to the same business rules and permission envelopes as human operators

Business users and developers compose together

Edit screen structure and properties in the visual designer. Developers extend data connections and server actions where required. Inspect save state and conflicts in the shared editing session. Public enterprise pages follow content review and publication after screen changes are saved.

Implementation acceptance

Model a representative workflow and test it from input to completion. Verify that a field change remains consistent across connected screens, access and error handling remain correct, and existing screens and data stay intact. Check complex interfaces, integrations and large datasets in the actual configuration.

No-code and business applications · Visual designer · Platform architecture