Management record
Stable identity, records, sources, provenance, documents, assertions, decisions, obligations, events, reports, retention, governed erasure, and legal holds.
Development status · 28 August 2026
Show the work. Name the boundary.
Lagstyr has moved well beyond a concept, but it is not a currently installable product. This page distinguishes implemented capability from configured deployment, live operation, and independent assurance.
How to read our claims
Built is not the same as available.
We use status language narrowly so a technical achievement does not become a commercial availability claim by implication.
Implemented
Built in the product code
The capability and its governing contracts exist and are covered by proportionate automated checks.
Reference-exercised
Run against controlled fixtures
The capability has been exercised through customer-neutral or clean-room reference journeys. This is not a live customer workload.
Under verification
Built or specified, with important evidence still ahead
Commissioning, live provider proof, deployment operation, corpus validation, or a broader assurance step has not yet been completed.
Not available
No current commercial or operational access
No installation, hosted environment, trial, pilot, demo, access programme, or production operation is being offered.
Implemented · reference-exercised
The authority foundation is substantial.
The following areas are implemented and exercised against controlled reference paths. Lists are capability groups, not a public API or availability commitment.
Authority kernel
Mandates, action classes, T0–T3 modes, proposal and approval, limits, conflicts, segregation of duties, containment, break-glass, restore, and immutable risk routing.
Operator surface
Attention queues, evidence-rich decision cards, operating registers, workflow controls, obligations, exceptions, measurements, and management reporting.
Agent work loop
Provider-governed context, typed tools, agent runs, tasks, proposals, approvals, effects, feedback, and controlled changes to prompts, skills, and models.
Effect verification
Idempotent action contracts, effect receipts, readback, reconciliation, outbound intent records, and ownership boundaries for specialist systems.
Measurement and reporting
Measurement contracts, results, costs, benefits, evaluation, feedback, structured report grammar, rendered reports, and closed-loop learning records.
Implemented · evidence still ahead
Some edges remain deliberately qualified.
These areas exist in code or supported contracts, but their most important proof depends on commissioning or live conditions that have not occurred.
Under verification
Customer-controlled deployment
The installation shape, isolation model, operations material, backup and restore paths, and clean-room journey exist. The intended proving installation is not provisioned.
Under verification
External system actuators
Several governed adapter and writeback contracts are implemented or partly implemented. They are not commissioned against a customer environment and are not presented as available connectors.
Under verification
Document-understanding edge
PDF parsing and extraction exist with provider-specific and corpus-dependent boundaries. Broad provider neutrality and corpus fitness are not claimed.
Under verification
Operational characteristics
Capacity, high availability, service levels, upgrade windows, and support response under real operating load require provisioned and observed deployments.
Explicitly not available
What you cannot obtain from Lagstyr today.
- A customer installation
- A hosted or shared sandbox
- A trial or pilot
- A product demo
- Early-access credentials
- A design-partner programme
- Production support or SLAs
- Certified compliance artefacts
The website currently collects expressions of interest only. Registering does not apply for access, place an order, or begin an evaluation.
Stay informed without an implied sales process.
Register for occasional development and availability updates. That is the complete current offer.