ALTERX

One system for
everything you run.

Say what you need done, once.
It takes care of the rest, on its own.

Alter Engine

The system that runs the work.

You do not build the workflow. The engine does.

Understand
Reads what you want in normal language.
Plan
Breaks it into a path.
Connect
Hooks the tools the work needs.
Do
Runs the steps and keeps a record.
Check
Looks at the result before it is finished.
Recover
If something fails, it classifies and continues.

Counter Inventory / Live State

Offline sync active
Cardamom Whole Organic 1kg42 units
Kashmiri Chilli Powder Premium115 bags
Sona Masoori Rice Raw 25kg88 bags
CTC Tea Assam Blend 5kg19 units
Cold Pressed Coconut Oil 1L204 bottles

AxInventory

Inventory, counter, and books — in one place.

Built for Indian retail. Not a chatbot.

CatalogueProducts stay in one list.
StockWhat you have, what moved.
POSSell at the counter, even offline, then sync.
PurchasingOrders in, stock up.
TaxGST-native behaviour.
BooksReal double-entry ledger.

Developers

Built so work cannot quietly fail.

v1 is a managed service. This is how execution is held, not a public signup.

Operators describe work in plain language. Engineers can see how it is held.

planning.ts

Planning

import { core } from "@alterx/engine"
const steps = await core.plan(mission, {
context: mission.records,
constraints: mission.rules,
})
// steps: [{ id, action, dependsOn }]

Conceptual, internal execution shown for clarity. Not a public API.

binding.ts

Binding

import { core } from "@alterx/engine"
const bound = await core.bind(plan, {
systems: ["axinventory", "email"],
scope: connector.scope,
})
// bound: { tools, credentials }

Conceptual, internal execution shown for clarity. Not a public API.

execution.ts

Durable execution

import { core } from "@alterx/engine"
const run = await core.execute(bound, {
checkpoint: true,
})
// run.state: "running" | "waiting_approval" | "completed"

Conceptual, internal execution shown for clarity. Not a public API.

verify.ts

Verification

import { core } from "@alterx/engine"
const checked = await core.verify(run.result, {
criteria: mission.criteria,
})
// checked: { matched, verified, consistent }

Conceptual, internal execution shown for clarity. Not a public API.

recover.ts

Recovery

import { core } from "@alterx/engine"
const continued = await core.recover(run.failure, {
classify: true,
})
// continued.state: "recovered" | "blocked"

Conceptual, internal execution shown for clarity. Not a public API.

memory.ts

Memory

import { core } from "@alterx/engine"
const archived = await core.memory(session, {
retain: ["decisions", "evidence"],
})
// archived: { sessionId, timeline }

Conceptual, internal execution shown for clarity. Not a public API.

In the system

000

routes shipped

000

engine capabilities

000

execution layers

Questions

A system that runs work you describe in plain language, instead of a tool you configure.

Alter Engine understands the request, plans it, connects the tools it needs, runs it, checks the result, and recovers if a step fails.

The execution system underneath ALTERX — planning, binding, durable execution, verification, recovery, and memory.

Inventory, counter (POS), purchasing, GST, and books for Indian retail, built on ALTERX.

No. You describe the outcome. The engine plans and runs the steps.

Not in v1. It is a managed service.