# lagstyr > Lagstyr is the operating authority layer for agent-run companies: let agents act inside exact limits, stop at policy boundaries, and keep an independent record of every material decision and effect. Generated from the pages it lists (tools/build-agent-index.py). Where this file and a page disagree, the page is right. ## Entry points - [lagstyr — keep control when AI agents act](https://lagstyr.com/): Lagstyr is the operating authority layer for agent-run companies: let agents act inside exact limits, stop at policy boundaries, and keep an independent record of every material decision and effect. - [The AI-native operating guide — a free reference model from lagstyr](https://lagstyr.com/ai-native-guide/): A free, five-document reference model for business owners and executives: how a 1–500-person organisation becomes AI-native — architecture, phased plan, governance, and benefits discipline. Download the full markdown set, no email required. - [Company — why Lagstyr exists](https://lagstyr.com/company/): Lagstyr exists so companies can trust AI agents with real work without surrendering authority, operating memory, or accountability. - [Contact — write to the Lagstyr team](https://lagstyr.com/contact/): Send a message to the Lagstyr team — general, privacy, security, or legal enquiries. We read everything and reply by email. - [Development evidence — what Lagstyr has built, proven, and what comes next](https://lagstyr.com/development/): A dated evidence record for Lagstyr: what is built and lab-tested, what still needs proving in a real installation, and the gates on the path to availability. - [Privacy Policy — lagstyr](https://lagstyr.com/privacy/): How lagstyr handles personal information: no cookies, no analytics, no trackers. Issued by Vspry Australia Pty Limited (ABN 41 631 026 330), Brisbane, Australia. - [Product — keep AI agent action under company authority](https://lagstyr.com/product/): Lagstyr sits between agent intent and company consequence, enforcing mandates, evidence, approval boundaries, verified effects, obligations, and measured outcomes. - [Security — how to report a vulnerability to Lagstyr](https://lagstyr.com/security/): How to report a security vulnerability to Lagstyr: where to send it, what to include, what is in scope today, what happens next, and our good-faith research commitment. - [General Terms and Conditions of Use — lagstyr](https://lagstyr.com/terms/): The terms governing lagstyr.com, the free AI-native operating guide, interest registration, and the future Lagstyr platform. Issued by Vspry Australia Pty Limited. - [Trust — Lagstyr architecture, boundaries, and assurance position](https://lagstyr.com/trust/): Lagstyr's trust position: deterministic authority, local and explicitly approved processing routes, verified external effects, customer-controlled compute, and honest limits on current evidence. ## Machine-readable - [Any page as Markdown](https://lagstyr.com/): send `Accept: text/markdown` and the page arrives without navigation, decoration or layout. Every entry point above supports it. - [API catalog](https://lagstyr.com/.well-known/api-catalog): RFC 9727 linkset of what is on offer. - [Service description](https://lagstyr.com/.well-known/openapi.json): OpenAPI 3.1 for the above. - [Delivery status](https://lagstyr.com/status.json): capability statuses and the dated evidence log, generated from the development page. - [Sitemap](https://lagstyr.com/sitemap.xml): every published page. - [AI-native operating guide](https://lagstyr.com/ai-native-guide/): five Markdown documents, ungated. - [Content signals](https://lagstyr.com/robots.txt): search, ai-input and ai-train are all permitted. ## How to read our status language Claims on this site carry one of four labels. They are not decoration: they are the difference between what runs and what is designed. - **Built & lab-tested** — Works end to end on controlled test data - **Built, not yet proven live** — Exists in code; the proof needs a real installation - **Planned** — Designed, not built - **Not available** — Nothing to install, trial, or buy today ## What is authoritative - The pages themselves, and their labels. `status.json` carries the same labels as data, as of 2026-09-19. - [The handbook](https://lagstyr.com/docs/) is the operating documentation: operator, administrator and engineering sections, with a glossary. - [The development page](https://lagstyr.com/development/) is the evidence record, with dated entries. Nothing on this site is generally available today; the labels say what each capability is. ## Citing lagstyr Cite the page, its URL and the date you read it — and carry the status label with any capability claim, because it is what makes the claim true. For example: > lagstyr, *lagstyr — keep control when AI agents act*, https://lagstyr.com/, read YYYY-MM-DD (development evidence as of 2026-09-19). ## Contact - [Contact the team](https://lagstyr.com/contact/) — the form reaches a person. - Security reports: [security.txt](https://lagstyr.com/.well-known/security.txt).