# Pascal Developer Platform

Source: https://www.trypascal.io/platform/developer-platform

Build on the business. Ship what it needs.

Create applications, functions, and integrations using Pascal’s business objects and APIs. Keep source, checks, review, and release connected.

## Capabilities

### 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.

### Connect the interface to the operation

Generated bindings connect a Work Surface to its declared data, actions, and agents. Keep those references with the project that uses them.

### Package reusable business logic

Use Forge for a calculation or business function. Inspect its code, test it, and review its version before choosing where it is activated.

### Integrate through the TypeScript SDK

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.

### Inspect changes before applying them

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.

### Keep access specific to the work

Choose credentials and permissions for the service or person making a request. A consequential function follows the operation’s authorization and review path.

## Connected context

Build internal interfaces with Work Surfaces, reusable functions with Forge, and system connections with Integrations. Use Workrooms to keep the implementation and review with the team.

- React source and static project configuration
- Typed bindings and supported SDK resources
- Code Tasks, builds, function versions, and releases

## Controls and permissions

Use the API of the product responsible for each resource. Workspace credentials and current permissions govern every request. Applying source, activating a function, and completing a business action remain separate steps.

## Example

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.

## Workflow

### Start from the operating project

- The Factory Control project connects the application to its requirements and intended users. The implementation has a clear business purpose.

### Inspect the source change

- Open the Code Task’s files and diff. Review the native components and project-local bindings alongside the checks and working-copy preview.

### Follow the release review

- The application review applies to its exact source and build. The separate lithium operating change still needs Operations and Compliance.

## Next steps

Bring an application, function, or integration idea. Identify its product APIs, permissions, and the path from local implementation to reviewed release.

- [Contact sales](https://www.trypascal.io/contact)
- [Software delivery](https://www.trypascal.io/solutions/software-factory)