In private development

Agents do the work.
Your company keeps the authority.

Lagstyr is the system of record and control for delegated company work. It turns a material task into one governed case—from sourced evidence and explicit authority to accountable judgement, verified effect, and measured outcome—across the systems your company already uses.

Lagstyr is not currently available for installation.

The proposition

Machine-speed execution needs company-grade authority.

An agent can reason, call tools, and cross systems in seconds. But access is not authority, a trace is not a management record, and a confident output is not a decision. The more capable agents become, the more important it is that the company can answer: Who allowed this? On what evidence? What changed? What remains owed? Did it work?

Lagstyr is being designed first for owner-led and tightly managed companies moving agents beyond drafting and into material work—where founders, COOs, CFOs, company secretaries, and other accountable operators need the complete chain, not another summary.

One authoritative management record

From mandate to outcome, without losing the thread.

Lagstyr sits above the specialist systems that hold company facts. It records the authority and operating context that lets people and agents perform consequential work across them.

  1. 01

    Mandate

    Who or what may act, for which company, in what scope, within which value and time limits.

  2. 02

    Evidence

    Authoritative facts, source material, provenance, uncertainty, and conflicts assembled for the work.

  3. 03

    Decision

    The recommendation, accountable judgement, approval, refusal, exception, and reason stay together.

  4. 04

    Effect

    The authorised change reaches the system that owns it once, then readback verifies what happened.

  5. 05

    Obligation

    Commitments created by the decision remain visible, owned, dated, and linked to the original case.

  6. 06

    Outcome

    Results are measured against the decision so autonomy can widen, narrow, or stop on evidence.

Controlled reference evidence

Supplier renewal: from source document to governed work.

The implemented components are exercised against customer-neutral evidence. They show how contract facts can reach authority without a model silently promoting them. They do not claim one commissioned, live customer workflow.

01Ingest

Immutable source documents enter with identity, classification, and provenance.

02Read

Embedded text and supported scanned pages are processed on-box with typed page outcomes.

03Extract

Renewal dates, notice periods, clauses, and obligations retain exact source spans.

04Govern

An accountable person accepts or rejects the exact frozen proposal.

05Operate

Accepted facts and owned obligations become visible in the contract journey.

06Measure

The outcome view reports what is evidenced and leaves unconfigured value visibly absent.

Reference-exercised

Evidence to governed obligation

Document processing, supplier-renewal candidates, human promotion, contract facts, obligations, attention queues, and journey visibility are exercised on controlled paths.

Implemented · uncommissioned

External effect and outcome contracts

Typed effects, verification, reconciliation, measurements, costs, and benefit-evidence views exist, but live supplier-system and buyer-value evidence remain ahead.

Commissioning ahead

Customer proof

A buyer-owned corpus, live connector round trip, production installation, and observed operating outcomes are not claimed.

Product capability in private development

Built around the company’s authority, not the agent’s convenience.

Each label states whether the capability is reference-exercised or still needs commissioning. Customer and independent evidence are named separately in the development record.

implemented · controlled reference

Authority and action control

Mandates, action classes, graduated autonomy, value and scope limits, segregation of duties, containment, break-glass, and restore.

implemented · controlled reference

Operator and approver work

Attention queues and decision cards that bring the evidence, proposal, limits, conflicts, and accountable decision into one view.

implemented · synthetic-corpus exercised

Evidence and management record

Stable identity, governed records, page-level provenance, history, reports, obligations, decisions, and the chain behind consequential work.

implemented · uncommissioned

Verified effects

Typed actions, idempotent execution, readback, receipts, and reconciliation against the specialist system that owns the transaction.

implemented · controlled reference

Governed change

AI-system registers, impact assessments, exceptions, proposal-and-approval for material changes, and no silent agent self-improvement.

implemented · commissioning data required

Measurement and learning

Measurement contracts, costs, benefits, feedback, and outcome reporting that make wider autonomy an evidence-based decision.

Claim discipline: implemented means built and test-exercised. It does not mean deployed for a customer, independently certified, or generally available.

Earned autonomy

People control the moments that matter.

Oversight should be proportional to consequence. Routine work can proceed inside exact limits. Material commitments, exceptions, and changes to authority go to an accountable person with the evidence already in view.

T0 · retrieve

Read permitted sources. Search, classify, and assemble evidence without changing the source.

T1 · draft

Prepare a recommendation or complete action. A person independently decides and commits.

T2 · act with approval

Execute the exact typed action an authorised person approved, then verify the effect.

T3 · bounded autonomy

Narrow, reversible action inside hard limits, with continuous monitoring and automatic containment.

Agents cannot grant themselves tools, widen their limits, or rewrite the authority model. Human authority remains irreducible.

Customer-controlled architecture

The company record belongs inside the company boundary.

Lagstyr is being designed for customer-controlled deployment. Specialist systems keep their rightful authority; the runtime remains operable without Lagstyr’s vendor being online; model providers are selected and governed by the organisation.

BYOC direction

Your cloud, your deployment

The intended distribution model places the kernel, workers, database, and object storage inside infrastructure the customer controls.

Operating profiles

Partner-operated or customer-operated

Control Starter and Authority Platform define two intended operating models on the same signed kernel. They are profiles, not separately available products.

No runtime reach-in

Authority does not phone home

No vendor licence check, heartbeat, telemetry requirement, or management endpoint is intended to sit on the company’s runtime path.

Where things stand

Evidence before claims.

Lagstyr has a substantial implemented foundation and is being exercised through customer-neutral reference journeys and clean-room test environments.

It has no production customer installation, no public trial environment, and no independent security certification. We are not accepting installations yet.

Read the full development position

Free resource · no email required

The AI-native operating guide.

A vendor-neutral, five-document reference model for leaders building an AI-native organisation: architecture, phased delivery, proportionate governance, and honest benefits discipline.

Read and download the guide Free · ungated · Markdown