A framework for deciding what to build
The four-layer model is the 23 Systems implementation framework. It helps a business identify missing foundations and avoid treating every problem as a reason to buy another tool. It is a teaching model, not a universal technical standard or a mandatory four-stage purchase.
Business applications can play two roles: a CRM may supply approved customer information to the knowledge layer and receive an approved task from the execution layer. Reading from it and writing to it require separate decisions.
Layer 1: business knowledge
Collect or retrieve approved information, organize it, retain its sources, and decide who may use it. Useful context includes current policies, decisions, customer records, and documented processes. Stale or conflicting information needs a resolution path.
Aibleto is being developed for this foundation. Its intended role is authorized, read-only context delivery. A read permission must not silently become permission to change the source system. Portability, access controls, and restore procedures need testing before production use.
Layer 2: AI assistance
This is where a person asks a question, reviews an explanation, or drafts an output with an appropriate AI tool. For a customer call, the request might be: “Summarize the current account situation and show the sources.”
The interface and model should be replaceable without discarding the business record. Replacing them still calls for evaluation: different models may interpret the same context differently.
Layer 3: agents and workflows
A workflow adds a trigger, defined steps, and an owner. Instead of waiting for someone to ask, it could prepare a briefing before a scheduled meeting. It needs rules for missing data, conflicting sources, failed connections, and escalation.
An agent can make some choices within those rules. That flexibility should be bounded by permissions, observable behavior, and a way for the owner to pause the process. More autonomy is not automatically more useful.
Layer 4: business execution
This is where approved work affects operational systems: creating a task, updating a record, or delivering a message. Each integration needs explicit authorization appropriate to its consequence.
For an early sales pilot, keep the briefing in draft form and have a person approve follow-up tasks. The knowledge service can remain read-only while a separate, authorized component carries out the action.
Controls run through every layer
Identity, permissions, source quality, review, auditability, and cost control do not belong at the end of the diagram. Check them at each boundary. Keep a recoverable copy of approved knowledge and document how the system continues if one provider is unavailable.
23 Systems designs and implements the appropriate combination of these layers, using existing products where they fit. Start with the smallest combination that resolves the bottleneck, then measure whether it earns expansion.