S++Business systems language
A language in development

Business behavior,
made explicit.

S++ describes who participates in a business operation, what must be checked, what changes, and where consistency matters. The implementation can adapt without losing the business story.

Explore a real example Read the language model
01 / MODEL02 / COMPOSE03 / DEPLOY
One business definition.
Many physical choices.
SPPBUSINESS
Roles · Scenes · ServicesDescribe the operation and its consistency boundary.
APPAPPLICATION
Bindings · Deployment · PolicyChoose where services run and how they connect.
PHYPHYSICAL
Storage · Numbers · ResourcesProvide the representation and runtime guarantees.
S++ / 001
THE PROBLEM 01

Business meaning gets buried
in implementation.

In a conventional system, a single business operation may be scattered across models, controllers, validation, persistence, and transaction code. S++ brings the participants and the operation back into view.

THE LANGUAGE 02
01

Model the role, not just the object.

A person can act as a buyer or a merchant. A product can become goods, then an order line. Each role makes its own business facts visible.

02

Make every scenario accountable.

A scene declares its participants and calls checks, calculations, and updates in business order. Transaction boundaries are visible in the source.

03

Keep deployment decisions movable.

The application and physical layers choose service routing, storage, numeric representation, and transaction implementation.

IN THE SOURCE 03

The business operation
is readable at a glance.

Here is an excerpt from the Petstore payment scene. The participants, eligibility checks, bounded funds transfer, and record updates are all part of one explicit flow.

Follow the Petstore flow
petshop-scene-payShopOrder.sppSPP
Scenario serial payShopOrder(
    Buyer, Merchant, ShopOrder, PaymentAgreement
) {
    checkBuyerCredential;
    checkPaymentEligibility;
    preparePayment;

    transaction {
        payOrderFunds bounds {
            Buyer.wallet: [0, null];
            Merchant.cash: [0, null];
        };
        updateShopOrder;
        insertReceipt(PaymentAgreement.receipt);
    }
}

Illustrative excerpt; omitted preparation and lookup steps are present in the demo source.

FROM IDEA TO EXECUTION 04

Two domains of proof.
One language model.

The project is being tested against both a complete commerce journey and selected banking deposit transactions. Each example exposes different modeling and consistency questions.

01 / PETSTORE

A complete customer journey

Browse, cart, order, payment, fulfillment, cancellation, returns, and reservation.

MULTIPLE DOMAINS · BUSINESS SCENES02 / DEPOSIT SYSTEM

Consistency under pressure

Account opening, cash deposit, repayment allocation, recorded postings, reversal, and failure handling.

TRANSACTIONS · QUANTUM FACTS
WHERE WE ARE 05

Built to be tested.
Still being defined.

S++ is an active language project. Its demos execute through generated Java services, and the team tracks limits alongside working behavior. We are looking for teams willing to evaluate the model on real business workflows.

Read the current boundaries
Implemented today
  • Role and entity modeling
  • Atomic services and explicit scenes
  • APP / PHY deployment definitions
  • Generated Java service execution
  • Petstore and deposit demonstrations
Specific recovery and production integration behaviors are still evolving.
WORK WITH US

Have a complex business
flow worth testing?

We are preparing guided evaluations of S++ with engineering teams and early partners.

See the scenarios Contact details will be published here.