Programming languageVersion 7.1

Make the statetell the story.

RedRuff Solve is built for real-time, stateful, rule-driven systems that need to decide what happens next—and explain why.

Enter the language Read the guide

Model state · preserve truth · react to change · select the best valid outcome · explain everything

WHY SOLVE EXISTS

The hard part isn’t writing one function. It’s making everything agree.

Operational software usually stitches together a database, workers, cron, rules, connectors, workflows, queues, traces, and recovery. Solve makes the shared meaning between them native.

Persistent stateEntities + SolveDB

RulesTruth that stays true

External eventsDurable handlers

SchedulesTime-driven work

PlansHuman + system steps

ReasoningAudit-grade traces

ONE MENTAL MODEL

RedRuff Solve

State + truth + change + choice + work + explanation

THE LANGUAGE, AS A JOURNEY

From one entity to a system that can defend every decision.

MODEL THE STATE

Start with what the business remembers.

Entities hold durable business state. Structures shape temporary values. Queries read like the question you meant to ask.

inventory.solve

01entity Product:02    sku: Text03    name: Text04    inventory: Int05    active: Bool = true0607product = create Product:08    sku = "RR-104"09    name = "Edge Router"10    inventory = 12

Persistent state is declared beside its meaning—not hidden behind an ORM.

PRESERVE TRUTH

Invalid state never gets a chance to become history.

Transactions make related changes succeed or fail together. Requirements protect one operation. Rules protect the whole domain.

Order quantity3

118

Inventory12 / 12

Waiting for a transaction

checkout.solve

01transaction:02    require product.inventory >= 303    product.inventory -= 304    save product05    save order

GLOBAL RULEInventory.onHand ≥ 0Invariant protected

REACT TO CHANGE

The outside world can interrupt. The story still continues.

Events cross the system boundary. Reactions express domain consequences. The supervised runtime records, retries, recovers, and traces the work.

OrderReceived

{ id: "ord-849", quantity: 3, region: "south" }

01Recorded
Event stored durably
02Dispatched
Worker accepts the message
03Committed
Order state changes atomically
04Explained
Trace records what happened

Bounded queues · retries with limits · idempotency checks · dead-letter queues · startup recovery

EVENTS

Boundary input, durably handled.

REACTIONS

State changes with consequences.

SCHEDULES

Time-based work that can catch up.

SELECT THE BEST VALID OUTCOME

Requirements remove the impossible. Goals find the best.

A problem filters invalid candidates, scores valid ones, and explains the winner. A decision returns a clear typed answer from evidence.

Lower load 60%Higher rating 40%

Asha75

Load: 2
Rating: 4.9
Capacity: 30kg

Neel85

Load: 1
Rating: 4.6
Capacity: 24kg

Best valid outcome

Mira52

Load: 4
Rating: 5
Capacity: 45kg

Kabir

Load: 0
Rating: 4.8
Capacity: 40kg

Filtered: wrong region

Neel wins with the strongest weighted score after hard requirements remove invalid candidates.

dispatch.solve

01problem AssignDriver(order: Order) -> Driver:02    choose driver from Driver03        where status == "available"0405    require driver.region == order.region06    require driver.capacity >= order.weight0708    minimize driver.currentLoad weight 0.609    maximize driver.rating weight 0.41011    explain

Problems choose.

Decisions answer.

Plans coordinate.

COORDINATE THE WORK

Some steps run in milliseconds. Some wait for a person.

Plans keep both in one durable strategy—with dependencies, missing information, verification, and compensation when later work fails.

Ready to coordinate four durable steps.

1
system
Verify documentsWaiting
2
human
Compliance reviewWaiting
3
system
Activate vendorWaiting
4
system
Verify outcomeWaiting

EXPLAIN EVERYTHING

Every important outcome leaves a reason behind.

Reasoning traces connect inputs, reads, rules, candidate scores, plan steps, connector calls, missing information, and the final result.

trace_7f18a · AssignDriver verified

00:00.003INPUTorder.region = south · weight = 20kg
00:00.009READ4 available Driver records
00:00.012REQUIREKabir rejected · region mismatch
00:00.018SCOREAsha 75.2 · Neel 84.8 · Mira 52.0
00:00.021SELECTNeel · strongest valid weighted score
00:00.024VERIFYresult != none · passed

PRODUCTION, WITHOUT THE PRETEND

Lightweight by evidence. Honest by design.

Validated in the Solve Enterprise 7.1.0 Windows x86-64 release-gate environment. Your workload and hardware will differ.

0153.6M

parser characters / sec

02226K

SolveDB writes / sec

032.78M

SolveDB reads / sec

0420.5ms

startup p95

Production is a behavior

Bounded. Recoverable. Observable.

Bounded queues and backpressure
Retries, idempotency, and dead-letter queues
Database backup, verification, recovery, and rollback
Health, readiness, metrics, and trace verification

release.sh

01solve check02solve test03solve db migrate --preview04solve db backup --out Backups/today05solve serve --profile production06solve health07solve trace verify

START SMALL. GROW INTO PRODUCTION.

Model one entity.
Add one rule.
Let the system explain the rest.

Explore Solve Developer guide

Make the statetell the story.

RedRuff Solve

From one entity to a system that can defend every decision.

Start with what the business remembers.

One domain. Three native views.

Invalid state never gets a chance to become history.

Try to oversell the last 12 units.

The outside world can interrupt. The story still continues.

Watch an order survive the boundary.

Boundary input, durably handled.

State changes with consequences.

Time-based work that can catch up.

Requirements remove the impossible. Goals find the best.

Choose the best valid driver.

Some steps run in milliseconds. Some wait for a person.

Onboard a vendor—even when work crosses people and time.

Every important outcome leaves a reason behind.

Not just what happened. Why.

Lightweight by evidence. Honest by design.

Bounded. Recoverable. Observable.

Model one entity.
Add one rule.
Let the system explain the rest.

Make the statetell the story.

RedRuff Solve

From one entity to a system that can defend every decision.

Start with what the business remembers.

One domain. Three native views.

Invalid state never gets a chance to become history.

Try to oversell the last 12 units.

The outside world can interrupt. The story still continues.

Watch an order survive the boundary.

Boundary input, durably handled.

State changes with consequences.

Time-based work that can catch up.

Requirements remove the impossible. Goals find the best.

Choose the best valid driver.

Some steps run in milliseconds. Some wait for a person.

Onboard a vendor—even when work crosses people and time.

Every important outcome leaves a reason behind.

Not just what happened. Why.

Lightweight by evidence. Honest by design.

Bounded. Recoverable. Observable.

Model one entity.Add one rule.Let the system explain the rest.

Model one entity.
Add one rule.
Let the system explain the rest.