Why Kentaro Exists

Maysano connects business work to data. In many organisations, the weak point is not access to another dataset or model. It is the missing decision context between a business request and the work that follows.

Developer–agent collaboration matters, but developers already work with repositories, tests, reviews, issue trackers, release gates, and monitoring. Those structures do not remove ambiguity, but they give it somewhere to go. The harder relationship is between a business owner and an agent: the person who can name an outcome, recognise a trade-off, and remains accountable for the decision.

Connecting an agent to a system is usually not the difficult part. Defining the relationship is.

A mandate is explicit authority to act toward an outcome. It holds the business outcome, decision context, scope, authority limits, approval rights, evidence expected, route for challenge, and escalation path. It says enough about the work relationship for both person and agent to know where they stand.

A mandate is not a task brief. A task brief says what to do; it may still leave the purpose, decision owner, and acceptable trade-offs unstated. Nor is a mandate a legal contract. It does not transfer human accountability to an agent.

A task brief says what to do.A mandate says why it matters, what authority exists, what remains human, and how the result will be judged.

Without this object, teams tend toward two failure modes. They over-constrain an agent until it can do little more than replay a checklist, or they grant broad access without clear ownership and ask people to repair the consequences later.

Aviation’s Crew Resource Management offers a practical lesson. As automation changes the work, human contribution shifts toward intent, judgement, trade-offs, exceptions, decisions, and accountability. That does not make people incidental. It makes coordination more important.

Human review at the end of an opaque process is not meaningful oversight. Algorithmic management provides the negative example: hidden authority, silent priority changes, and unexplained decisions leave people with the responsibility for an outcome without a credible way to shape it.

A human–agent work contract should make authority clearer, not less clear. It should help a person see what changed, challenge an output, correct context, and decide when an exception needs human judgement.

Helmreich, Merritt and Wilhelm on Crew Resource ManagementJarrahi et al. on algorithmic management at work

Maysano connects objectives, decision context, use cases, data products, delivery work, and outcome evidence. It does not replace data platforms, catalogues, engineering tools, or human decision-makers.

For Kentaro, that means understanding an objective, a use case, the relevant data products, the in-scope decision, and the evidence by which value will be assessed. Kentaro is not another coding agent with a different interface.

Kentaro Harness keeps its established technical meaning: context, tools, permissions, execution, and feedback. The wider focus is Business-Agent Work Design: the operating relationship that lets those technical elements serve accountable work.

Kentaro Harness aims to reduce friction in practical work. It needs secure access to the right tools, data, and platform functions. It also needs an explicit working relationship: the objective, permitted information, boundaries, approvals, and accountable owner.

The goal is not to make Kentaro appear independent. The goal is clearer, safer, more useful collaboration between business people and agents. Kentaro Harness is open source under the MIT licence.

This is exploration and early work, not a claim that a final operating model already exists. The stories, Harness, and the ideas on this page are a way to learn in public about a problem that will matter well beyond one product.