Eiger: Auditable, executable, flexible legal regulations
summary
Eiger implements a domain-specific language embedded in Haskell that encodes regulations as dependency graphs of facts, pairs a domain expert with an engineer, and runs on real client data to deduce compliance. Implementation details include a heterogeneous dmap store, runtime instance lookup via packed edicts for JSON deserialization, a custom Iger monad for dependency tracking, and use of GHC.Generics plus OverloadedRecordDot. A demo runs a CBAM example and computed €31,077, a limited user study is anecdotally positive.
AI-written summary · about
chapters (8)
- 0:00Intro
- 2:17The Carbon Border Adjustment Mechanism -A case in point
- 7:24The Eiger model
- 8:59Benefits of using Eiger
- 16:43Design criteria
- 18:39Type-safe heterogeneity
- 21:03Runtime instance lookup
- 24:00Dependency tracking (2/2)
related talks
14mExecution domains in GHC/Haskell (Lightning Talk)
21mProduction Haskell Demystified
50mMaking Risk Decisions with Haskell at Scale
01h 26mReflections on Haskell@Meta
32mCode as Data: Extracting & Analyzing Info from Haskell Codebases
53mFalling Skies: Haskell Tooling and Ecosystem Growth
46mPainless software development with Haskell
01h 04mHaskell - A Peek Inside the Ivory Tower