From the website, Telegram, ads or another connected source.
SYSTEM FAMILY / LEAD OPERATIONS
QUALIFICATION≠ AUTHORIZATION
One explicit path for inbound leads.
Intake, deterministic field checks and bounded model judgment can support qualification — then the workflow forks to an allowed CRM action or a human handoff.
What your sales team gets
A lead arrives. SEN handles the routine preparation before a person decides what happens next.
Collects the key details, checks required fields, flags duplicates or obvious junk and can create a prepared CRM card when a CRM is connected.
Sees the prepared lead and decides: call now, assign it, follow up or stop.
RESULT
Less copying, sorting and manual data entry. Your team spends more time talking to real customers.
CANONICAL FAMILY PATH
The registry is the family-level authority. The operating slice below is illustrative first slice, not a second taxonomy.
One bounded workflow shape.
Capability stays inside explicit authority.
Interpretation, extraction or classification gets a defined task — never open-ended authority.
Completeness, allowed values and routing remain inspectable outside the model.
Human approvals and actions are explicit per workflow. Capability is not authorization.
BOUNDARY RECEIPT / 05Workflow structure, not production performance.
NO FAKE METRICSNO LIVE DEPLOYMENT CLAIMHUMAN REVIEW PATHEXPLICIT FAILURE PATH