Lamiak Core
The system underneath every LAMIAK product.
Lamiak Core is the layer under every agent: it assembles context, routes each step, holds actions for approval, and measures what happened. Parts of it are built and tested today; every part below carries its current status.
The loop
Understand the work.Act with control. Learn from outcomes.
The loop in the abstract, then each of its stages with the status it carries in the registry today. No stage is offered to customers yet, and each product page shows its own status.
01 Context
What the system knows: records, documents, permissions, history.
02 Action
What an agent or workflow does, inside the rules you set.
03 Outcome
What actually happened, recorded with its evidence.
04 Learning
What changes next time, promoted only after review.
The stages, today and next
Today
Context
In developmentGather the records and permissions a task needs into one packet before an agent acts.
Approval
Human approvalIn developmentHold selected actions for a person, and record who decided and when.
Routing
In pilotSend each step to the right model for the task and the sensitivity of the data.
Evaluation
In developmentScore agents against suites and graders before trusting a change.
Feedback
In developmentCapture edits, rejections and outcomes from the people doing the work.
Next
Dataset snapshots
PlannedFreeze feedback and outcome data into versions a decision can cite.
Model registry
PlannedOne identity for every model, adapter and prompt, with its evaluation history.
Promotion gates
PlannedA candidate proves better on evaluation before it is given authority.
Training from outcomes
PlannedAdapt models on outcome data a customer has agreed to share.
Next is where the loop closes: outcomes become data, data becomes a candidate, and a candidate earns its place on evaluation before it is given authority.
The complete list, including the parts that are not loop stages, is on the Trust page.
The five parts
Each part, and how far along it is.
One page per part. Each separates what is built today from what is designed, and carries the status of the registry entries it rests on.
Context
What the system knows before it acts.
Assembling the records, documents and permissions a task needs into one packet, before an agent is allowed to do anything with them.
TodayIn developmentAgents
Agents that propose, inside limits you set.
Bounded agents that draft and propose rather than act, with each step sent to a model or to plain code depending on what the step is.
TodayIn developmentWorkflows and approvals
Steps that run the same way, and the person who decides.
Ordinary repeatable steps, with a person approving where the policy for that workflow says so, and each decision recorded with who made it and when.
TodayIn developmentEvaluation and learning
Measure first, then decide what changes.
Evaluation suites and graders run by hand today. Scorecards, promotion gates, dataset snapshots and training from outcomes are designed and not built.
TodayIn developmentDeployment and governance
Where your records sit, and what governs a change.
How records are kept apart per organisation, which outside services receive data and why, and what would have to be true before something changes.
TodayIn developmentStart with one workflow that matters.
We map the work, the systems it touches and the approvals it needs before anything is automated.