Uses of Package
ai.redouble.demo

Packages that use ai.redouble.demo
  • Class
    Description
    The agent's capabilities for the page: the tools in its palette and the skills it may draw on.
    What a benchmark produced: the reference run's answer and the report the runtime also logged as a table.
    One catalog entry on the status panel: its id, grade and provider, which client family it belongs to (an LLM, an embeddings model or a decision model), whether it takes a seat, whether the compliance envelope permits it, its status, what it accepts beyond text (images, documents), its output modalities, its per-million prices in the entry's currency, the bound it declares: a quota window (tpm) or, for a decision model served from the deployment's own machine, how many requests its server takes at once (maxConcurrent), whether its grade and prices are the discovery's inference no person has confirmed (unverified), and its note, the discovery's own words on where it came from.
    What connecting did: the provider that verified the credential with its listed count, or its failure in the provider's own words, or a note when nothing on the credential can list; and the fresh status the page re-renders from.
    The credential records a person provides for the session in one request.
    One credential a provider reads, as it declared it: the record id and its parts.
    What the demo agent returns: the answer, and which skills it admitted on the way, so the caller can see the skill door being used.
    Which model catalog this process runs on, and what to do when it is not this account's.
    What the page and the startup log say about the catalog: the file the demo keeps it in (catalogFile, null when the process runs outside its module), where it was read from (null when nowhere, and the runtime is on the shipped defaults), the file the page's edits land in (null when the catalog in use is not a file of the deployment's own: the shipped defaults, or a copy packaged on the classpath), how many entries it has, each grade's order (its entries in the deployment's order of preference, the first the grade's default), the single pins (the embeddings and the decision entry), and the steps a person takes when something is missing.
    Locates the shipped demo corpus, the folder the extract and decide runs read and the page shows, wherever and on whatever OS the process runs.
    The demo agent's input: the runtime's thinker input (a query and a depth) with nothing added.
    What the discovery did: its report, the file written, the entry count, the providers this run actually queried with each one's outcome, the entries the discovery's classifier wrote (classifiedBy names the model whose judgment they are; each carries a verify note), the classified entries whose own ping refused them, the new entries left out because the model refuses the zero-retention mode the account runs at (nonZdr), the listed models no provider key has a client for (unserved), and the status the page re-renders from.
    An edit to one catalog entry from the page: the entry's id, and any of a new grade, a new status, a new input or output price per million in the entry's currency, or a confirmation that the entry's inferred facts were checked; null leaves a field as it is.
    A grade's order from the page: the grade and its entries in the order of preference, the first the grade's default; an empty list clears the order.
    One part of a credential: which part (user, secret, host), the environment variable it reads from, and what it means.
    A single pin from the page: the slot (embeddings or decision) and the entry id; null clears the slot.
    One queried provider's outcome, readable at a glance: LISTED with a count, LISTING_FAILED with the reason, LISTING_UNSUPPORTED (pinged blind).
    One provider on the status panel: its key, whether it is configured, whether a session credential holds it, the human description of its credential, the credentials it declares, and its connection facts.
    The quick question's answer as the page shows it: the answer and the model's reasoning, the catalog entry that answered and the model that served it, and what the call cost, priced from the catalog like every other result on the page.
    The calls of one job, delivered by its completion event; see QuickAnswer.capture(JobDispatcher, QuickLLMQuestionTool).
    The whole status panel in one shape: whether the dispatcher runs, the providers, the catalog summary, the catalog entries, per grade the entry the runtime serves each kind of request with now (text, images, documents) and, where it serves none, its refusal in its own words, the shipped corpus path the page prefills, and the day the corpus's price story is answered for, which the pricing steps open on.
    One credential record a person provides for the session: the runtime's record id and its parts.
    A host's store of credentials a person pastes into the page, held for the process only.
    One skill on the page: its name, description, origin, bundle id and the tools it suggests.
  • Class
    Description
    The agent's capabilities for the page: the tools in its palette and the skills it may draw on.
    The agent's query and, when the caller names one, the rung it runs at; null runs it at the agent's declared grade.
    A benchmark request: the query every raced model answers, and how many times each answers it.
    The demo's write-side catalog logic, shared by every host: connecting a credential for the session, running the discovery that writes the deployment's catalog, and editing or pinning one of its entries.
    What connecting did: the provider that verified the credential with its listed count, or its failure in the provider's own words, or a note when nothing on the credential can list; and the fresh status the page re-renders from.
    The credential records a person provides for the session in one request.
    Which model catalog this process runs on, and what to do when it is not this account's.
    Locates the shipped demo corpus, the folder the extract and decide runs read and the page shows, wherever and on whatever OS the process runs.
    What the discovery did: its report, the file written, the entry count, the providers this run actually queried with each one's outcome, the entries the discovery's classifier wrote (classifiedBy names the model whose judgment they are; each carries a verify note), the classified entries whose own ping refused them, the new entries left out because the model refuses the zero-retention mode the account runs at (nonZdr), the listed models no provider key has a client for (unserved), and the status the page re-renders from.
    An edit to one catalog entry from the page: the entry's id, and any of a new grade, a new status, a new input or output price per million in the entry's currency, or a confirmation that the entry's inferred facts were checked; null leaves a field as it is.
    A grade's order from the page: the grade and its entries in the order of preference, the first the grade's default; an empty list clears the order.
    A single pin from the page: the slot (embeddings or decision) and the entry id; null clears the slot.
    The quick question's answer as the page shows it: the answer and the model's reasoning, the catalog entry that answered and the model that served it, and what the call cost, priced from the catalog like every other result on the page.
    The whole status panel in one shape: whether the dispatcher runs, the providers, the catalog summary, the catalog entries, per grade the entry the runtime serves each kind of request with now (text, images, documents) and, where it serves none, its refusal in its own words, the shipped corpus path the page prefills, and the day the corpus's price story is answered for, which the pricing steps open on.
    A host's store of credentials a person pastes into the page, held for the process only.
    One skill on the page: its name, description, origin, bundle id and the tools it suggests.
  • Class
    Description
    The agent's capabilities for the page: the tools in its palette and the skills it may draw on.
    The agent's query and, when the caller names one, the rung it runs at; null runs it at the agent's declared grade.
    A benchmark request: the query every raced model answers, and how many times each answers it.
    The demo's write-side catalog logic, shared by every host: connecting a credential for the session, running the discovery that writes the deployment's catalog, and editing or pinning one of its entries.
    What connecting did: the provider that verified the credential with its listed count, or its failure in the provider's own words, or a note when nothing on the credential can list; and the fresh status the page re-renders from.
    The credential records a person provides for the session in one request.
    Which model catalog this process runs on, and what to do when it is not this account's.
    Locates the shipped demo corpus, the folder the extract and decide runs read and the page shows, wherever and on whatever OS the process runs.
    What the discovery did: its report, the file written, the entry count, the providers this run actually queried with each one's outcome, the entries the discovery's classifier wrote (classifiedBy names the model whose judgment they are; each carries a verify note), the classified entries whose own ping refused them, the new entries left out because the model refuses the zero-retention mode the account runs at (nonZdr), the listed models no provider key has a client for (unserved), and the status the page re-renders from.
    An edit to one catalog entry from the page: the entry's id, and any of a new grade, a new status, a new input or output price per million in the entry's currency, or a confirmation that the entry's inferred facts were checked; null leaves a field as it is.
    A grade's order from the page: the grade and its entries in the order of preference, the first the grade's default; an empty list clears the order.
    A single pin from the page: the slot (embeddings or decision) and the entry id; null clears the slot.
    The quick question's answer as the page shows it: the answer and the model's reasoning, the catalog entry that answered and the model that served it, and what the call cost, priced from the catalog like every other result on the page.
    The whole status panel in one shape: whether the dispatcher runs, the providers, the catalog summary, the catalog entries, per grade the entry the runtime serves each kind of request with now (text, images, documents) and, where it serves none, its refusal in its own words, the shipped corpus path the page prefills, and the day the corpus's price story is answered for, which the pricing steps open on.
    A host's store of credentials a person pastes into the page, held for the process only.
    One skill on the page: its name, description, origin, bundle id and the tools it suggests.