@agentick/core 0.0.1

package/dist/state/boundary.d.ts

@@ -0,0 +1,347 @@
+/**
+ * Boundary System for Tentickle
+ *
+ * Boundaries extend Context with collection-phase effects. They provide a generic
+ * mechanism for components that affect how their children are processed during
+ * compilation, without hardcoding specific component checks in the compiler.
+ *
+ * The abstraction ladder:
+ * - createContext: render-phase values, read via useContext
+ * - createBoundary: render-phase values + collection-phase effects
+ * - createFormatter: convenience for formatter boundaries (collection-time)
+ * - createPolicy: convenience for policy boundaries (format-time, auto-accumulating)
+ *
+ * @example Formatter boundary (like XML, Markdown)
+ * ```tsx
+ * // XML/Markdown use the unified FormatterBoundary
+ * <XML>
+ *   <Content />
+ * </XML>
+ *
+ * // To get the current formatter during render:
+ * const formatter = useBoundary(FormatterBoundary);
+ * if (formatter) {
+ *   const formatted = formatter.formatter(blocks);
+ * }
+ * ```
+ *
+ * @example Policy boundary (like TokenBudget)
+ * ```tsx
+ * // Policies auto-accumulate - nested policies are combined
+ * <TokenBudget maxTokens={8000} strategy="drop-oldest">
+ *   <Timeline />
+ *   <TokenBudget maxTokens={2000} strategy="truncate">
+ *     <User>{message}</User>  {/* Both policies apply \*\/}
+ *   </TokenBudget>
+ * </TokenBudget>
+ *
+ * // To get all active policies during render:
+ * const policyValue = useBoundary(PolicyBoundary);
+ * if (policyValue) {
+ *   console.log('Active policies:', policyValue.policies.map(p => p.name));
+ * }
+ * ```
+ *
+ * @module tentickle/boundary
+ */
+import type { JSX } from "../jsx/jsx-runtime";
+import { type Context } from "./context";
+import type { Formatter } from "../renderers";
+import type { COMTimelineEntry } from "../com/types";
+/**
+ * Symbol used to mark boundary provider components.
+ * The fiber compiler detects this to handle boundary effects.
+ */
+export declare const BOUNDARY_PROVIDER_SYMBOL: unique symbol;
+/**
+ * Boundary class determines how the compiler handles the boundary.
+ * - 'formatter': Affects content rendering during collection (e.g., XML, Markdown)
+ * - 'policy': Affects entries after collection, during formatInput (e.g., TokenBudget)
+ */
+export type BoundaryClass = "formatter" | "policy";
+/**
+ * Definition for creating a boundary.
+ *
+ * @template T - The type of value this boundary holds
+ */
+export interface BoundaryDefinition<T> {
+    /** Default value when no provider above */
+    defaultValue: T | null;
+    /** Display name for debugging */
+    displayName?: string;
+    /** Boundary class - determines how compiler handles it */
+    class: BoundaryClass;
+}
+/**
+ * A Boundary object created by createBoundary().
+ *
+ * Boundaries ARE contexts with additional collection-phase effects.
+ *
+ * @template T - The type of value this boundary holds
+ */
+export interface Boundary<T> {
+    /** The underlying context (boundaries ARE contexts) */
+    readonly Context: Context<T | null>;
+    /** Provider component */
+    readonly Provider: BoundaryProvider<T>;
+    /** Boundary class */
+    readonly class: BoundaryClass;
+    /** Display name for debugging */
+    displayName?: string;
+    /**
+     * Internal: the definition.
+     * @internal
+     */
+    readonly _definition: BoundaryDefinition<T>;
+}
+/**
+ * Props for a boundary Provider component.
+ */
+export interface BoundaryProviderProps<T> {
+    /** The value to provide */
+    value: T;
+    /** Child components */
+    children?: any;
+}
+/**
+ * Internal data attached to boundary providers.
+ * @internal
+ */
+export interface BoundaryProviderData<T> {
+    class: BoundaryClass;
+    definition: BoundaryDefinition<T>;
+}
+/**
+ * A boundary Provider component type.
+ */
+export type BoundaryProvider<T> = {
+    (props: BoundaryProviderProps<T>): JSX.Element;
+    /** @internal - Boundary data for compiler detection */
+    [BOUNDARY_PROVIDER_SYMBOL]: BoundaryProviderData<T>;
+    /** Display name for debugging */
+    displayName?: string;
+};
+/**
+ * Creates a Boundary that extends Context with collection-phase effects.
+ *
+ * Boundaries can provide:
+ * - Context values (readable via useBoundary/useContext during render)
+ * - Formatter effects (affect content rendering during collection)
+ * - Policy effects (process entries after collection)
+ *
+ * @param definition - The boundary definition
+ * @returns A Boundary object with a Provider component
+ *
+ * @example
+ * ```tsx
+ * const MyBoundary = createBoundary({
+ *   defaultValue: null,
+ *   displayName: 'MyBoundary',
+ *   class: 'formatter',
+ *   formatter: (value) => new MyRenderer(),
+ * });
+ *
+ * // Use it
+ * <MyBoundary.Provider value={{}}>
+ *   {children}
+ * </MyBoundary.Provider>
+ * ```
+ */
+export declare function createBoundary<T>(definition: BoundaryDefinition<T>): Boundary<T>;
+/**
+ * Reads the current value of a boundary.
+ *
+ * This is a convenience wrapper around useContext that works with Boundary objects.
+ * Returns the value from the nearest Provider ancestor, or null if no Provider is found.
+ *
+ * @param boundary - The Boundary object (created by createBoundary)
+ * @returns The current boundary value, or null
+ *
+ * @example
+ * ```tsx
+ * const TokenBudgetBoundary = createPolicy<TokenBudgetProps>('TokenBudget', process);
+ *
+ * function TokenCounter() {
+ *   const budget = useBoundary(TokenBudgetBoundary);
+ *   if (!budget) return null;
+ *   return <System>Budget: {budget.maxTokens} tokens</System>;
+ * }
+ * ```
+ */
+export declare function useBoundary<T>(boundary: Boundary<T>): T | null;
+/**
+ * Value type for the FormatterBoundary.
+ * Just contains a formatter function - ContentRenderer is an internal implementation detail.
+ */
+export interface FormatterBoundaryValue {
+    /** The formatter function - transforms semantic blocks to content blocks */
+    formatter: Formatter;
+}
+/**
+ * The unified formatter boundary used by XML, Markdown, JSON, etc.
+ *
+ * All formatter components (XML, Markdown, JSON) use this single boundary.
+ * The value contains a formatter function. Use `useBoundary(FormatterBoundary)`
+ * to get the current formatter regardless of which formatter type is active.
+ *
+ * **Inner wins semantics:** When formatters are nested, the innermost formatter
+ * is used for content within its scope.
+ *
+ * @example
+ * ```tsx
+ * // In a component - get the current formatter
+ * const formatterValue = useBoundary(FormatterBoundary);
+ * if (formatterValue) {
+ *   const formatted = formatterValue.formatter(blocks);
+ * }
+ *
+ * // XML, Markdown, etc. use this boundary internally
+ * function XML({ children }) {
+ *   return (
+ *     <FormatterBoundary.Provider value={{ formatter: (blocks) => xmlRenderer.format(blocks) }}>
+ *       {children}
+ *     </FormatterBoundary.Provider>
+ *   );
+ * }
+ * ```
+ */
+export declare const FormatterBoundary: Boundary<FormatterBoundaryValue>;
+/**
+ * Creates a formatter component that uses the unified FormatterBoundary.
+ *
+ * This is a convenience function for creating formatter components like XML, Markdown.
+ * It creates a component that wraps children in FormatterBoundary.Provider with the
+ * provided formatter function.
+ *
+ * @param name - Display name for debugging
+ * @param formatter - The formatter function or factory
+ * @returns A component function that provides the formatter to children
+ *
+ * @example
+ * ```tsx
+ * // Create a custom formatter
+ * const CustomFormat = createFormatter('CustomFormat', (blocks) => {
+ *   return blocks.map(block => ({ type: 'text', text: `[${block.text}]` }));
+ * });
+ *
+ * // Use it
+ * <CustomFormat>
+ *   <Content />
+ * </CustomFormat>
+ * ```
+ */
+export declare function createFormatter(name: string, formatter: Formatter | (() => Formatter)): (props: {
+    children?: any;
+}) => JSX.Element;
+/**
+ * Policy process function type.
+ * Transforms timeline entries (filtering, summarization, etc.).
+ */
+export type PolicyProcessFunction<TConfig = unknown> = (entries: COMTimelineEntry[], config: TConfig) => COMTimelineEntry[] | Promise<COMTimelineEntry[]>;
+/**
+ * A single policy in the policy chain.
+ */
+export interface PolicyEntry<TConfig = unknown> {
+    /** Policy name for debugging/identification */
+    name: string;
+    /** The process function that transforms entries */
+    process: PolicyProcessFunction<TConfig>;
+    /** Configuration for this policy instance */
+    config: TConfig;
+}
+/**
+ * Value type for the PolicyBoundary.
+ * Holds an array of accumulated policies.
+ */
+export interface PolicyBoundaryValue {
+    /** Accumulated policies from all ancestors plus current */
+    policies: PolicyEntry[];
+}
+/**
+ * The unified policy boundary used by TokenBudget, etc.
+ *
+ * All policy components use this single boundary. Policies **accumulate** -
+ * nested policies don't replace parent policies, they add to them.
+ * Use `useBoundary(PolicyBoundary)` to get ALL active policies in scope.
+ *
+ * **Accumulating semantics:** When policies are nested, ALL policies apply
+ * to content within their combined scope, processed in order (outer first).
+ *
+ * @example
+ * ```tsx
+ * // In a component - get all active policies
+ * const policyValue = useBoundary(PolicyBoundary);
+ * if (policyValue) {
+ *   console.log('Active policies:', policyValue.policies.map(p => p.name));
+ *   // e.g., ['TokenBudget', 'Summarizer']
+ * }
+ * ```
+ *
+ * @example Nested policies accumulate - both TokenBudget AND Summarizer apply
+ * ```tsx
+ * <TokenBudget maxTokens={8000}>
+ *   <Summarizer threshold={5000}>
+ *     <Timeline />
+ *   </Summarizer>
+ * </TokenBudget>
+ * ```
+ */
+export declare const PolicyBoundary: Boundary<PolicyBoundaryValue>;
+/**
+ * Creates a policy component that auto-accumulates into PolicyBoundary.
+ *
+ * Policy boundaries affect the timeline entries during the formatInput phase,
+ * after all entries have been collected. Use this for filtering, transforming,
+ * or managing entries (e.g., token budgets, summarization).
+ *
+ * **Auto-accumulation:** The created component automatically reads parent policies
+ * from PolicyBoundary, appends its own policy, and provides the combined list.
+ * You don't need to manually handle accumulation.
+ *
+ * @param name - Display name for debugging
+ * @param process - Function to process entries
+ * @returns An object with Provider component and usePolicy hook
+ *
+ * @example Creating a policy
+ * ```typescript
+ * const tokenBudget = createPolicy<TokenBudgetProps>(
+ *   'TokenBudget',
+ *   async (entries, props) => applyTokenBudget(entries, props)
+ * );
+ *
+ * // Use the Provider - auto-accumulates with parent policies
+ * // <tokenBudget.Provider value={{ maxTokens: 4000, strategy: 'drop-oldest' }}>
+ * //   <Timeline />
+ * // </tokenBudget.Provider>
+ *
+ * // Read this specific policy's config with usePolicy hook
+ * // const config = tokenBudget.usePolicy();
+ * ```
+ */
+export declare function createPolicy<TConfig>(name: string, process: PolicyProcessFunction<TConfig>): {
+    /** Provider component that auto-accumulates into PolicyBoundary */
+    Provider: (props: {
+        value: TConfig;
+        children?: any;
+    }) => JSX.Element;
+    /** Hook to read this specific policy's config (innermost) */
+    usePolicy: () => TConfig | null;
+    /** The policy name */
+    name: string;
+    /** The process function */
+    process: PolicyProcessFunction<TConfig>;
+};
+/**
+ * Check if a component is a boundary provider.
+ * Used by the fiber compiler during traversal.
+ *
+ * @internal
+ */
+export declare function isBoundaryProvider(component: unknown): component is BoundaryProvider<unknown>;
+/**
+ * Get the boundary data from a provider component.
+ *
+ * @internal
+ */
+export declare function getBoundaryData<T>(provider: BoundaryProvider<T>): BoundaryProviderData<T>;
+//# sourceMappingURL=boundary.d.ts.map

package/dist/state/boundary.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"boundary.d.ts","sourceRoot":"","sources":["../../src/state/boundary.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA6CG;AAGH,OAAO,KAAK,EAAE,GAAG,EAAE,MAAM,oBAAoB,CAAC;AAC9C,OAAO,EAA6B,KAAK,OAAO,EAAE,MAAM,WAAW,CAAC;AACpE,OAAO,KAAK,EAAE,SAAS,EAAE,MAAM,cAAc,CAAC;AAC9C,OAAO,KAAK,EAAE,gBAAgB,EAAE,MAAM,cAAc,CAAC;AAMrD;;;GAGG;AACH,eAAO,MAAM,wBAAwB,eAA4C,CAAC;AAElF;;;;GAIG;AACH,MAAM,MAAM,aAAa,GAAG,WAAW,GAAG,QAAQ,CAAC;AAEnD;;;;GAIG;AACH,MAAM,WAAW,kBAAkB,CAAC,CAAC;IACnC,2CAA2C;IAC3C,YAAY,EAAE,CAAC,GAAG,IAAI,CAAC;IAEvB,iCAAiC;IACjC,WAAW,CAAC,EAAE,MAAM,CAAC;IAErB,0DAA0D;IAC1D,KAAK,EAAE,aAAa,CAAC;CACtB;AAED;;;;;;GAMG;AACH,MAAM,WAAW,QAAQ,CAAC,CAAC;IACzB,uDAAuD;IACvD,QAAQ,CAAC,OAAO,EAAE,OAAO,CAAC,CAAC,GAAG,IAAI,CAAC,CAAC;IAEpC,yBAAyB;IACzB,QAAQ,CAAC,QAAQ,EAAE,gBAAgB,CAAC,CAAC,CAAC,CAAC;IAEvC,qBAAqB;IACrB,QAAQ,CAAC,KAAK,EAAE,aAAa,CAAC;IAE9B,iCAAiC;IACjC,WAAW,CAAC,EAAE,MAAM,CAAC;IAErB;;;OAGG;IACH,QAAQ,CAAC,WAAW,EAAE,kBAAkB,CAAC,CAAC,CAAC,CAAC;CAC7C;AAED;;GAEG;AACH,MAAM,WAAW,qBAAqB,CAAC,CAAC;IACtC,2BAA2B;IAC3B,KAAK,EAAE,CAAC,CAAC;IACT,uBAAuB;IACvB,QAAQ,CAAC,EAAE,GAAG,CAAC;CAChB;AAED;;;GAGG;AACH,MAAM,WAAW,oBAAoB,CAAC,CAAC;IACrC,KAAK,EAAE,aAAa,CAAC;IACrB,UAAU,EAAE,kBAAkB,CAAC,CAAC,CAAC,CAAC;CACnC;AAED;;GAEG;AACH,MAAM,MAAM,gBAAgB,CAAC,CAAC,IAAI;IAChC,CAAC,KAAK,EAAE,qBAAqB,CAAC,CAAC,CAAC,GAAG,GAAG,CAAC,OAAO,CAAC;IAC/C,uDAAuD;IACvD,CAAC,wBAAwB,CAAC,EAAE,oBAAoB,CAAC,CAAC,CAAC,CAAC;IACpD,iCAAiC;IACjC,WAAW,CAAC,EAAE,MAAM,CAAC;CACtB,CAAC;AAMF;;;;;;;;;;;;;;;;;;;;;;;;;GAyBG;AACH,wBAAgB,cAAc,CAAC,CAAC,EAAE,UAAU,EAAE,kBAAkB,CAAC,CAAC,CAAC,GAAG,QAAQ,CAAC,CAAC,CAAC,CAmChF;AAMD;;;;;;;;;;;;;;;;;;;GAmBG;AACH,wBAAgB,WAAW,CAAC,CAAC,EAAE,QAAQ,EAAE,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,GAAG,IAAI,CAE9D;AAMD;;;GAGG;AACH,MAAM,WAAW,sBAAsB;IACrC,4EAA4E;IAC5E,SAAS,EAAE,SAAS,CAAC;CACtB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2BG;AACH,eAAO,MAAM,iBAAiB,EAAE,QAAQ,CAAC,sBAAsB,CAK3D,CAAC;AAML;;;;;;;;;;;;;;;;;;;;;;;GAuBG;AACH,wBAAgB,eAAe,CAC7B,IAAI,EAAE,MAAM,EACZ,SAAS,EAAE,SAAS,GAAG,CAAC,MAAM,SAAS,CAAC,GACvC,CAAC,KAAK,EAAE;IAAE,QAAQ,CAAC,EAAE,GAAG,CAAA;CAAE,KAAK,GAAG,CAAC,OAAO,CAe5C;AAMD;;;GAGG;AACH,MAAM,MAAM,qBAAqB,CAAC,OAAO,GAAG,OAAO,IAAI,CACrD,OAAO,EAAE,gBAAgB,EAAE,EAC3B,MAAM,EAAE,OAAO,KACZ,gBAAgB,EAAE,GAAG,OAAO,CAAC,gBAAgB,EAAE,CAAC,CAAC;AAEtD;;GAEG;AACH,MAAM,WAAW,WAAW,CAAC,OAAO,GAAG,OAAO;IAC5C,+CAA+C;IAC/C,IAAI,EAAE,MAAM,CAAC;IACb,mDAAmD;IACnD,OAAO,EAAE,qBAAqB,CAAC,OAAO,CAAC,CAAC;IACxC,6CAA6C;IAC7C,MAAM,EAAE,OAAO,CAAC;CACjB;AAED;;;GAGG;AACH,MAAM,WAAW,mBAAmB;IAClC,2DAA2D;IAC3D,QAAQ,EAAE,WAAW,EAAE,CAAC;CACzB;AAED;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA4BG;AACH,eAAO,MAAM,cAAc,EAAE,QAAQ,CAAC,mBAAmB,CAIvD,CAAC;AAMH;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA8BG;AACH,wBAAgB,YAAY,CAAC,OAAO,EAClC,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,qBAAqB,CAAC,OAAO,CAAC,GACtC;IACD,mEAAmE;IACnE,QAAQ,EAAE,CAAC,KAAK,EAAE;QAAE,KAAK,EAAE,OAAO,CAAC;QAAC,QAAQ,CAAC,EAAE,GAAG,CAAA;KAAE,KAAK,GAAG,CAAC,OAAO,CAAC;IACrE,6DAA6D;IAC7D,SAAS,EAAE,MAAM,OAAO,GAAG,IAAI,CAAC;IAChC,sBAAsB;IACtB,IAAI,EAAE,MAAM,CAAC;IACb,2BAA2B;IAC3B,OAAO,EAAE,qBAAqB,CAAC,OAAO,CAAC,CAAC;CACzC,CAyCA;AAMD;;;;;GAKG;AACH,wBAAgB,kBAAkB,CAAC,SAAS,EAAE,OAAO,GAAG,SAAS,IAAI,gBAAgB,CAAC,OAAO,CAAC,CAM7F;AAED;;;;GAIG;AACH,wBAAgB,eAAe,CAAC,CAAC,EAAE,QAAQ,EAAE,gBAAgB,CAAC,CAAC,CAAC,GAAG,oBAAoB,CAAC,CAAC,CAAC,CAEzF"}

package/dist/state/boundary.js

@@ -0,0 +1,341 @@
+/**
+ * Boundary System for Tentickle
+ *
+ * Boundaries extend Context with collection-phase effects. They provide a generic
+ * mechanism for components that affect how their children are processed during
+ * compilation, without hardcoding specific component checks in the compiler.
+ *
+ * The abstraction ladder:
+ * - createContext: render-phase values, read via useContext
+ * - createBoundary: render-phase values + collection-phase effects
+ * - createFormatter: convenience for formatter boundaries (collection-time)
+ * - createPolicy: convenience for policy boundaries (format-time, auto-accumulating)
+ *
+ * @example Formatter boundary (like XML, Markdown)
+ * ```tsx
+ * // XML/Markdown use the unified FormatterBoundary
+ * <XML>
+ *   <Content />
+ * </XML>
+ *
+ * // To get the current formatter during render:
+ * const formatter = useBoundary(FormatterBoundary);
+ * if (formatter) {
+ *   const formatted = formatter.formatter(blocks);
+ * }
+ * ```
+ *
+ * @example Policy boundary (like TokenBudget)
+ * ```tsx
+ * // Policies auto-accumulate - nested policies are combined
+ * <TokenBudget maxTokens={8000} strategy="drop-oldest">
+ *   <Timeline />
+ *   <TokenBudget maxTokens={2000} strategy="truncate">
+ *     <User>{message}</User>  {/* Both policies apply \*\/}
+ *   </TokenBudget>
+ * </TokenBudget>
+ *
+ * // To get all active policies during render:
+ * const policyValue = useBoundary(PolicyBoundary);
+ * if (policyValue) {
+ *   console.log('Active policies:', policyValue.policies.map(p => p.name));
+ * }
+ * ```
+ *
+ * @module tentickle/boundary
+ */
+import { createElement } from "../jsx/jsx-runtime";
+import { createContext, useContext } from "./context";
+// ============================================================================
+// Types
+// ============================================================================
+/**
+ * Symbol used to mark boundary provider components.
+ * The fiber compiler detects this to handle boundary effects.
+ */
+export const BOUNDARY_PROVIDER_SYMBOL = Symbol.for("tentickle.boundary.provider");
+// ============================================================================
+// createBoundary
+// ============================================================================
+/**
+ * Creates a Boundary that extends Context with collection-phase effects.
+ *
+ * Boundaries can provide:
+ * - Context values (readable via useBoundary/useContext during render)
+ * - Formatter effects (affect content rendering during collection)
+ * - Policy effects (process entries after collection)
+ *
+ * @param definition - The boundary definition
+ * @returns A Boundary object with a Provider component
+ *
+ * @example
+ * ```tsx
+ * const MyBoundary = createBoundary({
+ *   defaultValue: null,
+ *   displayName: 'MyBoundary',
+ *   class: 'formatter',
+ *   formatter: (value) => new MyRenderer(),
+ * });
+ *
+ * // Use it
+ * <MyBoundary.Provider value={{}}>
+ *   {children}
+ * </MyBoundary.Provider>
+ * ```
+ */
+export function createBoundary(definition) {
+    const displayName = definition.displayName || "Boundary";
+    // Create underlying context (boundaries ARE contexts)
+    const Context = createContext(definition.defaultValue, displayName);
+    // Create the Provider component
+    function Provider(props) {
+        // Provider wraps Context.Provider
+        // The fiber compiler detects this via BOUNDARY_PROVIDER_SYMBOL
+        // and applies the boundary effects during traversal
+        return createElement(Context.Provider, {
+            value: props.value,
+            children: props.children,
+        });
+    }
+    // Mark as boundary provider so compiler can detect it
+    const boundaryData = {
+        class: definition.class,
+        definition,
+    };
+    Provider[BOUNDARY_PROVIDER_SYMBOL] = boundaryData;
+    Provider.displayName = `${displayName}.Provider`;
+    // Create the boundary object
+    const boundary = {
+        Context,
+        Provider: Provider,
+        class: definition.class,
+        displayName,
+        _definition: definition,
+    };
+    return boundary;
+}
+// ============================================================================
+// useBoundary
+// ============================================================================
+/**
+ * Reads the current value of a boundary.
+ *
+ * This is a convenience wrapper around useContext that works with Boundary objects.
+ * Returns the value from the nearest Provider ancestor, or null if no Provider is found.
+ *
+ * @param boundary - The Boundary object (created by createBoundary)
+ * @returns The current boundary value, or null
+ *
+ * @example
+ * ```tsx
+ * const TokenBudgetBoundary = createPolicy<TokenBudgetProps>('TokenBudget', process);
+ *
+ * function TokenCounter() {
+ *   const budget = useBoundary(TokenBudgetBoundary);
+ *   if (!budget) return null;
+ *   return <System>Budget: {budget.maxTokens} tokens</System>;
+ * }
+ * ```
+ */
+export function useBoundary(boundary) {
+    return useContext(boundary.Context);
+}
+/**
+ * The unified formatter boundary used by XML, Markdown, JSON, etc.
+ *
+ * All formatter components (XML, Markdown, JSON) use this single boundary.
+ * The value contains a formatter function. Use `useBoundary(FormatterBoundary)`
+ * to get the current formatter regardless of which formatter type is active.
+ *
+ * **Inner wins semantics:** When formatters are nested, the innermost formatter
+ * is used for content within its scope.
+ *
+ * @example
+ * ```tsx
+ * // In a component - get the current formatter
+ * const formatterValue = useBoundary(FormatterBoundary);
+ * if (formatterValue) {
+ *   const formatted = formatterValue.formatter(blocks);
+ * }
+ *
+ * // XML, Markdown, etc. use this boundary internally
+ * function XML({ children }) {
+ *   return (
+ *     <FormatterBoundary.Provider value={{ formatter: (blocks) => xmlRenderer.format(blocks) }}>
+ *       {children}
+ *     </FormatterBoundary.Provider>
+ *   );
+ * }
+ * ```
+ */
+export const FormatterBoundary = createBoundary({
+    defaultValue: null,
+    displayName: "Formatter",
+    class: "formatter",
+});
+// ============================================================================
+// createFormatter
+// ============================================================================
+/**
+ * Creates a formatter component that uses the unified FormatterBoundary.
+ *
+ * This is a convenience function for creating formatter components like XML, Markdown.
+ * It creates a component that wraps children in FormatterBoundary.Provider with the
+ * provided formatter function.
+ *
+ * @param name - Display name for debugging
+ * @param formatter - The formatter function or factory
+ * @returns A component function that provides the formatter to children
+ *
+ * @example
+ * ```tsx
+ * // Create a custom formatter
+ * const CustomFormat = createFormatter('CustomFormat', (blocks) => {
+ *   return blocks.map(block => ({ type: 'text', text: `[${block.text}]` }));
+ * });
+ *
+ * // Use it
+ * <CustomFormat>
+ *   <Content />
+ * </CustomFormat>
+ * ```
+ */
+export function createFormatter(name, formatter) {
+    const resolvedFormatter = typeof formatter === "function" && formatter.length === 0
+        ? formatter()
+        : formatter;
+    function FormatterComponent(props) {
+        return createElement(FormatterBoundary.Provider, {
+            value: { formatter: resolvedFormatter },
+            children: props.children,
+        });
+    }
+    FormatterComponent.displayName = name;
+    return FormatterComponent;
+}
+/**
+ * The unified policy boundary used by TokenBudget, etc.
+ *
+ * All policy components use this single boundary. Policies **accumulate** -
+ * nested policies don't replace parent policies, they add to them.
+ * Use `useBoundary(PolicyBoundary)` to get ALL active policies in scope.
+ *
+ * **Accumulating semantics:** When policies are nested, ALL policies apply
+ * to content within their combined scope, processed in order (outer first).
+ *
+ * @example
+ * ```tsx
+ * // In a component - get all active policies
+ * const policyValue = useBoundary(PolicyBoundary);
+ * if (policyValue) {
+ *   console.log('Active policies:', policyValue.policies.map(p => p.name));
+ *   // e.g., ['TokenBudget', 'Summarizer']
+ * }
+ * ```
+ *
+ * @example Nested policies accumulate - both TokenBudget AND Summarizer apply
+ * ```tsx
+ * <TokenBudget maxTokens={8000}>
+ *   <Summarizer threshold={5000}>
+ *     <Timeline />
+ *   </Summarizer>
+ * </TokenBudget>
+ * ```
+ */
+export const PolicyBoundary = createBoundary({
+    defaultValue: null,
+    displayName: "Policy",
+    class: "policy",
+});
+// ============================================================================
+// createPolicy
+// ============================================================================
+/**
+ * Creates a policy component that auto-accumulates into PolicyBoundary.
+ *
+ * Policy boundaries affect the timeline entries during the formatInput phase,
+ * after all entries have been collected. Use this for filtering, transforming,
+ * or managing entries (e.g., token budgets, summarization).
+ *
+ * **Auto-accumulation:** The created component automatically reads parent policies
+ * from PolicyBoundary, appends its own policy, and provides the combined list.
+ * You don't need to manually handle accumulation.
+ *
+ * @param name - Display name for debugging
+ * @param process - Function to process entries
+ * @returns An object with Provider component and usePolicy hook
+ *
+ * @example Creating a policy
+ * ```typescript
+ * const tokenBudget = createPolicy<TokenBudgetProps>(
+ *   'TokenBudget',
+ *   async (entries, props) => applyTokenBudget(entries, props)
+ * );
+ *
+ * // Use the Provider - auto-accumulates with parent policies
+ * // <tokenBudget.Provider value={{ maxTokens: 4000, strategy: 'drop-oldest' }}>
+ * //   <Timeline />
+ * // </tokenBudget.Provider>
+ *
+ * // Read this specific policy's config with usePolicy hook
+ * // const config = tokenBudget.usePolicy();
+ * ```
+ */
+export function createPolicy(name, process) {
+    // Create a context for this specific policy's config
+    const PolicyConfigContext = createContext(null, `${name}Config`);
+    function PolicyProvider(props) {
+        // Get parent policies (auto-accumulation)
+        const parentValue = useContext(PolicyBoundary.Context);
+        const parentPolicies = parentValue?.policies || [];
+        // Create new policy entry
+        const newPolicy = {
+            name,
+            process: process,
+            config: props.value,
+        };
+        // Combine parent policies with this one
+        const combinedPolicies = [...parentPolicies, newPolicy];
+        // Provide both the combined policies AND this policy's specific config
+        return createElement(PolicyBoundary.Provider, {
+            value: { policies: combinedPolicies },
+            children: createElement(PolicyConfigContext.Provider, {
+                value: props.value,
+                children: props.children,
+            }),
+        });
+    }
+    PolicyProvider.displayName = `${name}.Provider`;
+    function usePolicy() {
+        return useContext(PolicyConfigContext);
+    }
+    return {
+        Provider: PolicyProvider,
+        usePolicy,
+        name,
+        process,
+    };
+}
+// ============================================================================
+// Utilities
+// ============================================================================
+/**
+ * Check if a component is a boundary provider.
+ * Used by the fiber compiler during traversal.
+ *
+ * @internal
+ */
+export function isBoundaryProvider(component) {
+    return (typeof component === "function" &&
+        BOUNDARY_PROVIDER_SYMBOL in component &&
+        component[BOUNDARY_PROVIDER_SYMBOL] !== undefined);
+}
+/**
+ * Get the boundary data from a provider component.
+ *
+ * @internal
+ */
+export function getBoundaryData(provider) {
+    return provider[BOUNDARY_PROVIDER_SYMBOL];
+}
+//# sourceMappingURL=boundary.js.map