From 486f65f6244d6f174816d72421ba96d6f21794cf Mon Sep 17 00:00:00 2001 From: mpmedia Date: Sun, 7 Jun 2026 10:45:52 -0500 Subject: [PATCH] Add example: taxonomy recommendations CSV --- examples/taxonomy_recommendations_example.csv | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 examples/taxonomy_recommendations_example.csv diff --git a/examples/taxonomy_recommendations_example.csv b/examples/taxonomy_recommendations_example.csv new file mode 100644 index 0000000..709926c --- /dev/null +++ b/examples/taxonomy_recommendations_example.csv @@ -0,0 +1,7 @@ +proposal_id,status,proposed_label,parent,reason,candidate_sources,notes +TAX-001,confirmed_existing,Clients/Resellers/Acme-Transit,Clients/Resellers,Base reseller label by participant domain,acme-transit.com,Domain presence in from/to/cc is enough — no subject qualifier needed +TAX-002,confirmed_existing,Clients/Resellers/Metro-Rail,Clients/Resellers,Base reseller label by participant domain,metro-rail.com,Domain presence in from/to/cc is enough +TAX-003,proposed_new,Finance/Purchase-Orders,Finance,PO/WO documents need their own label distinct from Sales/PO,Apps Script attachment scan,Use attachment filename pattern for classification +TAX-004,policy_note,participant-domain base labels,,Reseller/client labels should be additive,All reseller scans,"Even if Sales/Finance/Support applies, preserve reseller label" +TAX-005,policy_note,secondary work-type labels,,Sales/Finance/Support labels need tight keyword/attachment signals,All reseller scans,Do not use reseller domain alone for work-type labels +TAX-006,do_not_automate_yet,end-customer domains,,End-customer domains must not receive reseller label unless reseller participant exists,Manual review,"Flag with ! Rule Needed if pattern repeats — may need Studio flow for context evaluation"