docs: TallyFlow Scout marketing + Edge/Print/Capture feature refresh

Review tallyflow-assets-iot (TallyFlow Scout v0.5.3): Collect, Verify, Locate with Edge remote reader / offline CSV locate. Clarify Scout does not replace Core Assets. Refresh Edge, Print parent-container and multi- unit identity notes, Capture share/offline/barcode notes, architecture, use cases, capabilities, and website drafts after src/ repo pulls.
2026-07-27 15:59:32 -04:00
parent cf1e09e1c4
commit 8f4ed8a306
23 changed files with 292 additions and 151 deletions
@@ -1,33 +1,39 @@
 # TallyFlow Edge Review (repo: tallyflow-iot)

-**Tech Stack:** Rust (Cargo workspace) + Leptos (web UI)
+**Product name:** TallyFlow Edge (repo/package still `tallyflow-iot`)  
+**Tech stack:** Rust (Cargo workspace) + Leptos CSR web UI  
+**Branches reviewed:** `develop` through `81fa9d8` (July 2026 pull)

 ## Structure
- `core/`: Main service/library
-  - RFID drivers (Impinj, Zebra, ATID ATF862 / Invengo XC-RF861 — same reader rebranded)
-  - Barcode support (Zebra, SNAPI)
-  - REST API v1
-  - Real-time tag streaming
-  - Reader config/control
-  - Runs as an always-on Windows or Linux service
- `web/`: Leptos CSR web interface
-  - Reader health monitoring
-  - Live tag streaming with filtering
-  - Start/stop controls
-  - Imports types directly from `core` (no duplication)

-## Key Capabilities
- Hardware abstraction for multiple RFID vendors
- Real-time data pipeline from readers → REST → web UI
- Designed for always-on Edge deployment
- Strong documentation (REST_API.md, LIBRARY.md, etc.)
+- `core/` — service/library  
+  - RFID drivers: Impinj, Zebra, **ATID ATF862 / Invengo XC-RF861 (Master mode)**  
+  - Barcode: SNAPI / Aurora / wedge paths  
+  - **Remote reader** REST API (mobile/handheld submit — used by **TallyFlow Scout**)  
+  - REST API v1, live tag streaming, reader start/stop/health  
+  - **Reader-side filtering** (for quotes such as RMS tunnel/filter needs — validate in field)  
+  - Keyboard wedge + optional lookup filter (e.g. Assa Abloy patterns)  
+  - Egress processors: CSV logger, REST, AMQP → TallyFlow  
+  - **MCP** Streamable HTTP at `/mcp` (health, readers, tags; statistics-oriented skills expanded)  
+  - Windows Service install path  
+- `web/` — Leptos UI: reader health, live stream/filter, start/stop, improved statistics display  

-## Relevance to TallyFlow Platform
- Primary ingestion layer for RFID/Edge data
- Feeds the web app, reporting, and exception systems
- Complements tallyflow-web (which consumes the data)
+## Key capabilities (market carefully)

-## Next Steps for Review
- Inspect `core/src/` for reader driver implementations
- Review REST API endpoints in REST_API.md
- Check web/ Leptos components for UI patterns
+- Multi-vendor fixed RFID + remote/handheld readers under one site edge  
+- Unified tag feed → CSV / REST / AMQP  
+- Ops UI without vendor tools  
+- MCP read-oriented copilot surface (not autonomous dock control by default)  
+- Companion handheld: [[TallyFlow Scout]] (Collect / Verify / Locate)
+
+## Relevance
+
+- Primary **site edge** ingestion for docks, tunnels, and multi-reader plants  
+- Can feed Core via AMQP; can stand alone with CSV/REST and customer apps (e.g. Alice+Olivia console)  
+- Scout is the supported mobile remote-reader experience for Edge  
+
+## Next review steps
+
+- Confirm shipped MCP tool list vs docs after statistics/MCP skill commits  
+- Document ATF862 Master mode hardware prerequisites  
+- Field-test reader-side filtering before strong marketing claims