The ESP reference.
An overview of the Enterprise Software Path — the factory, the crosscuts, and the runtime — for teams evaluating RSpond. Detailed API documentation ships with design-partner access.
What ESP is
The Enterprise Software Path is the pipeline that turns a working prototype into a deployable, enterprise-grade application. It has three parts:
- The factory — parses your working prototype into a structured spec, then generates a hardened Java / Spring implementation.
- The crosscuts — the twelve enterprise capabilities verified against every generated application.
- The runtime — the Liquid Compute Runtime that carries the application into your target environment.
Start with the How It Works walkthrough, or jump to the prototype quickstart.
The loop, formally
Each pass through the factory runs four stages:
| Stage | Action |
|---|---|
| Parse | The working prototype is read into a structured spec — routes, data, behavior, and intent. |
| Generate | ESP produces a Java / Spring implementation with the crosscuts applied. |
| Verify | The implementation is checked against every crosscut. Failures feed back into the next generation. |
| Emit | A crosscut-complete, deployable application — ready for the target environment. |
The loop repeats until verification is clean. The prototype remains the source of truth throughout.
The twelve capabilities
Every generated application is verified against:
- Security & identity
- Transactions
- Logging & tracing
- Auditing
- Caching
- Error handling
- Monitoring & metrics
- Data validation
- Interoperability
- FinOps & governance
- Configuration
- Regulatory modules
See the Platform overview for what each crosscut means in production.
Liquid Compute Runtime
The runtime is the portable compute layer generated applications run on — designed to carry the same application across cloud, on-premises, edge, and hybrid targets without a per-environment rewrite.
Runtime specifics — deployment targets, resource model, and configuration — are documented as part of the design-partner program.
Where ESP stands
ESP is in early design-partner preview. The architecture is defined, the factory loop and crosscut model are specified, and we’re onboarding the first enterprise teams to run their prototypes through it.
Detailed API references, generator configuration, and runtime deployment guides are delivered with design-partner access — and published here as they stabilize.
Evaluate ESP with your own prototype.
Join the design-partner program to get early access to the factory and the detailed documentation.
Join the Telegram Become a partnerDon’t post proprietary code, credentials, or confidential company information.