JS Cock’s process map, alignment view

Incoming Inquiries — v3

Re-drawn from your original diagram with stable step IDs (01–22) so we can refer to the same step unambiguously in chat, on the demo call, and on this page. Open in a new tab → · Original diagram →

What’s wired vs what’s next

1. 01.

   Sales Engineer delegates an inquiry to the AI Agent (Kine) via M-Files

   The inquiry itself is visible in the demo (M-Files stand-in folder). What's deferred to Week 2 is the live inbox watcher and the human delegate-to-Kine click.

   Deferred
2. 02.

   Kine extracts required information and maps it to a predefined JSON structure

   schema v1, see /inquiry/[jt] — JSON tab.

   Demo-implemented
3. 03.

   Is all required information available?

   Deterministic completeness rule — see the rule trace on /flow/[jt].

   Demo-implemented
4. 04.

   Kine sends an email to the customer requesting the missing information

   Drafted in original language (NO/EN); see followup card on /flow/[jt].

   Demo-implemented
5. 05.

   Kine receives the additional information from the customer

   Demo uses fixture replies under .tmp/jscock_customer_replies/.

   Demo-implemented
6. 06.

   Re-check completeness (loop)

   AI re-extracts the reply and merges with the original; see re_extract_merged stage.

   Demo-implemented
7. 07.

   Inquiry sent to Sales Engineer for manual JSON mapping (escape hatch)

   Real review UI is Week 2-3; demo shows the deterministic verdict only.

   Week 2-3
8. 08.

   Does the customer exist in BC?

   BC stand-in (SQLite) with 3 seed customers; lookup-or-create wired.

   Demo-implemented
9. 09.

   Kine creates the customer in BC

   Allocates BC# in C-2xxxx range. Persisted in the local stand-in DB.

   Demo-implemented
10. 10.

    Kine searches for suitable products in the catalog

    Vector index over 18.8k SKUs (sentence-transformers) + TF-IDF baseline.

    Demo-implemented
11. 11.

    Are all products available in BC?

    Demo-implemented
12. 12.

    Kine creates new items in BC

    Demo shows item creation path conceptually; full item-master integration is Week 2.

    Week 2-3
13. 13.

    Sales Engineer reviews and approves the new items

    Demo: ApprovalPrompt component on /flow/[jt].

    Demo-implemented
14. 14.

    Kine searches for suitable suppliers among 40+ in vector DB

    Demo uses a fictional ~5-supplier stand-in; real Qdrant index is Week 3.

    Week 2-3
15. 15.

    Kine sends inquiries to the two most suitable suppliers

    AI-drafted RFQ emails per supplier; see supplier_rfq_drafted stage on /flow/[jt].

    Demo-implemented
16. 16.

    Kine receives quotes from suppliers

    5 hand-written supplier-reply fixtures; AI-parsed into structured quotes.

    Demo-implemented
17. 17.

    Kine selects the most competitive quote using price + Targit data

    Deterministic scorer (50% price, 30% lead time, 15% completeness, 5% Targit-preferred).

    Demo-implemented
18. 18.

    Sales Engineer scores the quote and makes adjustments

    Demo: ApprovalPrompt component (note + edit + reject/approve).

    Demo-implemented
19. 19.

    Kine creates an empty quote in BC and assigns the customer

    Allocates Q-YYYY-NNNNN; persisted in stand-in DB.

    Demo-implemented
20. 20.

    Kine adds all products to the quote, including prices and delivery times

    Demo-implemented
21. 21.

    Kine links the BC quote number to the incoming inquiry in M-Files

    mfiles_writeback stage writes to .tmp/jscock_mfiles/<JT>/quote_no.txt.

    Demo-implemented
22. 22.

    Kine sends the quote to the customer

    Real email send is Week 3 — out-of-scope for the local demo.

    Deferred