Build internal interfaces in React
Author Work Surfaces with ordinary TSX routes, scoped CSS, and Pascal UI components. Static project configuration declares the resources the interface uses.
Developer Platform. Create applications, functions, and integrations using Pascal’s business objects and APIs. Keep source, checks, review, and release connected.
Illustrative workflow with synthetic data.

Product walkthrough · Illustrative example
Read the transcript and visual descriptionsAuthor Work Surfaces with ordinary TSX routes, scoped CSS, and Pascal UI components. Static project configuration declares the resources the interface uses.
Generated bindings connect a Work Surface to its declared data, actions, and agents. Keep those references with the project that uses them.
Use Forge for a calculation or business function. Inspect its code, test it, and review its version before choosing where it is activated.
Configure an API endpoint, access token, and workspace for a service. Use the SDK’s supported resource contracts and the authenticated Developer Portal for the available API surface.
Work with Codex in a Code Task. Files and Changes show the working copy. Apply transfers the reviewed change to the project; release remains a separate decision.
Choose credentials and permissions for the service or person making a request. A consequential function follows the operation’s authorization and review path.
Inspect the Factory Control project, its implementation change, and the review behind the application release.
The Factory Control project connects the application to its requirements and intended users. The implementation has a clear business purpose.
Open the Code Task’s files and diff. Review the native components and project-local bindings alongside the checks and working-copy preview.
The application review applies to its exact source and build. The separate lithium operating change still needs Operations and Compliance.

In practice
A coding Task builds Factory Control with React routes, native components, and project-local bindings. The developer reviews the diff, checks, and working preview before applying the source. Engineering acceptance and explicit activation bring the application into use, with the operating policy review still tracked separately.
Example operation.Explore the solutionBring an application, function, or integration idea. Identify its product APIs, permissions, and the path from local implementation to reviewed release.