Model transport and stage projection

Generate a sealed catalog and stage projections from tool definitions; native functions and JSON adapters share the same tool contract.

createTextTransport explicitly creates an ordinary text transport; createModelTransport uses nativeFunctionInteraction by default. When the JSON protocol is needed, pass jsonObjectInteraction explicitly; Core does not guess a fallback from model names, URLs, or failure counts.

createStageModelTransport uses stages[{id,toolIds}] to constrain each model stage. Static sources are verified at assembly time, and dynamic source factories take a snapshot at this prepare time; a prepared call has a fixed resolver and receivers. Unknown stages are rejected before any dynamic source is called; tools outside the stage cannot bypass the constraint at runtime.

modelInteractionCatalog provides a read-only catalog under the two real adapter IDs native-functions and json-object. An App can choose catalog entries according to explicit model tool configuration, without automatically guessing from model names, URLs, or failure counts. Using an adapter directly and referring to it by catalog ID follow the same ModelInteractionAdapter contract.

requireStrictArguments requests the strict argument capability declared by the adapter and rejects assembly when it is unsupported. It does not guarantee that the provider responds correctly, and the final collector and Schema still need to validate.

createSessionModelTransport allows one response to contain prose and several tool calls while reusing the same call collector; it only exposes resolved results and never executes tools. prepareSessionFunctions prepares tool declarations per stage, keeping unknown tools and invalid arguments as problem markers for the App to validate before real dispatch.

Progressive examples for the same business case

Create a named text transport

Beginner · Node.js

TypeScript

import { ModelRunner, Support } from '@jangts/agent-core';
const text = Support.createTextTransport({ id: 'brief', options: { temperature: 0.2 } });
const runner = new ModelRunner({ provider: { async *stream() { yield '服务正常'; } }, transports: [text] });
console.log((await runner.invoke({ input: '简答服务状态', transport: text })).value);

JavaScript

import { ModelRunner, Support } from '@jangts/agent-core';
const text = Support.createTextTransport({ id: 'brief', options: { temperature: 0.2 } });
const runner = new ModelRunner({ provider: { async *stream() { yield '服务正常'; } }, transports: [text] });
console.log((await runner.invoke({ input: '简答服务状态', transport: text })).value);

Generate transports for two stages from same-source tools

Configuration · Node.js

TypeScript

import { Support } from '@jangts/agent-core';
const inputSchema = Support.defineSchema({
  jsonSchema: { type: 'object', properties: {}, additionalProperties: false },
  parse(value: unknown) {
    if (!value || typeof value !== 'object' || Array.isArray(value) || Object.keys(value).length) throw new TypeError('需要空对象');
    return {};
  },
});
const tools = Support.defineModelTools([
  { id: 'greet', description: '问候', inputSchema, resolve: () => 'greet' },
  { id: 'status', description: '状态查询', inputSchema, resolve: () => 'status' },
]);
const transport = Support.createStageModelTransport({ id: 'intent', tools,
  stages: [{ id: 'recognize', toolIds: ['greet', 'status'] }, { id: 'status-only', toolIds: ['status'] }],
});
console.log(transport.prepare('status-only').schemaChars);

JavaScript

import { Support } from '@jangts/agent-core';
const inputSchema = Support.defineSchema({
    jsonSchema: { type: 'object', properties: {}, additionalProperties: false },
    parse(value) {
        if (!value || typeof value !== 'object' || Array.isArray(value) || Object.keys(value).length)
            throw new TypeError('需要空对象');
        return {};
    },
});
const tools = Support.defineModelTools([
    { id: 'greet', description: '问候', inputSchema, resolve: () => 'greet' },
    { id: 'status', description: '状态查询', inputSchema, resolve: () => 'status' },
]);
const transport = Support.createStageModelTransport({ id: 'intent', tools,
    stages: [{ id: 'recognize', toolIds: ['greet', 'status'] }, { id: 'status-only', toolIds: ['status'] }],
});
console.log(transport.prepare('status-only').schemaChars);

Keep the tools and replace only the explicit interaction adapter

Extension · Node.js

Model calls still use invoke({input,transport}) and return ModelResult; switching interaction does not redesign business results.

TypeScript

import { Support } from '@jangts/agent-core';
const inputSchema = Support.defineSchema({
  jsonSchema: { type: 'object', properties: {}, additionalProperties: false },
  parse(value: unknown) {
    if (!value || typeof value !== 'object' || Array.isArray(value) || Object.keys(value).length) throw new TypeError('需要空对象');
    return {};
  },
});
const tools = Support.defineModelTools([
  { id: 'status', description: '查询服务状态', inputSchema, resolve: () => 'status' },
]);
const native = Support.createModelTransport({ id: 'native', tools });
const adapterId: keyof typeof Support.modelInteractionCatalog = 'json-object';
const json = Support.createModelTransport({ id: 'json', tools, adapter: Support.modelInteractionCatalog[adapterId] });
console.log(native.id, json.id);

JavaScript

import { Support } from '@jangts/agent-core';
const inputSchema = Support.defineSchema({
    jsonSchema: { type: 'object', properties: {}, additionalProperties: false },
    parse(value) {
        if (!value || typeof value !== 'object' || Array.isArray(value) || Object.keys(value).length)
            throw new TypeError('需要空对象');
        return {};
    },
});
const tools = Support.defineModelTools([
    { id: 'status', description: '查询服务状态', inputSchema, resolve: () => 'status' },
]);
const native = Support.createModelTransport({ id: 'native', tools });
const adapterId = 'json-object';
const json = Support.createModelTransport({ id: 'json', tools, adapter: Support.modelInteractionCatalog[adapterId] });
console.log(native.id, json.id);

Policies & implementations

• Stage list validation and dynamic source snapshots
• Explicit model interaction adapter catalog
• Session transport for prose and multiple tool calls