Two products from one page
A WebForms page becomes two things in the target: a React screen and one or more API operations. Splitting them well requires knowing which code is presentation (show this panel, disable that button) and which is business behavior (the rate, the eligibility check, the write). PYD ENTERPRISES makes that split with program slicing and shows it beside the code-behind lines, so the React and API teams agree on the boundary before either starts.
PYD ENTERPRISES does not generate React components or ASP.NET Core controllers. It produces the OpenAPI contract, the decisions and fixtures, and a screen-flow diagram.
What the example reveals
The quote handler has a rule (rate by tier, smoker surcharge), a validation (coverage 10,000 to 500,000), and two review items. First, the tier is computed from a query string value on first load and then trusted from ViewState on postback; if ViewState MAC validation were ever disabled, the client could choose its own tier. Second, Math.Round(x, 2) rounds half to even, so a premium of 105.125 displays as 105.12. Whether the new service keeps that is a business decision, and the spec records it either way.