Leads and the team.
Leads and the team: the 11 calls this system serves, each a route of the API and a tool of the MCP server, at contract 0476e35e6e275db5.
Figure 1Leads and the teamspecified
Leads and the team
The 11 calls below are the whole of this system on the wire: each is one route of the API and one tool of the MCP server, with one typed input, one card as its answer and one refusal shape. Every answer carries its foot: what was read, the population and the control.
The calls#
| tool | route | takes | gives |
|---|---|---|---|
| si.ask.judge_fit | POST /v1/ask/judge_fit | Judges one entity against a buyer profile, and against a brand whose offerings’ fit is in question | The answer gives the fit with each criterion and its highlights, the temperature with its reason, and the verdict. It makes no lead |
| si.read.candidates | POST /v1/read/candidates | Reads the candidates of one brand, narrowed by a buyer profile or by a place | Each candidate arrives with the signals gathered about it, the rung it has reached, and what it still lacks to qualify |
| si.read.leads | POST /v1/read/leads | Reads the leads of one brand, narrowed by a place, a condition or a user | The answer gives the leads, or the package that holds them |
| si.read.speed_to_lead | POST /v1/read/speed_to_lead | Reads the delay from delivery to the first touch for one brand, over a window | The answer gives the measure’s readings, with the population each was read over |
| si.read.withheld | POST /v1/read/withheld | Reads the withheld count for one brand or one tenant | The answer gives the count by buyer profile and temperature, with the period and the limit it was read against |
| si.act.assign | POST /v1/act/assign | Assigns one lead to one user by hand, or hands it on | The answer gives the assignment, with the person who made it as its reason |
| si.act.capacity | POST /v1/act/capacity | Sets how many new leads one user can take in a period | The answer gives the new capacity, with how many the user holds and when it refills |
| si.act.mark_lead | POST /v1/act/mark_lead | Marks a condition on one lead, with a reason where the condition asks for one | The answer gives the lead’s new outcome |
| si.act.notification_channel | POST /v1/act/notification_channel | Writes one notification channel, which is where a notice goes | The channel is ready once its test notice is acknowledged. Until then it is not ready, with the reason |
| si.act.notification_rule | POST /v1/act/notification_rule | Writes one notification rule, which says who is told and never what happens | The answer gives the rule, with the next notice it will send |
| si.act.routing | POST /v1/act/routing | Writes, previews or arms a routing rule from a predicate and the people or the team it attaches | A write or an arm gives the rule. A preview gives the leads it would have admitted and who would have had them, read over history |
The bars this system enforces#
Every bar is a row of the parameter register: an administrator changes it, and the platform reads it by name at the place of enforcement the row records.
| parameter | family | dimension | enforced at |
|---|---|---|---|
| the longest wait of each place of a lead | machinery | a time for each place | the place’s reader, which notifies a user past it |
| the bar of fit of a kind of buyer, and the level of its interval | receive | a probability; a level | the judgement of a candidate (MODELS/the-fit-of-a-buyer-and-the-package-of-a-lead, sections 5 and 6) |
| the judgement policy of a kind of buyer: the stages that run and the bar between them | machinery | stages; a probability | the judgement, chosen by the measurement harness on its beat (the same model, section 7) |
| the recency window of an intent observation | receive | a time | the temperature of a lead (the same model, section 6) |
Claims#
| claim | state | route or tool |
|---|---|---|
| The platform serves 11 calls of Leads and the team at contract 0476e35e6e275db5. | target | si.ask.judge_fit |