You don’t just use software; you design systems. This briefing provides the architectural framework of Luklak, enabling you to design robust, scalable, and elegant solutions for your enterprise. At its core, Luklak is not a suite of applications but a unified platform for building them. To design effectively, it’s crucial to understand its three-tiered structure.

​
The 3-Tier Architecture

Think of Luklak as a system with three distinct layers of abstraction, moving from foundational logic to user operation.

​
Deconstructing the Universal Object

The 🧊 Universal Object is the most critical concept to master. Every 🧊 Object you create is an instance of a specific Object Type, which acts as its blueprint. This blueprint defines the Object’s structure and behavior through two core components:

Workflows

The state machine that governs the 🧊 Object’s lifecycle, consisting of Statuses and Transitions.

Data Fields

The attributes or properties of the 🧊 Object. You assemble these fields into configurable Data screens to capture information.

​
Core Capabilities for Solution Design

As an architect, these are the primary tools you will use to build your solutions:
  • Object Connection: Go beyond simple parent-child links. Model complex relationships (1:1, 1:N, N:M) between any 🧊 Object types across any 📋 Function, enabling truly integrated systems.
  • Universal Automation Engine: The system’s central nervous system. Use triggers, conditions, and actions to automate processes not just within a 📋 Function, but across your entire Luklak environment.
  • Granular Governance: Implement robust security with fine-grained permission schemes and user roles, ensuring the right people have the right access at every level of the system.
  • Integration & Extensibility: Connect Luklak to external systems using tools within the Universal Automation engine. While Luklak does not offer an open inbound API, you can push data and trigger external processes via Webhooks or by making outbound HTTPS requests to third-party APIs. For secure and auditable integrations, always use dedicated Functional accounts to perform these actions.

​
Your First Solution Design: A Mental Walkthrough

Here’s how to approach designing a solution on Luklak—using a recruitment system as an example.
1

1. Deconstruct the Business ProcessFirst, identify the core entities (Candidate, Job Position, Interview), the data to capture for each, and the stages they move through (APPLIED -> SCREENING -> HIRED).
2

2. Define Your Universal ObjectsMap your entities to Luklak Object types. Candidate and Job Position become 🧊 Standard Objects. Interview becomes a 🧊︎ Sub-Object nested under Candidate.
3

3. Model Relationships with Object ConnectionCreate a many-to-many connection between Candidate and Job Position. Now you can easily see all applicants for a position, and all positions a candidate has applied for.
4

4. Design Cross-Functional AutomationMap out the key automations. Example: WHEN a Candidate’s status changes to HIRED, THEN create a New Hire Onboarding 🧊 Object in the separate HR 📋 Function and send an HTTPS request to an external payroll system.
What’s Next?