the missing context · 01
The organisation is hard to read
Data lives in different systems. Processes are partly documented. People reconstruct the missing context through experience, messages, and memory every time the work is done.
The operating authority layer for agent-run companies · BYOC
lagstyr is the company-controlled operating spine for organisations putting agents to work: one governed memory, one authority model, and one execution surface across every system the company uses.
Why AI pilots disappoint
AI pilots can draft and summarise. They struggle when real work crosses several systems, depends on knowledge held in people’s heads, or requires someone to exercise authority. The model is not always the problem. The organisation is difficult to read, difficult to act within, and difficult to learn from.
the missing context · 01
Data lives in different systems. Processes are partly documented. People reconstruct the missing context through experience, messages, and memory every time the work is done.
the missing control · 02
Access to a system does not establish authority. An agent still needs to know what is true, what it may do, when it must stop, and who can decide.
Your people have been bridging these gaps manually for years. Agents make the hidden operating layer impossible to ignore.
Delegation of authority
A mandate says who may do what, for which company, up to what value, and until when. lagstyr checks it before consequential work proceeds—for people and agents alike.
Which legal entity may be bound. Authority in one company does not quietly carry into another.
The named person or agent holding the mandate—and the human accountable for the agent’s work.
What may be done, and to what, stated in business terms: prepare a supplier renewal, not call this endpoint.
How much may be committed. Anything above the limit stops or goes to someone who holds the authority.
From when, until when. Mandates expire; temporary cover is a dated grant, not a shared password.
When the facts fall outside the mandate—or an approver is conflicted—the action is stopped and routed to the right person.
An agent begins with no standing authority. It receives only the tools and mandate its role requires—and it cannot grant itself more.
The company operating spine
lagstyr does not need to own every fact to own the operating context. It connects the knowledge, decisions, authority, and actions that make the company coherent across all the systems it uses.
People, companies, suppliers, contracts, and agents keep a stable identity across every system in which they appear.
Knowledge and know-how accumulate around sources, decisions, and results instead of disappearing into disconnected tools.
Each fact keeps its rightful owner. lagstyr holds the mandates and decisions that let people and agents act across those facts.
People and agents act across specialist systems through one governed path, and each result informs what happens next.
Authority is the kernel. The company OS is the ambition.
Clear ownership
The ledger remains the authority for accounts. Payroll remains the authority for pay. Repositories remain the authority for code. lagstyr owns the context that connects their work into one accountable organisation.
the operating context
specialist facts
A specialist system can change without the company losing its memory, its authority model, or the reason work was done. The operating context stays with the company.
An operating spine, not a replacement suite
Xero can keep the accounts. GitHub can keep the repositories. Stripe can keep the payments. lagstyr keeps the shared context that lets the organisation remember, decide, delegate, act, and improve across all of them.
bring context in
lagstyr reads the systems you already use and preserves the source. Agents can see the whole operating picture without turning a copied summary into company truth.
act with authority
Once an action is authorised, lagstyr carries it out through the system that owns it and keeps the mandate, decision, evidence, and result together.
Specialist tools keep the transactions. lagstyr keeps why the company acted, who was allowed, and what happened next.
Autonomous in execution · accountable in authority
Routine work can proceed inside clear limits. Exceptions, material commitments, and changes to authority go to the right person with the evidence and reason already in view.
An agent gathers the evidence and prepares the action.
The mandate is checked. Where judgement is required, an accountable person decides.
The authorised change is made once, through the system that owns it, and recorded.
Gather evidence, never change the source.
Routine work inside an exact mandate; exceptions are routed to a person.
An agent prepares the action; an accountable person authorises it.
Changes to the operating spine always require approval; the proposer cannot sign off.
Agents cannot grant themselves new tools, wider limits, or a different mandate. Any change to their powers follows the same governed path. Human authority remains irreducible.
A practical starting point
lagstyr begins with recurring work that crosses systems, consumes human effort, carries real consequences, and can be measured. It starts in read-only or shadow mode and records how the work actually happens before more authority is delegated.
today · supplier renewal
The request arrives by email. Contract terms live in documents. Supplier history lives in accounting. Service performance lives elsewhere. Someone reconstructs the case, finds the approver, performs the action, and leaves little reusable record.
with lagstyr
An agent assembles the evidence, exposes missing or conflicting information, checks its mandate, obtains the required decision, acts through the system that owns the transaction, and retains the outcome.
The systems remain. The scavenger hunt disappears.
Process documentation becomes an output of doing the work—not a six-month prerequisite produced once and forgotten.
A practical adoption ladder
Begin by making the current work visible. Widen an agent’s authority only when the preceding step has shown that doing so is safe and economically useful.
Every rung preserves what happened and why. Evidence—not enthusiasm—earns the next level of autonomy.
Company controlled · BYOC + BYOM
The operating memory, agent context, and evidence stay inside infrastructure you control, on the models you choose.
BYOC
Bring your own cloud
Kernel, workers, database, and storage run inside your cloud account, VPS, or hardware. The company record stays inside your boundary.
BYOM
Bring your own model
Use the model providers and endpoints you choose. No hidden vendor default receives your prompts or company records.
No reach-in
No vendor on the runtime path
No licence check, heartbeat, or telemetry sits in the path of your company’s work. Your organisation does not depend on ours being online.
As models become more capable, they are trusted with more consequential work. That makes clear authority more valuable, not less.
No false promise
It is infrastructure for consequential delegated work—not a shortcut that turns a company into an agent-run organisation overnight.
it cannot decide for you
lagstyr will not make bad source data true, settle a disputed authority model, or turn a broken and politically contested process into a good one by itself.
use the simplest tool that works
If the need is only search, summarisation, drafting, or a dashboard—or one existing system already handles the workflow well—a simpler product is the better answer.
lagstyr matters when agents need to perform consequential work across systems—and the company needs that work to remain explainable, measurable, and under human authority.
Early access
lagstyr is in private development. We are speaking with founders, executives, and boards preparing to delegate consequential work to agents.