Pascal Framework
Connect the systems your business already runs on.
Build agents, workflows, and applications around their data.
Developer access is arranged with Pascal. Public package installation is not yet available.
Product walkthrough · Illustrative example
Read the transcript and visual descriptionsBuilt on your business
Enterprise software is rarely a blank project. The company already runs on decades of tables, events, integrations, approvals, batch jobs, and operator knowledge.
A Pascal project connects those systems through shared business objects, processes, and actions. Build the workflow that crosses them, the interface your team needs, and the review that makes a change accountable.
One project. A connected operation.
Follow an illustrative supply-chain project from connected source records to business logic, workflows, and the applications people use.
Bring manufacturing orders from SAP, lot custody from the production system, and shipment milestones from logistics. Keep each record connected to the system responsible for it.
sources/Illustrative supply-chain system. Explore the layers to follow the connections.
Graphs, state machines, process models, workflows, simulation, optimization, models, and human decisions become more powerful when they share the same business state.
Process mining reconstructs what actually happened from legacy events. A durable workflow takes over at the deviation, coordinates people and agents, survives long waits, and verifies the result in the owning system.
Explore the product
The ontology gives a scenario the real network of orders, assets, suppliers, inventory, and constraints. Simulation and optimization compare changed worlds before an intervention touches production.
Explore the product
Agents receive typed evidence and domain tools. Policy, workflow, and approval keep their recommendations within the same permissions and review requirements as every other operator.
Explore the product
Reviewed cases give the next candidate something concrete to improve on. Compare results against the current approach, inspect important failures, and bring the evidence into release review.
Explore the product
A complete operating example
A temperature alert starts in one system. The response needs records, decisions, and actions from several. Here is how the pieces can work together.
SAP owns manufacturing orders, the MES owns lot custody, and the logistics network owns shipment milestones.
Pascal connects those records into related orders, lots, shipments, plants, suppliers, promises, and available actions.
A temperature event changes the Object Set and exposes a deviation from the expected shipment and production process.
An agent drafts a containment plan, Atlas compares scenario branches, and a workflow collects the required approvals.
Check the result in the system that performed the action. Use later cost, service, and safety observations to inform evaluation and future improvements.
An illustrative supply-resilience system. Apply the same pattern to the objects, decisions, and controls that define your operation.
Define a process in code and check it locally. Inspect the compiled bundle before connecting a workspace to publish it.
Request developer accessBuild a Work Surface in React. Connect it to declared data and actions with typed bindings, then review a working preview.
Work SurfacesRead business records and call supported actions through the TypeScript SDK. Keep workspace credentials on the server.
Request developer accessConnect Python analysis to supported Pascal APIs. Request the current package and workspace access to get started.
Request developer accessDefine typed Forge functions, test behavior and review a build. Release and activation remain explicit decisions.
Explore ForgeBuild a scoped provider integration or configure an available connector. Incoming data and external actions have separate permissions.
Explore IntegrationsCreate the project, make a change and inspect its validated output. Connect a workspace when you are ready to publish or call its services.
import { defineCompassProcess } from "@pascal/framework";
export const process = defineCompassProcess({
slug: "incident-response",
name: "Incident response",
states: [
{ value: "open", label: "Open", isInitial: true },
{ value: "resolved", label: "Resolved", isTerminal: true },
],
transitions: [
{ fromStateValue: "open", toStateValue: "resolved", name: "Resolve" },
],
});Create a local resource project with the matching Pascal package set.
Declare Open and Resolved states and their transition.
Run the project checks. A transition to an undeclared state fails validation.
Fix the declaration and build a validated local resource bundle.
Local compilation does not publish a process or execute a business transition. Authenticated API calls and application releases are separate paths.
Request developer accessWork with shipments, approved actions, and published datasets through their product APIs. Keep the workspace and permissions explicit in every request.
Stable identity, typed fields and bounded selections.
Schema, quality, version and lineage.
Allowed transitions and durable execution.
Connected evidence and pinned scenario inputs.
Typed functions and authorized invocation results.
Reusable assignments, relevant context, and supervised Tasks.
Inspect the Task’s files, tests, and working preview. Apply the reviewed change to its project, then follow the build and release.
Product walkthrough · Illustrative example
Read the transcript and visual descriptionsRelease the version you reviewed. Actions that change another system still need current permission and confirmation from that system.
Start with one process, application or integration.