1.2 KiB
1.2 KiB
| 1 | proposal_id | status | proposed_label | parent | reason | candidate_sources | notes |
|---|---|---|---|---|---|---|---|
| 2 | 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 |
| 3 | 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 |
| 4 | 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 |
| 5 | 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 | |
| 6 | 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 | |
| 7 | 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 |