Kimi · Product expert

Recommendation Contract

A structured schema for carrying a recommendation, its evidence, constraints, provenance, and uncertainty to a human or governed downstream process.

Layered evidence entering a transparent sealed contract that stops at a human review boundary
Build stateDesigned / schema implemented
Evidence stateRepository-tested
Approved public claimNot ranking or routing

A recommendation should carry its lineage.

The contract defines a stable, inspectable way to express what is being recommended, why, under which constraints, from which evidence, and with what uncertainty.

It does not score routes, rank candidates, choose a winner, dispatch work, or autonomously act. The contract describes and preserves a recommendation; it is not the decision-maker.

What Kimi watches

Whether the evidence, constraints, and version history survive the handoff—and whether later readers can tell what changed.

What exists

A designed schema implemented in the repository and exercised with repository tests.

What it does not do

It does not rank, route, dispatch, authorize, or replace the human or governed process receiving the recommendation.

Ask the continuity expert.

Kimi can explain the contract fields, why lineage travels with the recommendation, and where execution authority begins.

Contact the studio