The path taken

Senda is the Spanish word for a path, the narrow kind that exists because people walked it. It appears where the steps went, and it stays because the next person can see it and follow it.

Our mark is drawn from that. One root, one trunk, and five routes opening from the same point. Four are ways the work could have gone. One runs straight to the gate, and that one is drawn in colour. Every screen we make keeps the same rule: the route an agent took is the one you see lit.

We build for a world where agents do most of the work. A request arrives, a document needs reading, a queue needs watching. Today a person does each of those, or nobody does and the request waits for morning. An agent can do them at any hour. We want that in every company, and in the processes people deal with outside work.

In that world agents are the actors and people are the orchestrators. The orchestrator writes the rules, decides where an agent may go, answers when it asks and holds the switch. Senda is built for that person.

The Corpus holds what a company wrote down, its documents and the way it decides, and answers with the quote or the rule it used. When the documents do not say, it says so. Line is where an agent is written, tested, launched and stopped, and it asks a person before a step it was not cleared to take. Semant keeps every run, step by step, apart from the product that ran it.

We think speed is good. Work that waits costs someone: the customer who gave up at midnight, the team that spends its morning on the night's backlog. The answer to the risk of going faster is better instruments: rules that are written, runs that are kept, an owner who can stop it. Slowing down leaves the backlog where it was.

When an agent answers a customer, someone should be able to open that answer the next day and see which document it came from, which rule applied and which person said yes. That is what lets a company hand more work to agents without handing over its judgment.