The Law–Markets–Data Triangle: Three Speeds, One System
Key Insights
- Law, markets, and data as three layers of one governance system — a governance protocol running in years, an incentive layer running in seconds, and an information substrate running in real time.
- How the temporal mismatch between them produces regulatory lag, enforcement asymmetry, and feedback loops.
Law, markets and data are usually studied as separate disciplines. This essay argues they are three layers of one governance system, each running at a different speed. Once you see the system, a great deal that looks like confusion — regulatory lag, enforcement asymmetry, flash crashes, surveillance — becomes a predictable consequence of clocks that are out of sync.
Three layers, three speeds
Think of any regulated economic act — a payment, a trade, a lending decision — as an event that passes through three layers:
- Law is the governance protocol: rules about who may act, under what conditions, with what evidence, and at whose risk. Its native unit of time is years. A statute takes months to draft and years to be interpreted into a settled meaning. Even fast-track regulation moves in quarters.
- Markets and money are the incentive layer: prices, contracts, and market mechanisms that coordinate behaviour through rewards and penalties. Their native unit of time is seconds to quarters. A price reprices in microseconds; an earnings cycle takes a quarter.
- Data is the information substrate: the records, signals, and models through which both law and markets observe reality. Its native unit of time is real time — a transaction is logged in milliseconds, a market feed in microseconds.
These are not three industries. They are three layers of one system, and each layer can only act on the evidence produced by the layer below it.
The temporal mismatch
The same act is therefore evaluated at three speeds simultaneously:
- Data records it in milliseconds. The event exists as a timestamped fact almost instantly.
- Markets price it in seconds. The event changes incentives and is reflected in prices while it is still fresh.
- Law judges it in years. The event is finally characterised — lawful or not, sanctioned or protected — long after it has been recorded and priced.
This mismatch is the regulatory lag that the other essays in this series explore. It is structural, not accidental: legislation is slow because legitimacy requires deliberation, and deliberation requires time. But the cost of that slowness is an enforcement asymmetry — fast actors exploit the window in which novel conduct is not yet characterised by law, and slow institutions can only react to the past.
Feedback loops, not one-way flows
Viewing the triangle as a cybernetic system (in Wiener's sense) reveals that the layers influence each other through feedback, not just in a single direction:
- Law → Markets: a new rule changes incentives, which changes prices and behaviour.
- Markets → Data: repricing produces new data, new volumes, new patterns.
- Data → Law: revealed patterns (money laundering typologies, market abuse, data breaches) feed back into legislation and supervision.
When a layer is missing or broken, the whole loop degrades. Without good data, both markets and law are blind. Without working markets, prices stop carrying information. Without legitimate law, neither layer has a stable frame to operate in.
Why the triangle matters here
This platform is organised around the same three layers. The Compliance pillar is the law layer — AML and regulatory rule frameworks. The Markets pillar is the incentive layer — market microstructure, volatility, trading. The Data Engineering pillar is the information substrate — pipelines, schemas, data contracts, governance. Reading the site as one system, rather than three silos, is the point of the cross-pillar synthesis.
The practical lesson: when you diagnose a problem in one pillar, check the other two. A compliance failure is frequently a data problem wearing a legal costume. A market failure is frequently a data problem wearing a microstructure costume. The triangle is the shared skeleton underneath.
Article Metadata
Bloom Taxonomy Questions
In your own words, what does each of the three layers govern, and at what unit of time?
Pick a regulated act (a payment, a trade, a data breach) and trace it through all three layers, noting where each layer reacts and how fast.
Is regulatory lag a bug to be fixed or a structural price of legitimacy? Defend your position.
Propose one mechanism that could shorten the law layer's response time without sacrificing due process.
Further Reading
Databricks Blog
Lakehouse, Spark, Delta Lake, Unity Catalog — engineering blog
Apache Kafka
Kafka documentation, KIPs, and ecosystem updates
Apache Flink
Flink documentation and release notes
Apache Iceberg
Iceberg table format — specs, REST catalog, performance
dbt Blog
dbt Labs engineering blog — analytics engineering, Semantic Layer
Dagster Blog
Dagster orchestration — software-defined assets, IO managers
Feynman Concept Cards
Master each concept: read the ELI5, explore analogies, work examples, and teach it back.
Law–Markets–Data Triangle is a concept in foundations. In simple terms, A cross-pillar framework describing law, markets/money, and data as three layers of one governance system running at different speeds: law is the governance protocol (years), markets the incentive lay
Analogy
Example
Find Gaps
Explain Law–Markets–Data Triangle as if teaching a colleague who is new to foundations. Cover: what it is, how it works, and why it matters.
Create
Create a diagram that demonstrates Law–Markets–Data Triangle in a real-world foundations scenario. Walk through your design decisions.
Show solution
A diagram for Law–Markets–Data Triangle should include: 1. The core components of law markets data triangle 2. How they interact 3. Expected outcomes or outputs
Regulatory Lag is a concept in regulations. In simple terms, The temporal gap between the speed of data (real-time), markets (seconds), and law (months to years). Because statutes move slowest, rules are always catching up to the behaviour they regulate, produc
Analogy
Example
Find Gaps
Explain Regulatory Lag as if teaching a colleague who is new to regulations. Cover: what it is, how it works, and why it matters.
Create
Create a diagram that demonstrates Regulatory Lag in a real-world regulations scenario. Walk through your design decisions.
Show solution
A diagram for Regulatory Lag should include: 1. The core components of regulatory lag 2. How they interact 3. Expected outcomes or outputs