From f19114dc76728ad5000f943bd6094bf6d2d4a267 Mon Sep 17 00:00:00 2001 From: bxvtr Date: Fri, 15 May 2026 14:48:45 +0000 Subject: [PATCH 1/3] docs(readme): test bold --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index fa19876..9fbebee 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,7 @@ Execution, scheduling glue, and Control-Time Event injection when a Control Sche ```mermaid flowchart TB - R1["**Runtime**
canonical Event"] --> Entry["**EventStreamEntry**
canonical Event + ProcessingPosition"] + R1["`**Runtime**`
canonical Event"] --> Entry["**EventStreamEntry**
canonical Event + ProcessingPosition"] Entry --> Core["**TradingChassis Core**
CoreStep / CoreWakeupStep"] Core --> Result["**CoreStepResult**
dispatchable Intents + Control Scheduling Obligation"] Result --> R2["**Runtime**
dispatch / scheduling / I/O"] @@ -263,7 +263,7 @@ Control split, dispatchable Intents plus optional Control Scheduling Obligation the Runtime, and a boundary that makes parity and testing practical—not a second copy of decision logic per environment. -## Public Entrypoints +### Public Entrypoints | Entrypoint | Purpose | | --- | --- | @@ -276,7 +276,7 @@ copy of decision logic per environment. | `PolicyIntentEvaluator` | Protocol for policy admission (`evaluate_policy_intent`) | | Risk Engine (`RiskEngine`) | Convenience `PolicyIntentEvaluator` implementation | -## CoreWakeupStep semantics +### CoreWakeupStep semantics CoreWakeupStep is not "parallel Event processing". It is deterministic batch processing: the Runtime gives Core an ordered sequence of From 7c11a8a00db71d57526b95931e026174f10cd37d Mon Sep 17 00:00:00 2001 From: bxvtr Date: Fri, 15 May 2026 14:49:44 +0000 Subject: [PATCH 2/3] docs(readme): test bold --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9fbebee..877fc31 100644 --- a/README.md +++ b/README.md @@ -128,7 +128,7 @@ Execution, scheduling glue, and Control-Time Event injection when a Control Sche ```mermaid flowchart TB - R1["`**Runtime**`
canonical Event"] --> Entry["**EventStreamEntry**
canonical Event + ProcessingPosition"] + R1["Runtime
canonical Event"] --> Entry["**EventStreamEntry**
canonical Event + ProcessingPosition"] Entry --> Core["**TradingChassis Core**
CoreStep / CoreWakeupStep"] Core --> Result["**CoreStepResult**
dispatchable Intents + Control Scheduling Obligation"] Result --> R2["**Runtime**
dispatch / scheduling / I/O"] From f3f2c864d14b0534a1ef39711e8f1b5e00eccce8 Mon Sep 17 00:00:00 2001 From: bxvtr Date: Fri, 15 May 2026 14:50:38 +0000 Subject: [PATCH 3/3] docs(readme): bold --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 877fc31..8a5dee9 100644 --- a/README.md +++ b/README.md @@ -128,10 +128,10 @@ Execution, scheduling glue, and Control-Time Event injection when a Control Sche ```mermaid flowchart TB - R1["Runtime
canonical Event"] --> Entry["**EventStreamEntry**
canonical Event + ProcessingPosition"] - Entry --> Core["**TradingChassis Core**
CoreStep / CoreWakeupStep"] - Core --> Result["**CoreStepResult**
dispatchable Intents + Control Scheduling Obligation"] - Result --> R2["**Runtime**
dispatch / scheduling / I/O"] + R1["Runtime
canonical Event"] --> Entry["EventStreamEntry
canonical Event + ProcessingPosition"] + Entry --> Core["TradingChassis Core
CoreStep / CoreWakeupStep"] + Core --> Result["CoreStepResult
dispatchable Intents + Control Scheduling Obligation"] + Result --> R2["Runtime
dispatch / scheduling / I/O"] ``` Core never replaces the Runtime: the Runtime is responsible for feeding canonical