KROG
🇳🇴

How we work

Lawyers as Legal Engineers.

A four-step flow from specification to running compliance to agent-actionable tasks.

  1. Step 01

    Write a DPS

    Legal Engineers describe data activities in a Data Processing Specification — the single source of truth.

  2. Step 02

    Generate compliance documents

    Privacy notices, ROPA entries, DPIA inputs and contract clauses are derived from the DPS.

  3. Step 03

    Generate consent requests

    Requests are issued and recorded through the Consent API, with receipts built to ISO 27560.

  4. Step 04

    Generate agent task descriptions

    Machine-readable task briefs tell authorised AI agents what they may do, and within what bounds.

One specification, one state.

Same pattern as above — but here against the EU AI Act. Each Article 10 obligation is expressed as a state you can query.

Context

Personal data used to train a high-risk AI system

Data governance state (live) — EU AI Act, Article 10

Governance states

  • Data availability & quantityArt. 10(2)(e)Sufficient
  • Data suitabilityArt. 10(2)(e)Partial
  • Relevance & representativenessArt. 10(3)Sufficient
  • Error-freeness & completenessArt. 10(3)Partial
  • Contextual / geographic suitabilityArt. 10(4)Unknown
  • Bias examination & mitigationArt. 10(2)(f)–(g)Sufficient
  • Data gaps identified & addressedArt. 10(2)(h)Not met

EU AI Act Art. 10 documentation status for each high-risk AI system under your responsibility as provider.

Because each obligation is expressed against governed vocabularies, its state is a query — not a reconstruction. That is what an auditor, and an AI agent, can both read.