KROG
🇳🇴

The records layer

Verifiable, not merely asserted.

Every change of position is recorded — append-only, cryptographically signed, with provenance and integrity proofs. Records use open standards so they remain meaningful outside our platform.

  • Consent record

    Permission given by a data subject, captured with purpose and basis.

    built to ISO 27560

  • Contract record

    Agreed terms between parties, with provenance of every change.

    PROV-O

  • Authorisation record

    Granted authority — who may act, for what, within what bounds.

    ODRL · VC

  • Right-exercise record

    An act invoking a held right, signed and time-stamped.

    PROV-O

  • Confirmation / receipt

    Signed acknowledgement that an event was received and accepted.

    built to ISO 27560

Consent is one record type among many. The records layer covers the full lifecycle of jural positions, not only personal-data permissions.

One worked example

The same object, through the whole chain.

Process, Records, Engine and Agents do not each describe a different example. They describe different stages of the same object: one consent under the Email Newsletter specification.

Object: Consent · sub_8f3c1a · DPS Email Newsletter (6d79e35089c96073)

  1. DPS
  2. Applicable rule
  3. Jural stateStatus: Roadmap
  4. AuthorityStatus: Roadmap
  5. Agent actionStatus: Roadmap
  6. Record
This page

Record

Status: Live

The proof, verifiable outside the platform.

The act leaves a consent record with a receipt built to ISO 27560 — append-only, signed, time-stamped, with provenance. The same object, now as evidence an auditor or a machine can read without access to the platform.

← Previous stageAgent actionStatus: RoadmapThe act, within given bounds.

Stages labelled Roadmap are designed, not operational today. They are never described in the present tense.