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 thePATHand withoutJEDEN_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'smodel-catalogalternatives answer:stado capabilities call model-catalog --consumer jeden --jsonwith{}, Brama'sGET /v1/modelsor a statement recorded withstado capabilities attestation record model-catalog. Jeden resolves no address of Brama for it. - Images, speech and web search — the
image_generateandttstools hand their request tostado capabilities call inference --operation images|speech --consumer jeden --json(an OpenAI image request withresponse_formatb64_json; a speech request withinput,voiceandresponse_format, answered as{"content_type", "bytes", "audio_base64"}), andweb_searchhands{"query", "count"}tostado capabilities call search --consumer jeden --json; Jeden names no search vendor, endpoint or key, and reads noTAVILY_API_KEYorBRAVE_SEARCH_API_KEY. WithJEDEN_MODEL_ENDPOINT(or Jeden's token store) the media tools ask that provider's/v1/images/generationsand/v1/audio/speech. Their refusals arejeden.mediaandjeden.web; Stado's own keep theirjeden.alternatives.callcause with acontext: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-cataloganswers. - Weles —
/login,/logout,/refresh,/settings,/billing,/subscriptions list, the status line's quota andjeden doctoruse thebrowser-automationalternative. Served at a directory route, Jeden speaks its HTTP API, withWISENT_PLATFORM_BILLING_TOKENas its bearer when set. When it is thewelesprogram on this host, Jeden runs that program with the verbs its CLI documents:weles login --helpnames the providers and the phrase that authorizes one sign-in;weles accounts list --jsonlists the accounts it resolves from the Skarbiec inventory;/refresh <account>runsweles accounts refresh --provider P --subscription S --jsonand/logout <account>runsweles accounts logout --provider P --subscription S --jsonfor the account the list names;/login's listing,/subscriptions list,/usage's quota rows and the status line readweles accounts billing --jsonandweles 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, startsweles login --provider …, and then reads the run withweles runs showeach time you answer (ready,approvedornot-receivedto a run that waits for you,read-again, orcancel, which runsweles runs cancel), never on a timer, untilweles login --rungives its verdict. The program reports no expiry, so/refreshwithout an account refreshes none. Billing changes (purchase policy, payment setup, purchases, renewals, disabling) have no verb and are refused asjeden.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'stranscriptssource (transcript-lake search <query> --limit <n> --json, andtranscript-lake status --jsonforjeden context sources) run the program thetranscriptsalternative 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 itsjeden.alternativescause. A goal title that fails isjeden.goal.title(lake-unstartable,prompt-unwritten,answer-uncollected,lake-refused,answer-not-json,answer-names-no-goal,prompt-empty), recorded asgoal_lifecycle_refused; the source's failures arejeden.context.transcripts(cancelled,runtime-unavailable,lake-unrun,lake-refused— for exampleduckdb failed to startwhen DuckDB is not on thePATH—,answer-not-json,answer-unexpected, andarchive-emptyfor an archive that holds no partition yet), each the source'sunavailabledetail. BRAMA_URL,WISENT_PLATFORM_BILLING_URL,TRANSCRIPT_LAKE_BINand the settingcontext.advisor.transcriptLakeBinare not read: an address or program named in the environment,~/.jeden/.envor the configuration no longer routes anything, and/setupno 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 inSTADO_BINwhen it is set, elsestadoonPATH, 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 thatPATH. Fix: install Stado, or setSTADO_BINto its program. A Stado that starts but refusesstado --version, which Jeden runs to decide whether its model requests go through Stado, isstado-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; exit69. Fix: read them withstado capabilities <family>, bring one back, or select another order withstado 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 atstado://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 withasks ask|show|answer; its refusals arejeden.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_BINis 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 thePATHJeden runs with, observed: what the system answered and thatPATH. 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 readstado waits.call-unanswered: no alternative of the family answered, observed: Stado's sentence; exit69. Fix: bring one back or record an answer withstado 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 asmodel-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, noresolution.provideror 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/compactwhen 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 codecontext_length_exceededof theprovider_refusalStado hands over in its refusal'sdetails(or one ofdetails.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 withstado 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 examplestado-unavailablewhen Weles cannot run Stado to issue the sign-in's capabilities, orconfirmation-mismatchfor a phrase that is not the oneweles login --helpnames), observed: its exit status and its errors page; Weles's exit2exits2, its69exits69, anything else1. Fix: Weles's own.answer-unreadableandanswer-unexpected: a--jsonverb printed no JSON document, or one without the field Weles documents (a run id, the accounts list, aweles login --providerusage line), observed: what it printed. Fix: update Weles to the release its documentation describes.inventory-unresolved:weles accounts list --jsoncould not resolve the Skarbiec inventory it reads the accounts from, observed: each error Weles names;/loginalone prints it on itsAccount discovery failedline. 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 withstado capabilities select browser-automation --order ….- A sign-in run itself ends as
jeden.auth.sign-in-failedwhenweles login --runanswersok: false, asjeden.auth.sign-in-cancelledaftercancel, and an answer that is none of the offered ones isjeden.auth.answer-unknown(exit2).