End-to-end flow
JT123017
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:Subject: #mostBody: 145 charsAttachments: image001.png, image002.png, image049624.gif
Show extracted JSON
{ "language": "no", "intent": "new_inquiry", "customer": { "company": null, "contact_name": null, "contact_email": null, "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": null, "notes": "References 'ramme avtale' (framework agreement) but no details provided" }, "completeness": "unusable", "missing": [ "customer_company", "customer_contact_name", "customer_email", "customer_phone", "line_items", "product_references", "quantities", "specifications", "delivery_location", "delivery_deadline" ] }- 3ok
Completeness verdict: unusable
Step 03Missing: customer_company, customer_contact_name, customer_email, customer_phone, line_items, product_references, quantities, specifications, delivery_location, delivery_deadline
unusable- customer_company
- customer_contact_name
- customer_email
- customer_phone
- line_items
- product_references
- quantities
- specifications
- delivery_location
- delivery_deadline
Rule trace (deterministic)Verdict: unusable · no items extracted
Process map: see how this aligns with JS Cock’s diagram →