contextReductionCatalog

SUPPORT · constant · Runtime value

Import

TypeScript

import { contextReductionCatalog } from '@jangts/agent-core/support';

JavaScript

import { contextReductionCatalog } from '@jangts/agent-core/support';

Other public entry points:@jangts/agent-core/support, @jangts/agent-core/support/context.

Definition

const contextReductionCatalog: { trim: { validate(step: ContextReduction): void; run: ({ step, fragment }: OperationCall) => Promise<ContextFragment["value"]>; }; compress: { validate(step: ContextReduction, handlers: Set<string>): void; run: (call: OperationCall) => Promise<ContextFragment["value"]>; }; }

Field structure

Field	Type	Required	Description
trim	{ validate(step: ContextReduction): void; run: ({ step, fragment }: OperationCall) => Promise<ContextFragment["value"]>; }	Required	See the type definition and usage context.
compress	{ validate(step: ContextReduction, handlers: Set<string>): void; run: (call: OperationCall) => Promise<ContextFragment["value"]>; }	Required	See the type definition and usage context.

Examples

• Context policy: validate, reduce, and audit: Support provides replaceable policy implementations while Core keeps the final input contract and budget checks.

Explicitly use a validation-only policy

Beginner · Node.js

TypeScript

import { Support } from '@jangts/agent-core';
import type { ContextPolicy } from '@jangts/agent-core/support/context';
const policy: ContextPolicy = { mode: 'validate' };
Support.validateContextPolicy(policy, [], []);
console.log(policy.mode);

JavaScript

import { Support } from '@jangts/agent-core';
const policy = { mode: 'validate' };
Support.validateContextPolicy(policy, [], []);
console.log(policy.mode);

Configure reduction order from real business fragments

Configuration · Node.js

These numbers are explicit choices for the example business, not SDK recommendations for capacities that suit all models.

TypeScript

import { Support } from '@jangts/agent-core';
import type { ContextPolicy } from '@jangts/agent-core/support/context';
const policy: ContextPolicy = { mode: 'reduce', triggerChars: 1800, targetInputChars: 1500,
  selection: { mode: 'sequence' },
  steps: [{ id: 'recent-history', kind: 'trim', fragmentId: 'history', field: 'messages',
    grouping: { kind: 'user-turn' }, keepGroups: 2, targetChars: 1000 }],
};
Support.validateContextPolicy(policy, [], []);
console.log(policy.steps);

JavaScript

import { Support } from '@jangts/agent-core';
const policy = { mode: 'reduce', triggerChars: 1800, targetInputChars: 1500,
    selection: { mode: 'sequence' },
    steps: [{ id: 'recent-history', kind: 'trim', fragmentId: 'history', field: 'messages',
            grouping: { kind: 'user-turn' }, keepGroups: 2, targetChars: 1000 }],
};
Support.validateContextPolicy(policy, [], []);
console.log(policy.steps);

Limit the mutable range for the App's own processing

Extension · Node.js

Auditing also requires the ContextPlan to carry the original fragments; listing IDs alone does not modify or publish material by itself.

TypeScript

import { Support } from '@jangts/agent-core';
import type { ContextPolicy } from '@jangts/agent-core/support/context';
const policy: ContextPolicy = { mode: 'audit', mutableFragmentIds: ['history'] };
Support.validateContextPolicy(policy, [], []);
console.log(policy.mutableFragmentIds);

JavaScript

import { Support } from '@jangts/agent-core';
const policy = { mode: 'audit', mutableFragmentIds: ['history'] };
Support.validateContextPolicy(policy, [], []);
console.log(policy.mutableFragmentIds);

Related policy source

• Real scheduling catalog for policies and reduction operations

Related definitions

• ContextReduction