Rename product TallyFlow IoT → TallyFlow Edge across vault
Update product naming in docs, marketing, architecture, use cases, and capabilities materials. Rename related notes, screenshot folder, and marketing image filenames. Keep git/repo identifiers (e.g. tallyflow-iot) and generic industry IoT language unchanged.
This commit is contained in:
@@ -32,7 +32,7 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
|
||||
- Focused on quality control and visual documentation
|
||||
- Sends data to Core via API
|
||||
|
||||
### 5. IoT
|
||||
### 5. Edge
|
||||
- Rust-based service
|
||||
- Integrates fixed RFID readers (Impinj, Zebra, ATID ATF862 / Invengo XC-RF861 — same reader rebranded) and environmental sensors
|
||||
- Pushes tag events and sensor data to Core (optional / dashed connection)
|
||||
@@ -42,7 +42,7 @@ TallyFlow is built around exactly **five primary components**, with **Core** as
|
||||
|
||||
## Data Flows
|
||||
- **Assets, Print, Capture** → Core: Solid lines (primary flows)
|
||||
- **IoT → Core**: Dashed line (optional, event-driven)
|
||||
- **Edge → Core**: Dashed line (optional, event-driven)
|
||||
- **Print** additionally supports asset registration back into Core
|
||||
- Core Web UI communicates with Core Backend via the same API used by other components
|
||||
|
||||
|
||||
Reference in New Issue
Block a user