Context assembly
In developmentGather the records and permissions an agent needs for a task into one packet before it acts; built for selected workflows, and packets are not yet saved for review.
Lamiak Core · 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.
The question
What does an agent see when it starts a task?
A packet put together for that one task: the records the step needs, the documents attached to them, and the permissions that apply. Assembly is built for selected workflows and runs ahead of the step it feeds. The packets themselves are not kept afterwards, so there is nowhere yet to open one and read what went in.
How it works today
In developmentWhat is built, stated as built.
Assembly is wired into the workflows that need it, and it runs before the step it feeds.
Assembled per task
The records and documents a step needs are gathered first, rather than left to the step to ask for them part-way through.
Bounded by the organisation
What may be gathered is limited to the records tagged to that organisation, and database access rules are set up the same way; known gaps in that separation are still being closed.
Selected workflows
Assembly is built where a workflow needs it, not switched on across everything a product does.
What is planned
PlannedWhat is designed, stated as designed.
Keeping the packet, and keeping the data it drew on, are designed and not built.
Packets kept for review
Saving each assembled packet so a person can open it afterwards and read what the step was actually given.
Snapshots to check against
Versioned snapshots of the data behind a run, so a result can be re-checked against the input that produced it.
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.
Separation between businesses
In developmentEach business's records are tagged to its organization, and database access rules limit staff to their own organization's data; known gaps in this separation are still being closed.
Dataset snapshots
PlannedVersioned snapshots of the feedback and outcome data used for training and evaluation.
The rest of Lamiak Core
The parts this one sits beside.
- 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.
- Workflows and approvalsSteps 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.
- 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.