Jeden/Docs

Other products

Jeden asks Stado, never an address.

Jeden keeps no address of another product. Model requests are handed to stado capabilities call inference --consumer jeden; every other need is served by the alternative stado capabilities resolve FAMILY --consumer jeden names in Stado's selected order.

Which family serves what#

  • Model requests — each chat request is handed whole to stado capabilities call inference --consumer jeden --json, which asks the first inference alternative that answers it (Brama, or a statement recorded for that exact request). Without Stado on the PATH and without JEDEN_MODEL_ENDPOINT, a provider in Jeden's token store stands in, named on standard error; Jeden runs no other product's program for it.
  • The model catalog — /model, /model --all, the model picker and a call's price read the catalog Stado's model-catalog alternatives answer: stado capabilities call model-catalog --consumer jeden --json with {}, Brama's GET /v1/models or a statement recorded with stado capabilities attestation record model-catalog. Jeden resolves no address of Brama for it.
  • Images, speech and web search — the image_generate and tts tools hand their request to stado capabilities call inference --operation images|speech --consumer jeden --json (an OpenAI image request with response_format b64_json; a speech request with input, voice and response_format, answered as {"content_type", "bytes", "audio_base64"}), and web_search hands {"query", "count"} to stado capabilities call search --consumer jeden --json; Jeden names no search vendor, endpoint or key, and reads no TAVILY_API_KEY or BRAVE_SEARCH_API_KEY. With JEDEN_MODEL_ENDPOINT (or Jeden's token store) the media tools ask that provider's /v1/images/generations and /v1/audio/speech. Their refusals are jeden.media and jeden.web; Stado's own keep their jeden.alternatives.call cause with a context: line naming the tool, the model and what was asked.
  • Brama's own API — Jeden reaches no part of Brama's own API and resolves no address of Brama, so a session starts without asking Stado anything and takes no lease of an account. Budget pricing and the lifecycle model's output ceiling read the catalog model-catalog answers.
  • Weles — /login, /logout, /refresh, /settings, /billing, /subscriptions list, the status line's quota and jeden doctor use the browser-automation alternative. Served at a directory route, Jeden speaks its HTTP API, with WISENT_PLATFORM_BILLING_TOKEN as its bearer when set. When it is the weles program on this host, Jeden runs that program with the verbs its CLI documents: weles login --help names the providers and the phrase that authorizes one sign-in; weles accounts list --json lists the accounts it resolves from the Skarbiec inventory; /refresh <account> runs weles accounts refresh --provider P --subscription S --json and /logout <account> runs weles accounts logout --provider P --subscription S --json for the account the list names; /login's listing, /subscriptions list, /usage's quota rows and the status line read weles accounts billing --json and weles accounts quota --json, each subscription's plan, status, cost and quota as the provider's own page showed them (a value Weles read none of is shown as not observed, never as unlimited). /login <provider> asks you for the phrase, the Stado host whose browser runs the sign-in and the minutes its one-use capabilities may live, starts weles login --provider …, and then reads the run with weles runs show each time you answer (ready, approved or not-received to a run that waits for you, read-again, or cancel, which runs weles runs cancel), never on a timer, until weles login --run gives its verdict. The program reports no expiry, so /refresh without an account refreshes none. Billing changes (purchase policy, payment setup, purchases, renewals, disabling) have no verb and are refused as jeden.weles.verb-absent. /usage's own counts read Jeden's usage file and need no Weles.
  • Transcript Lake — goal titles (transcript-lake goal title --stdin --json), jeden pursue's preference evidence (transcript-lake search <query> --json) and the advisor's transcripts source (transcript-lake search <query> --limit <n> --json, and transcript-lake status --json for jeden context sources) run the program the transcripts alternative names. When this host offers none (no Stado, or none answering) a goal is titled by the prompt's first line, a pursuit reads no lake evidence, and the source is unavailable with its jeden.alternatives cause. A goal title that fails is jeden.goal.title (lake-unstartable, prompt-unwritten, answer-uncollected, lake-refused, answer-not-json, answer-names-no-goal, prompt-empty), recorded as goal_lifecycle_refused; the source's failures are jeden.context.transcripts (cancelled, runtime-unavailable, lake-unrun, lake-refused — for example duckdb failed to start when DuckDB is not on the PATH —, answer-not-json, answer-unexpected, and archive-empty for an archive that holds no partition yet), each the source's unavailable detail.
  • BRAMA_URL, WISENT_PLATFORM_BILLING_URL, TRANSCRIPT_LAKE_BIN and the setting context.advisor.transcriptLakeBin are not read: an address or program named in the environment, ~/.jeden/.env or the configuration no longer routes anything, and /setup no longer offers to store one.

How naming an alternative fails#

Each refusal prints what failed, why, what was observed, then fix: … and cause: jeden.alternatives.<cause>; jeden errors show jeden.alternatives prints every cause with its test, which tests/alternatives/resolve.mjs provokes through the real Stado in an isolated home. A command that met the refusal while doing its own step adds a context: line naming the step (for /login: listing the providers Weles signs in to) and keeps the refusal's exit status. No alternative answering exits 69, since the same command can succeed once one answers; every other refusal exits 1.

  • stado-unstartable: the Stado CLI could not be started. Jeden finds it the way Stado states a consumer finds it: the path in STADO_BIN when it is set, else stado on PATH, else ${STADO_BIN_DIR:-$HOME/.stado/bin}/stado, where its installer places it; the refusal names the program it ran and which of the three found it, observed: what the system answered and that PATH. Fix: install Stado, or set STADO_BIN to its program. A Stado that starts but refuses stado --version, which Jeden runs to decide whether its model requests go through Stado, is stado-refused, with its status and what it printed.
  • none-answers: no <family> alternative in Stado's selected order answers jeden now, observed: Stado's own sentence naming each alternative and its cause; exit 69. Fix: read them with stado capabilities <family>, bring one back, or select another order with stado capabilities select <family> --order ….
  • stado-refused: Stado refused the question itself (an older Stado that does not know the family or the consumer), observed: its status and sentence. Fix: update Stado with the stado release installer at stado://releases/stado/<version>/<platform>/install.sh.
  • answer-unreadable: what Stado printed is not JSON, observed: the decoder's words, its exit status, what it printed and its standard error. answer-incomplete: the answer is JSON but lacks a field (provider, kind or route; a failure document's message or error_code), named in the sentence, observed: the same. Fix for both: update Stado.
  • kind-unspoken: the alternative is of a kind the need cannot reach (a browser-automation alternative that is neither a directory route nor a program), observed: provider, kind and route. Fix: select first one Jeden reaches that way.
  • not-a-program: a transcripts alternative that is not a program on this host, observed: provider, kind and route. Fix: select one that is a program first.
  • The operator-asks family (stado capabilities resolve operator-asks --consumer jeden) names the program that puts a waiting ask to the operator, Oko on Wisent's hosts, run with asks ask|show|answer; its refusals are jeden.completion.asks.oko's, and a host that names no such alternative keeps the ask in Jeden's register only, with that refusal on the ask. JEDEN_OKO_BIN is no longer read.

How a called family fails#

Handing a request to stado capabilities call FAMILY --consumer jeden --json is jeden.alternatives.call (tests/alternatives/call.mjs, through /model --all and jeden run --model-only). Each refusal is the turn's refusal, Stado's own sentence observed.

  • call-unstartable: the Stado CLI could not be started from the PATH Jeden runs with, observed: what the system answered and that PATH. Fix: install Stado. call-unhanded: Stado started but the request could not be written to its standard input, observed: the write's error, the request's size in bytes and how the process then ended. call-uncollected: how Stado ended could not be read, observed: the error. Fix: run the command named and read stado waits.
  • call-unanswered: no alternative of the family answered, observed: Stado's sentence; exit 69. Fix: bring one back or record an answer with stado capabilities attestation record.
  • call-refused: Stado refused the request itself, observed: its error code, exit status and sentence (an order in Stado's configuration naming an alternative the family does not have, or a family an older Stado does not offer, such as model-catalog). Fix: Stado's own, then update Stado.
  • call-unreadable: what Stado printed is not JSON, observed: the decoder's words, exit status, output and standard error. call-answerless: Stado ended successfully but its document names no answer (for the catalog, no resolution.provider or answer object; for doctor, no inference order). Fix: update Stado.
  • A model request that Stado refuses or that no alternative answers carries a context: line naming the model and the session it was asked for (asking model `<route>` for session <id> through `stado capabilities call inference --consumer jeden --json`); the image, speech and search tools name the tool, the model and what was asked the same way. The refusal keeps its exit status.
  • catalog-unreadable: the catalog the alternative answered is not one Jeden reads (Brama's catalog is checked as strictly as Brama's own read), observed: the answer. Fix: repair what serves it, or select another first.
  • request-refused: the alternative (Brama) refused the request itself with an HTTP status, the refusal every alternative would give, observed: its answer. Fix: choose a model it serves with /model, or /compact when it names the context length.
  • context-overflowed: a provider one of Stado's inference alternatives reached refused the request as longer than the model's context, read from the code context_length_exceeded of the provider_refusal Stado hands over in its refusal's details (or one of details.unreachable[]), never from its words; observed: the provider, its HTTP status and message, and Stado's sentence. The turn promotes to a route with a longer context as it does for a direct provider's overflow. Fix: /compact, or a model with a longer context.

How running the Weles program fails#

When the browser-automation alternative is the weles program, its refusals are causes of jeden.weles; jeden errors show jeden.weles prints them with their tests, which tests/auth/login.mjs provokes through the real Stado and Weles in an isolated home. A refusal Weles declares itself (its JSON answer names a cause, a message and a fix) keeps Weles's words and fix and the meaning of its exit status. jeden doctor's weles probe reports the program's route as its endpoint and counts the providers weles login --help names.

  • program-unstartable: the program at the route Stado named could not be started, observed: what the system answered. Fix: prove it again with stado capabilities resolve browser-automation --consumer jeden --failed weles, and repair or reinstall Weles there.
  • refused, refused-usage, refused-retryable: Weles refused the command with its own cause (for example stado-unavailable when Weles cannot run Stado to issue the sign-in's capabilities, or confirmation-mismatch for a phrase that is not the one weles login --help names), observed: its exit status and its errors page; Weles's exit 2 exits 2, its 69 exits 69, anything else 1. Fix: Weles's own.
  • answer-unreadable and answer-unexpected: a --json verb printed no JSON document, or one without the field Weles documents (a run id, the accounts list, a weles login --provider usage line), observed: what it printed. Fix: update Weles to the release its documentation describes.
  • inventory-unresolved: weles accounts list --json could not resolve the Skarbiec inventory it reads the accounts from, observed: each error Weles names; /login alone prints it on its Account discovery failed line. Fix: correct what Weles names.
  • verb-absent: the program documents no verb for changing billing (purchase policy, payment setup, purchases, renewals, disabling a subscription) or a subscription's structured status. Fix: select first a browser-automation alternative served at a directory route with stado capabilities select browser-automation --order ….
  • A sign-in run itself ends as jeden.auth.sign-in-failed when weles login --run answers ok: false, as jeden.auth.sign-in-cancelled after cancel, and an answer that is none of the offered ones is jeden.auth.answer-unknown (exit 2).