Transport & Logistics
Corridors, fleets, passengers and freight that have to keep moving across agencies and jurisdictions — and keep being accounted for when the network drops mid-shift.
In operational use
The platform
One platform. From operations to intelligence.
Operate real systems, preserve evidence, understand what is happening, and govern what changes next.
SigmaCorp is one connected system. Domain products such as TMS-X, Sigma X and Sigma Lens run real operations and remain authoritative for them. Ground preserves evidence of what happened and Atlas structures it into a model of the world. Cortex reasons over authorized evidence to explain, forecast and recommend. Nexus coordinates governed execution back through the products that own each operation. Command Center governs identity, entitlements, policy, approvals and audit across the whole system, and is not part of routine operational flow.
Command CenterGoverns across the system — not inside routine operations.Preview
Operate
Domain products run real operations and remain authoritative for them.
- TMS-XTransport operationsOperational
- Sigma XFleet operationsIn development
- Sigma LensTrade and customsPreview
Preserve evidence
What actually happened is preserved, related and kept accountable.
- GroundEvidence and provenancePreview
- AtlasStructured world modelPreview
Understand
Authorized evidence becomes explanation, forecast and recommendation.
- CortexReasoning and forecastingResearch
Govern what changes next
Authorized intent becomes coordinated action, back through the systems that own it.
- NexusGoverned executionResearch
Product proof
The systems that make it real.
Three of them. One runs operations today, one watches the physical fleet those operations depend on, and one reasons over what both of them record.
Each system states its own stage of maturity.
TMS-X
OperateOperationalEvery journey, from the first seat sold to the shift that closes it.
TMS-X runs intercity passenger and parcel transport across agencies — ticketing, boarding, manifests, courier and end-of-shift reconciliation — and keeps working when the network does not.
- Voyage lifecycle
- Ticketing and seating
- Parcels and courier manifests
- Shift reconciliation
- Offline continuity
Sigma X
ObserveIn developmentWhere every vehicle is, and what it is actually doing.
Sigma X decodes telemetry straight off the tracker — position, ignition, movement, speed, odometer, fuel — and holds it against the trip the vehicle was supposed to be running. Trips can be created automatically from a released TMS-X voyage.
- Codec 8 Extended telemetry
- Trip lifecycle
- Cross-pool vehicle loans
- Fuel-loss detection
- Garage visits
Cortex
UnderstandResearchIt shows its evidence before it shows its answer.
Cortex opens a situation from a deterministic trigger, assembles only the evidence it is authorized to see, forecasts within a stated interval, and recommends. Acting on the recommendation stays with the system that owns the operation.
- Deterministic triggers
- Evidence manifest with provenance
- Forecasting with declared intervals
- Constraint-verified dispatch
- Declared authority ceiling
Operating domains
Where the system meets the world.
The same doctrine — operate, preserve evidence, understand, govern — is not equally weighted everywhere. These are the domains SigmaCorp has chosen to work in, and how far the work has actually got in each.
SigmaCorp works in five operating domains. Transport and logistics is the most developed, with TMS-X in operational use, Sigma X in development and Drive specified. Trade and customs is addressed by Lens and Gate, both in build. Humanitarian and field operations is addressed by Ground and Cortex as architecture. Aviation is a research programme built around Altos, using synthetic disruption scenarios. Infrastructure is the earliest, resting on Ground's evidence layer alone. Each domain is marked with the movements — operate, preserve evidence, understand, govern — that carry the most weight in it.
Trade & Customs
Classification, valuation and compliance work where an error is financial and regulatory at once. The system’s job is to prepare and evidence a position, not to decide it.
Architecture and build in progress
Humanitarian & Field Operations
Dispersed teams working on incomplete information over intermittent links, where what was observed in the field has to survive the trip back and still be attributable.
Architecture and build in progress
Aviation
One aircraft out of service moves crew legality, maintenance and passenger commitments at the same time. The difficulty is not detecting it — it is bounding what to do next.
Research programme
Infrastructure
Physical networks whose condition is only as good as the record of it. Before anything can be reasoned about, observations have to be held with their provenance intact.
Research programme
Each domain is marked with the movements that carry the most weight in it. The full sequence applies everywhere; the emphasis is what differs.
Build systems that strengthen how Africa moves, trades, responds and grows.
We build from African operating realities, strengthen institutional capability and create technology that can serve the wider world.
Built from Africa. Built for the world.
How we hold this
- Observed, inferred, predicted and simulated are kept distinct.
- Access to operational data does not imply the right to train on it.
- Critical systems degrade safely rather than stopping.
- Consequential action stays governed by the system that owns it.
Grounded intelligence
Intelligence that knows what it knows.
Operations that carry consequences cannot treat a measurement, an estimate and a forecast as the same kind of statement. Sigma systems keep them apart, stay honest about what they can no longer see, and leave the authority to act where it already belongs.
Sigma systems classify every observation as observed, derived, inferred, predicted or simulated, and the class is a required field. In the corridor case shown, a measured vehicle speed and a derived corridor transit sit above a line marking where measurement ends; a predicted interval and a recommendation sit below it. A second line, marking authority, sits below the recommendation. Under strain a system reports whether it is live, cached, queued, unavailable or showing synthetic demonstration data, and selected frontline operations continue through connectivity loss without widening what an operator may do. Cortex reaches the recommend step only; preparing and requesting an action require a named requester and a different named approver, after which Nexus coordinates the authorised command and the product that owns the operation performs it.
What is known
Every observation Ground holds declares what kind of statement it is. The class is a required field, so nothing enters the system without saying how it came to be true.
- Observed
- Measured directly by an instrument or recorded by a person.
- Derived
- Computed from observations by a declared transformation.
- Inferred
- Concluded from evidence, and attributable to what it rests on.
- Predicted
- Estimated for a time that has not happened yet.
- Simulated
- Generated to explore a scenario. Never a substitute for the real thing.
- Observed
Vehicle speed on corridor 7
83 km/h
Sigma X · Codec 8 Extended
- Derived
Corridor transit, from completed journeys
11.4 h
TMS-X · completed voyages, corridor 7
Nothing below this line was measured.
- Predicted
Transit estimate for the next window
9.8–13.0 h
Cortex
- Inferred
Release the next corridor window
A1 Recommend
Cortex
Nothing below this line happens without authority.
What happens when it breaks
Resilience is not a promise that nothing fails. It is a promise that a system under strain keeps telling you which of these it is in.
Live
Current, from the authoritative system.
Work continues
Cached
Last known good, with the time it was known.
Work continues
Queued
Work accepted locally, waiting to reconcile.
Work continues
Unavailable
Not known right now, and shown as not known.
Work stops here
Synthetic
Generated for demonstration, and labelled wherever it appears.
Work stops here
Selected frontline operations continue through connectivity loss — and losing the network never widens what an operator is allowed to do.
Who is allowed to act
Reasoning and authority are different things, and the boundary between them is structural. A recommendation is a statement. It becomes an action only when someone with the standing to authorise it says so.
- Operational access
- What a system may read to do the work in front of it.
- Training right
- Whether that same data may be learned from. A separate grant.
Access to data is not a right to train on it. The two are recorded separately, on every observation.
How this is held
- Know what was observed.
- Mark what was inferred.
- State what is uncertain — including when nothing can be stated.
- Degrade without pretending.
- Act only with authority.
In closing
Build systems that understand the world they operate in.
That is the whole argument. A system that cannot say what it observed, cannot keep working when the network goes, or cannot tell you who authorised an action, is not finished — however capable it looks.
The homepage closes by restating its argument: SigmaCorp builds systems that understand the world they operate in. It then separates what exists now — one system in operational use, one in development, and platform layers built far enough to describe — from where the work is headed, which is intent rather than availability, and from the principles that must remain true as it expands. A single action leads to the products. The footer carries site navigation, the company origin line, and a note that public contact channels are not published yet.
Direction
The products differ. The doctrine does not. What follows is where the work stands and where it is structurally headed — kept apart on purpose.
- Now
- One system in real operational use, one in development, and an evidence layer, a reasoning layer and a control plane built far enough to be described honestly.
- Next
- The same four movements applied to domains that already have the operational problem and not yet the system: trade, field operations, aviation, infrastructure.
- What must stay true
- Whatever the platform reaches, a measurement never becomes a forecast, a degraded system never pretends, and reasoning never acquires the authority to act.
Now describes what exists. Next describes intent, not availability.
If you want to see the work rather than read about it, start with the systems themselves.
See the systems