End-to-end flow
JT123820
One inquiry, all stages. Each box below is the actual artifact persisted by the pipeline — not a mockup. The brief asks: "does Kine actually work?". This page is the answer.
4 stages
- From: scrskarv@akerbp.comSubject: RFQ Details: 6000123714Body: 131 charsAttachments: RFQ Details.PDF
Show full email body
[You don't often get email from scrskarv@akerbp.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
Show extracted JSON
{ "language": "en", "intent": "new_inquiry", "customer": { "company": null, "contact_name": null, "contact_email": "scrskarv@akerbp.com", "phone": null, "vat_number": null, "address": null }, "items": [], "application_context": null, "attachments_referenced": [], "delivery": { "location": null, "deadline": null, "incoterms": null }, "previous_reference": { "is_update_of": "6000123714", "notes": null }, "completeness": "unusable", "missing": [ "customer_company", "contact_name", "phone", "product_items", "quantities", "specifications", "application_context", "delivery_location", "delivery_deadline" ] }- 3ok
Completeness verdict: unusable
Step 03Missing: customer_company, contact_name, phone, product_items, quantities, specifications, application_context, delivery_location, delivery_deadline
unusable- customer_company
- contact_name
- phone
- product_items
- quantities
- specifications
- application_context
- delivery_location
- delivery_deadline
Rule trace (deterministic)Verdict: unusable · no items extracted
Process map: see how this aligns with JS Cock’s diagram →