Approvals and decision records
In developmentSelected actions wait for an owner or admin to approve or reject them, and each decision is recorded with who decided and when; not yet switched on in a live product.
Human approval
Lamiak Core · Workflows 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.
The question
Where does a person have to say yes?
Where the policy for that workflow says so. The steps themselves are ordinary code with a defined input and output, so the same input walks the same path. Around them sit the points that wait for an owner or an admin, and each decision, whether it approves or rejects, is stored with the person who made it and the moment they did. This is partly built and exercised in testing; it is not switched on in a live product.
How it works today
In developmentWhat is built, stated as built.
Partly built and exercised in testing. It is not switched on in a live product.
Repeatable steps
A step is code with a defined input and output, so the same input walks the same path each time it runs.
Approval where the policy says
Which actions wait for an owner or an admin is set per workflow, in the policy for that workflow, rather than decided by the agent doing the work.
The decision is recorded
An approval or a rejection is stored with the person who made it and the moment they did, so the record of a run answers who decided.
What is planned
PlannedWhat is designed, stated as designed.
Carrying the same approval points into a customer's own systems is designed and not built.
Approval inside your systems
The same pattern applied to actions in the tools a business already runs on, rather than only inside our workspace.
Changes that move together
A change to scope or schedule recorded alongside the price adjustment it triggers, held until someone releases both.
What this leans on
The registry entries behind this page.
Each card carries its own status, taken from the registry rather than written here. How the labels are used is set out on the trust page.
Proposals
In developmentProposals with options that clients can review and choose from in the portal; sending a proposal waits for a person's approval, and delivery is still being built.
Human approval
Approval-gated agents
PlannedAgents that propose actions inside your systems, with a person approving and a record of each decision.
Human approval
Change requests
PlannedTrack scope and schedule changes with the approval and price adjustment they trigger.
Human approval
The rest of Lamiak Core
The parts this one sits beside.
- ContextWhat 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.
- AgentsAgents 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.
- Evaluation and learningMeasure 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.
- Deployment and governanceWhere 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.
Start with one workflow that matters.
We map the work, the systems it touches and the approvals it needs before anything is automated.