SoulMesh
Architecture / Our approach

How the SoulMesh
framework is designed.

Useful AI needs more than a good answer. It needs the right information, clear limits, and people who can review what happens next.

Our approach separates those responsibilities so a recommendation does not quietly become a decision, and a proposed improvement does not become an unchecked change.

01 /

From information to action.

Four distinct responsibilities help keep useful assistance separate from permission to act.

  1. 01

    Information

    Understand the source, its relevance, and what is missing.

  2. 02

    Recommendation

    Explain an option, its evidence, and its uncertainty.

  3. 03

    Permission

    Check whether the person or system has authority for the intended action.

  4. 04

    Action

    Act within that authority and keep a record of what happened.

Illustrative example / Construction

Supplier quotes become a comparison, with exclusions called out. An estimator reviews the recommendation. Sending an order is a separate action, allowed only within the applicable authority and controls.

Existing permissions may cover an action. Where they do not, the system should seek the required approval—not assume it.

02 /

Learning from experience requires judgment.

A useful result on one project is not automatically a reliable rule for the next.

  • ConstructionAn estimate may depend on different ground conditions.
  • HealthcareA clinical outcome may involve a different patient population.
  • LegalA conclusion may depend on jurisdiction and facts.
SoulMesh’s approach / GSI

Experience informs change.
People govern its adoption.

Governed Self-Improvement (GSI) is SoulMesh’s approach to controlling how experience informs lasting change. Past work can suggest an improvement; it does not automatically establish a rule for future work.

Without careful evaluation, a lesson from one context can become an inappropriate assumption in the next. A proposed change must be assessed against its evidence, relevant conditions, and domain requirements.

People define the evaluation criteria and who can authorize a change.

From experience to reviewed improvement
  1. Establish contextIdentify the source, relevant conditions, and permitted use.
  2. Evaluate the proposalAssess the change against evidence, domain requirements, and defined criteria.
  3. Authorize bounded adoptionObtain human authorization for where the change may apply.
  4. Preserve traceabilityRetain the evidence and authorization behind the change.

The framework separates remembering an experience from adopting a lesson.

Improvement does not give the system permission to expand its own authority.

03 /

Clear responsibilities. Industry context.

Defined responsibilities.

The design separates information, recommendations, permissions, actions, and reviewed improvement.

What depends on the field.

Industry knowledge, workflows, integrations, and checks need to reflect the people doing the work. Exploring another industry starts with understanding those needs.

Nilo / Construction.

Nilo focuses on construction estimating and preconstruction, where source information, professional judgment, and clear authority matter at every step.

See Nilo on the homepage
SoulMesh’s framework is the subject of pending patent applications.
The full responsibility map

The architecture defines ten distinct responsibilities, each with a clear role.

Governance
Who has authority, what is allowed, and what must be recorded.
Boundary
How information, files, tools, and events enter the system.
Context
How information becomes relevant to the task and the field.
Reasoning
How recommendations, explanations, and alternatives are formed.
Trust
How outputs are checked against evidence and applicable requirements.
Memory
What may be retained, recalled, or used for reviewed improvement.
Interaction
How people express intent, review output, and give approval.
Prediction
How possible outcomes are explored with assumptions and uncertainty.
Execution
How authorized actions are carried out and recorded.
Reflection
How outcomes and feedback inform evaluation of proposed changes.
Bring your perspective

Have an idea for your industry?

Tell us about your experience, the problem you see, and who it could help. Let’s explore it.

Discuss your idea