Time to authoritative answer
Median and p95 time from source-document registration to the first governed promotion, with incomplete pairs excluded.
Product · private development
Material agent work becomes one governed case.
Lagstyr keeps source evidence, explicit authority, accountable judgement, external effect, obligation, and outcome connected—without pretending that any one AI model, or any one of your existing systems, can hold the whole company’s judgement and memory.
Lagstyr in operation
One contract. Five visible stages. No inferred success.
The operator can follow a supplier contract from source evidence to outcome without creating a second workflow record. Every stage is derived from the authoritative records that already own it.
01 · Evidence
Can the source be relied on?
The signed document, its classification, where it came from, how each page was read, and whether it is due for deletion all remain visible.
02 · Human authority
Were the extracted terms accepted?
The exact frozen proposal, source spans, accountable decision, approval, and applied facts stay together.
03 · Scheduled work
What is now owed?
Notice, renewal, and delivery obligations remain owned, dated, and linked to the contract that created them.
04 · External action
Did the owning system confirm the effect?
Accepted, rejected, partial, unknown, overdue, verified, and reconciled effects stay distinct. A live connection into a real supplier’s system is still ahead.
05 · Outcome
Did the work produce an evidenced result?
Missing measurement stays not configured. An adverse or overdue result needs attention; it is never rounded into success.
Operating outcomes
Know not only what agents did. Know whether it was authorised, verified, and worth doing.
The outcome view is calculated live from records your installation already holds. It keeps no second copy of the numbers, compares you with no other customer, and estimates no ROI.
Human decision load
Proposals, approval decisions, and active corrections show how much accountable human work the operating model requires.
Deadlines and prevention
Recorded obligations show the deadlines found; actions the system refused because they broke policy show the exceptions prevented.
Actions and verified effects
Accepted, rejected, corrected, unconfirmed, and read-back-verified effects stay separate.
Cost per accepted outcome
Cost per outcome is calculated only when the costs and the outcomes cover the same period. If nothing was accepted, you see no unit cost at all—the system never invents one.
Time and benefit evidence
Recorded released minutes remain time evidence. Financial benefit remains unavailable until an authoritative amount and currency exist.
Five planes, one governed path
The model can reason. The operating layer controls what becomes real.
The architecture separates responsibilities often collapsed into a prompt, an orchestration framework, or a collection of logs.
Identity
Stable people, organisations, agents, suppliers, contracts, and external aliases across every system.
Record
Authoritative management records with source, provenance, history, obligations, and retention.
Projection
Queryable context and disposable derived views that never silently become company truth.
Action
Precisely defined proposals, safe to retry, acting through the specialist systems that own the transaction.
Governance
Mandates, approvals, policy, limits, conflicts, exceptions, containment, and governed change.
Authority is sacred. Derived views are disposable. An answer can always be regenerated; the reason a company acted cannot be.
The human operating surface
Attention, judgement, and consequence in one view.
The console holds no authority of its own. It brings the records that need human action into a coherent operating surface while the kernel remains the only validator.
Evidence-rich decision cards
The proposal, mandate, material evidence, conflicts, limits, prior decisions, and expected effect arrive in the same case.
Attention queues
Exceptions and material work route to the person who actually holds authority, rather than a generic approval inbox.
Journey progress
Not started, not configured, waiting, needs attention, and complete remain explicit across the full case.
Calculation definitions
Outcome measures carry their exact meaning beside the number, including exactly what evidence exists and where live proof stops.
Intended operating profiles
One kernel. Two ways to operate it.
Every installation locks to one of two operating profiles. They are intended operating models, not separate products or pricing plans—and neither can be installed until its proof exists in a real deployment.
Control Starter
Run by an approved partner, for you
Designed for complex smaller and lower-mid-market businesses that need curated connectors, assisted setup, business-hours support, and recovery from backup rather than a promised uptime percentage.
Authority Platform
Run by your own team, in your own cloud
Designed for customers that operate the deployment themselves: bring-your-own-cloud (BYOC—the product runs in your cloud account, not ours), your identity systems in charge, tightly controlled outbound connections, and no third-party root access.
Shared boundary
Same authority and lifecycle controls
Both profiles use the same isolated kernel, release lifecycle, recovery, deletion, and offboarding controls. Each installation still needs its own proof before it can rely on them.
Inspect the evidence behind the ambition.
The development record separates what is built and lab-tested, what is built but not yet proven live, and what is not available yet.