Update architecture diagram per feedback

- Core Backend centered, Core Web UI moved to left (uses API)
- Print now shows it can register assets with Core
- IoT card includes ERP integration bullet
- Updated diagram layout, connections, and description

TallyFlow/TallyFlow-Architecture.md

@@ -7,7 +7,8 @@
 TallyFlow is built around exactly **five primary components**, with **Core** as the central hub that owns the database.
 
 ### 1. Core (Central)
-- Go backend + Vue.js Web UI
+- **Core Backend** (Go) positioned in the center
+- **Core Web UI** (Vue.js) on the left — consumes the Core API
 - Owns MongoDB (assets, tags, photos, zones, events)
 - Single API integration point for all other components
 - Handles configuration, reporting, and orchestration
@@ -22,6 +23,7 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
 - Zebra ZPL-compatible label printing and RFID encoding
 - Includes **Print UI** for configuration
 - Can also be driven directly via the **Print API**
+- **Can register assets directly with Core**
 
 ### 4. Capture (PhotoTag)
 - Native mobile application (not Go/Vue)
@@ -33,12 +35,14 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
 - Rust-based service
 - Integrates fixed RFID readers (Impinj, Zebra) and environmental sensors
 - Pushes tag events and sensor data to Core (optional / dashed connection)
+- **Can integrate with ERP systems**
 
 **MongoDB** is not a standalone component — it is fully owned and managed inside Core.
 
 ## Data Flows
-- **Assets, Print, Capture** → Core: Solid lines (primary, always-available flows)
+- **Assets, Print, Capture** → Core: Solid lines (primary flows)
 - **IoT → Core**: Dashed line (optional, event-driven)
-- Core Web UI and Print UI are shown as sub-elements within their respective components
+- **Print** additionally supports asset registration back into Core
+- Core Web UI communicates with Core Backend via the same API used by other components
 
 This structure was verified by reviewing the actual source repositories in `~/src/`. All external modules interact exclusively through Core’s API layer.