In development

bAIbel TMS is in development. It is not on sale, and nothing here is an offer.

bAIbelTMS
/tms/doors

How work arrives

Work arrives three ways: somebody here uploads it, your client drops it off themselves, or another company's software delivers it. All three land in the same pipeline, are governed by the same rules, and are recorded the same way.

The doors differ in who is standing at them. That is the only thing they differ in.

A project manager uploads it.

The ordinary door. A file goes into a project, is parsed into the working format, and the translated document comes back out of it.

Or your client does, through their own portal.

They sign in, drop off a file, watch it progress, and collect it. They do not need an account in your system, a licence, or a conversation with you first.

The portal depends on two packages.

react and react-dom. Nothing else. It is the one bundle served to people outside your company, and the dependency list is a security decision rather than a convenience — every package in a customer-facing bundle is something you have decided to trust on your client's behalf.

Or an agent delivers it, and the bytes never travel through an AI model.

Another company's software — increasingly, another company's AI agent — can submit work through a door built for exactly that. The document moves between systems. It does not pass through an AI model's context to get there.

One pipeline behind all three.

The same parsing, the same confidentiality decisions, the same budget gate, the same workflow. A document does not get weaker rules because of which door it came through, and nothing downstream has to know.

See it in the applicationHide the screenshot
THREE DOORS A project manager uploads it the ordinary door Your client, through their own portal no account in your system, no licence, no conversation with you first Another company's software, or its agent the document moves between systems It does not pass through an AI model's context to get there. ONE PIPELINE, WHATEVER THE DOOR Parsed into the working format The same confidentiality decisions The same budget gate The same workflow A document does not get weaker rules because of which door it came through. WHO GOT IT BACK Filed where only you can reach it Collected by a person who signed in Taken away by a third party's software Nothing, deliberately a check-only run still writes a record Three kinds of party, kept distinct — because a record that cannot tell them apart answers nothing. AND AT EVERY DOOR The languages come from the file, not from the form. A bilingual file that says English to French is admitted as English to French, whatever the form said — a form and a file that disagree is a mistake somebody would otherwise only find in the delivered document. "We produced nothing" and "we lost your document" are not the same sentence, so only one of them is an absent record.
How work arrives — the three doors converging on one pipeline

And the languages come from the file, not from the form.

A bilingual file that says English to French is admitted as English to French, whatever the form said. A form and a file that disagree is a mistake somebody would otherwise only find in the delivered document.

The record says what kind of party received it back.

Filed where only you can reach it. Collected by a person who signed in. Or taken away by a third party's software — which is a different sentence, because the recipient is a different kind of party and a processing record that could not tell them apart would be unable to answer the one question anybody asks it.

"Nothing, deliberately" is a recorded outcome.

A check-only run's product is its findings, not a file. It still writes a delivery record saying it delivered nothing on purpose — because an absent record cannot be told apart from a run that died, and we produced nothing and we lost your document are not the same sentence.

When something stops, somebody is told — and told again if nobody acts.

A run that halts notifies its owner. If nobody acts, it escalates, and the escalation says why a person who did not ask to hear about it is being told.

A failed notification stays owed.

A channel that cannot deliver says so. It is not caught, logged and forgotten — the difference between delivered and the mail server has been down for a week is the difference between accountability and the appearance of it. A temporary failure is retried; a hopeless one is marked undeliverable and said out loud.

And the notification tells you nothing about the document.

It names the run and says where to look. No reason, no excerpt, no detector's finding — because a failure reason can carry an exception message and a gate reason names what was found inside your client's material, and a mail server is covered by none of the decisions you have made about that material.

The message points at the run. The run tells whoever signs in everything.