LEM Layered Event Modelling

New here? · The idea in motion

Layered Event Modelling

Three visual steps from a flat diagram to a 2-cell. Watch which edges carry a duration (Δt), which have none, and where a claim can break — then explore the patchwork below.

Scene 01 / 03 · Flat graph conflation
One flat chain — every arrow looks the same Substrate, event, record and norm sit on one undifferentiated line ? cause or record ? Δt or norm jump Hardware substrate Event change Log record Breach norm When every arrow looks identical, category jumps masquerade as causes. 01 · THE PROBLEM · FLAT GRAPH CONFLATION S5 Normative standing under a norm S2 Events causal chain, Δt S3 Representation record of a state non-causal, no Δt non-causal, no Δt Δt₁ (causal) Δt₂ (causal) time elapses along causal edges Duty Breach e₁ e₂ e₃ Log r₁ Log r₃ 02 · SEPARATION · CAUSAL = Δt · NON-CAUSAL = UNDEFINED, NOT ZERO 2-cell α · sealed face Preservation proof holds under side condition φ Lower chain safely realises the upper step Obstruction · open hole in cell Window Δt₂ exploited or box wall breached Upper claim no longer survives the crossing 1 atomic abstract step above A₁ A₂ Crossing c no Δt Crossing c′ no Δt Δt₁ Δt₂ window Δt₃ c₀ c₁ c₂ c₃ wall breach / race 03 · WORKING DRAFT v0.1 · 2-CELLS, NESTING, WINDOWS & WALL BREACHES

Project map · Bernhard Kreinz

The patchwork around LEM v1.0

This project is a patchwork growing around the LEM v1.0 core — itself an idea still being developed further. Published work, working drafts, code and essays sit around the center; empty patches mark ground not yet walked.

Filter the patchwork without moving the map:
Paper · Preprint · v1.0 extends core ↓

Typed CrossingsWhat Casts, Refinement Proofs and Chain-of-Thought Checks Carry Across a Boundary

Whether a claim survives reuse in another structure is a property of the map that carries it. Crossings declared by kind and preservation conditions — across Lean 4 casts, system refinement, and ML proof kernels.

14 Nov 2026 · 30 pp · DOI 10.5281/zenodo.24219769 · CC BY 4.0

Working draft · v0.1 · German next dimension ↓

Flächen statt LinienZweite Dimension und Schachtelung als fehlendes Strukturelement getypter Übergänge

A flat multigraph is one dimension short. 2-cells and nested boxes make preservation a closed face and side channels a wall breach. Re-reads Typed Crossings and sketches the next lem-lean.

Nov 2026 · Cell not yet closed

Empty patch unvisited

Beyond risk

LEM v1.0 states generality beyond cyber, operational and compliance risk as a hypothesis, not a result. No time to walk other domains yet.

open ground · not yet written

Code · Lean 4 formalises →

lem-leanMachine-checked core & crossings

Axioms A1–A6 as types, Δt on causal edges only, locality, three deontic primitives, trace faithfulness, and negative rejection tests. No sorry, no Mathlib.

v0.4.0 · lake build · Apache 2.0

Empty patch unbuilt

2D proofs & licensing

Nested 2-cells, the refinement case, and the licensing relation between the type-level stratum and the event graph — open in lem-lean.

open ground · not yet formalised

Core · Center Living idea

LEM v1.0

Layered Event Modelling: Semantic Separation as a Precondition for Explicit Causal Analysis

Semantic continuity across an abstraction boundary conceals the mechanism by which the boundary is crossed.

Object language and metalanguage kept apart: five structures (S1–S5), axioms A1–A6, six typed edge kinds, predicate and edge diagnostics, and a transition duration Δt that exists only on causal edges. Version 1.0 is the starting core — an idea still developing as the surrounding papers, proofs and essays push back on it.

17 Oct 2026 DOI 10.5281/zenodo.23438101 All versions CC BY 4.0
Instantiation · S2 ← instantiates

TLCTC v2.7Top Level Cyber Threat Clusters

The worked instantiation released alongside LEM v1.0: system, data and business risk events populating the event abstraction structure S2 across cyber, operational and compliance risk.

Released with LEM v1.0 · tlctc.net

empty patch · unvisited

Left blank on purpose — there hasn’t been time to go here yet.

Essays · Formal & Risk tests & applies ↑

Essays around the core

Empty patch open

Next core & cases

Hyperproperties, box composition, further worked examples, and whatever folds back into the next revision of LEM itself.

open ground · waiting for time

How to read the patchwork: solid cobalt is the LEM v1.0 core; tinted and quiet planes are published papers, code, instantiation and essays; the hatched rim marks a working draft (an open cell); dashed cells are empty patches left open because there has not been time to go there yet.

Inside the core: five structures, six edges

Usually drawn as one layer cake. LEM keeps them as separate orders: the event structure S2 crosses S1, S3 and S5 without being reducible to any of them. Edges are typed by what would have to be true for them to fail.

S1 Substrate

  1. Sites
  2. Hardware
  3. Execution environments
  4. Processes

what contains what

S2 Event abstraction

  1. System risk event
  2. Data risk event
  3. Business risk event

Δt on causal edges

S3 Representation

  1. World state
  2. Data
  3. Information
  4. Decision

what stands for what

S4 Epistemic access

  1. Evidence
  2. Observation
  3. Inference

detection lives here

S5 Normative

  1. Meta-layer: authority, competence, scope
  2. Rights
  3. Obligations
  4. Prohibitions

standing under a norm

Causal
One event brings about another. It may fail to fire or be interrupted. The only edge with a Δt.
Constitutive
One state is what others amount to. Synchronous: no time passes, nothing propagates.
Classificatory
Something meets a category under a declared scheme. Fails when criteria are unmet or the scheme changes.
Normative
An act, omission or state gives rise to a duty or breaches a norm. Fails when norm, scope or authority does not reach the case.
Representational
A record stands for its referent. Fails by misrepresenting, judged by comparison, not by time.
Evidential
An observation supports an inference. It describes access to the model, not mechanism within it.

After LEM v1.0, Figure 1 and §6. The worked instantiation is TLCTC, whose system, data and business risk events form S2; TLCTC v2.7 was released together with LEM v1.0.

How to cite

Cite the version you read. The all-versions DOIs resolve to the latest one. Drafts are not for citation yet.

Kreinz, B. (2026). Layered Event Modelling: Semantic Separation as a Precondition for Explicit Causal Analysis (Version 1.0) [Preprint]. Zenodo. https://doi.org/10.5281/zenodo.23438101

Kreinz, B. (2026). Typed Crossings: What Casts, Refinement Proofs and Chain-of-Thought Checks Carry Across a Boundary (Version 1.0) [Preprint]. Zenodo. https://doi.org/10.5281/zenodo.24219769