GFS Platform Flow Diagrams

If you have 60 seconds and want to understand how Jarvis (our chat) works end-to-end, look at this one diagram. Plain-language labels, top-to-bottom story: your team → chat brain → memory → Mike approves → NetSuite. Designed to print as a wall poster (1800×1300 viewBox). Use this before drilling into anything else.

If you only look at two diagrams, look at these. Both are wall posters at viewBox 1600x1180 designed for non-engineer users (admins, finance, K-12 buyers) to understand the whole system at a glance. Cloudflare Platform Canvas shows every CF service (Worker, D1, R2, KV, Vectorize, Queues, DOs, Workflows, Browser, AI, Email, 22 crons) laid out by category. Software & Services Canvas shows the broader estate — people, surfaces, NetSuite, Cursor, Codex, Anthropic, Dropbox — with auth flows annotated.

Three user-facing surfaces. User Workflow Guide explains what the chatbot can do for each role. Training Surface is how Mike feeds 15 years of GFS knowledge as structured corpus entries the R89 few-shot loop injects. Entity Brain Dump captures per-customer/vendor/item narrative context (primary contacts, payment quirks, sensitivities) the chat auto-injects when answering questions about that entity.

High-level views of the post-R93 platform. Whole-system overview is the recommended first-read: Inputs → Core → Data → Outputs with the R89 decision-corpus feedback loop highlighted. System architecture drills into the Cloudflare bindings + AI layer.

Each pillar diagram shows the intake → routing → tools → sources → response pipeline for a specific job function. Tools are role-gated (R85 CHAT_ROLE_FILTERS, R96 consolidated). R96 note: Order Mgmt now absorbs Inventory + Logistics + USDA functionality; Reports merged into All. Legacy pillar diagrams kept below as historical reference.

These 4 pillars were consolidated in R96 per architect Option C (.gfsmultiagent/architect/r96-pillar-decision.md). Diagrams preserved as historical reference to show the pre-R96 architecture. Inventory, Logistics, USDA functionality is now served by Order Management Admin; Reports tools are in All (admin catch-all).

End-to-end pipelines that span all pillars. Every chat call goes through the chat-pipeline. Every email goes through intake. Every sync round goes through sync.

Targeted workflow diagrams that drill into specific transactional flows. Useful for onboarding + cross-team alignment.

Seven explanatory diagrams Mike flagged as gaps. Intake unification shows every way a request can enter the system — emails + chat + admin + cron + webhook + direct API — converging at the event ledger and workflow runner. Memory + learning shows the 5 memory layers (reflexion, decision corpus, wiki, training loop, knowledge chunks) plus the curation state-machine that prevents poison. Five more close strongly-recommended gaps: Council v2 (replaces stale R91 chat pipeline), customer lifecycle end-to-end (Driscoll's journey), HITL security invariant (the 4-gate audit story), cost surface (~$1.50/day), and data lineage (NS → chat answer with watermarks).

Mike's substrate moves shipped (R549-R562) but lacked diagrams. These document how the new infrastructure actually works internally — the workflow runner, event ledger, HITL state machine, and customer health pipeline. Color-coded REAL vs STUB so you see at a glance what works today vs documented intent.