From ac83fffce6b8da9efb3f51fab8bba08c5d0259a9 Mon Sep 17 00:00:00 2001
From: bxvtr <148579658+bxvtr@users.noreply.github.com>
Date: Wed, 26 Aug 2026 16:37:18 +0000
Subject: [PATCH] docs: remove spacer images from README

Removed spacer images from README.
---
 README.md | 18 ------------------
 1 file changed, 18 deletions(-)

diff --git a/README.md b/README.md
index 99366c1..a7d6643 100644
--- a/README.md
+++ b/README.md
@@ -32,8 +32,6 @@ simulation, Live trading, Venue Adapters, and infrastructure around you change.
 > In-repo pointers: [`core/docs/index.md`](docs/index.md) and
 > [`core/docs/code-map/core-pipeline-map.md`](docs/code-map/core-pipeline-map.md).
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## Why it is relevant
 
 Trading systems often drift when Backtesting logic, Live logic, policy limits, and
@@ -66,8 +64,6 @@ decision engine itself. Wall-clock scheduling, Venue behavior, Venue Adapter
 mapping, latency, liquidity, market-data quality, and infrastructure failure modes
 stay in the Runtime, Venue Adapter, and Venue—not in Core.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## What it gives you
 
 | What you get | Why it matters |
@@ -91,8 +87,6 @@ differ and must be modeled outside Core. What Core removes is a major
 source of mismatch—duplicating and subtly diverging Strategy/Risk Engine/
 Execution Control itself.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## How it fits into a full system
 
 Backtesting Runtimes, Live Runtimes, and local Research or simulation harnesses can
@@ -116,8 +110,6 @@ Kubernetes, credentials, and operations-related). What stays stable is the Core
 pipeline and contracts; what varies by design is Runtime choice, Venue Adapter,
 Venue, and deployment.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## When to use `tradingchassis_core`
 
 - Building an internal trading system where Backtesting and Live should share decision semantics.
@@ -133,8 +125,6 @@ Venue, and deployment.
 - You expect this package to ship a full Kubernetes Runtime, deployment manifests, or production operations.
 - You expect Core to execute orders, talk to Venues, replace Venue Adapters, or perform external dispatch.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## Quickstart
 
 Run the quickstart
@@ -178,8 +168,6 @@ See `examples/core_step_quickstart.py` for a full runnable walkthrough and
 [`docs/how-to/use-policy-evaluator.md`](docs/how-to/use-policy-evaluator.md) for policy extension points.
 Planned U3 cleanup candidates: [`docs/roadmap/dead-code-cleanup-candidates.md`](docs/roadmap/dead-code-cleanup-candidates.md).
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## Full pipeline
 
 Internal processing pipeline, in sequential order:
@@ -230,8 +218,6 @@ Current Market Event baseline contract:
 - Runtime may normalize venue data into canonical Events, but Core accepts only
   the documented canonical reduction contract.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## Internally wired vs externally supplied
 
 The clean Core pipeline is always the same shape; some pieces run inside Core
@@ -268,8 +254,6 @@ built-in Risk Engine policy behavior. See `examples/core_step_quickstart.py` (mi
 Strategy code reads State and returns Intents. It must not mutate Core-owned
 State, Queue/inflight substate, or reducer-managed data.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## Input / Core / Output / Not Owned By Core
 
 - Input: `EventStreamEntry` values with canonical Events and Event Stream position.
@@ -332,8 +316,6 @@ canonical entries, and Core reduces them in that order before making one decisio
   then runs Policy Admission and Execution Control once.
 - Runtime dispatches after the returned `CoreStepResult`.
 
-<img src="https://img.spacergif.org/spacer.gif" width="1" height="32"/>
-
 ## Developer Commands
 
 From root: