Vertical.
One market worked as a whole: its chain, its roles, its segments, its words and rules; ready or visibly not ready
Figure 1Verticalspecified
- kind
- definition
- scope
- platform
- key
- its name
- store
- postgres
- family
- market
Fields#
| field | type | required | note |
|---|---|---|---|
name | text | yes | |
industries | [text] | yes | |
chain | id | yes | |
roles | RoleAroundADecision | yes | |
segments | [id] | yes | |
words | Word | yes | |
regulations | Regulation | yes | |
sources | Source | yes | |
kinds_of_signal | KindOfSignal | yes | |
state | Readiness | yes | |
industry_group | text | no | the industry family it sits in, from the seed catalogue |
applications | Application | no | the customer questions it is worked for |
systems_models | SystemsModelTemplate | no | the systems model templates that model its chain; a game of roles, where one is laid, is the template’s own; every role that a template’s flows or game name is one of the vertical’s roles |
Routes that use it#
/v1/read/verticalreturns it