Views and service publication

Documentation status: tutorial — see Maturity and evidence.

Human review view

Create a review view that projects the current request, customer context, indicator list, assessment summary and decision fields. Bind functional components to named DataSource, DataSet and DataCursor surfaces. Keep local selection and navigation events inside the page boundary until a declared action is required.

A useful view composition is:

RiskReviewPage
  MainCursor -> current RiskRequest
  IndicatorDataSet -> request indicators
  DecisionDataSet -> current draft/final decision
  Summary -> request/customer details
  TabularView -> indicators
  DecisionPanel -> human input
  ActionPanel -> Validate / Finalize / Reload

Dashboard

A class-level dashboard can expose requests by status using conceptual collections. The view consumes the collection through its local cache; it should not own the provider protocol.

Published services

Publish stable business capabilities, not internal workflow helpers. SubmitRequest, ComputeRisk or StartReview are reasonable candidates when their signatures are stable.

The boundary is:

published action
  -> service adapter
  -> authentication/authorization
  -> parameter validation
  -> runtime action invocation
  -> structured response

Publication does not bypass process state or model constraints. The same action may be used locally, over RPC, through HTTP, by an agent or from a generated .NET client.