@noetic-tools/context 1.0.0 → 1.2.0

package/dist/context/layers/static-content.js

@@ -12,6 +12,9 @@ export function staticContent(opts) {
         id: opts.id ?? 'static-content',
         slot: opts.slot ?? Slot.WORKING_MEMORY + 5,
         scope: opts.scope ?? 'resource',
+        // Loaded once in `init` and never rewritten, so it can be pinned outright
+        // rather than waiting for churn telemetry to work that out.
+        placement: 'anchor',
         hooks: {
             async init() {
                 const raw = await opts.load();

package/dist/context/layers/steering.d.ts

@@ -11,6 +11,7 @@ export declare function steering(config: SteeringConfig): {
     name: string;
     slot: 90;
     scope: ContextScope;
+    placement: "live";
     budget: {
         min: number;
         max: number;

package/dist/context/layers/steering.js

@@ -162,6 +162,11 @@ export function steering(config) {
         name: 'Steering',
         slot: Slot.STEERING,
         scope,
+        // `recall` drains the pending queue as it renders, so its output can never
+        // be replayed from a pin — the drain is already committed, and serving an
+        // older render would lose the feedback for good. Rendering after history
+        // also puts guidance where the model weighs it most.
+        placement: 'live',
         budget: {
             min: 0,
             max: 500,

package/dist/context/layers/temporal-context.js

@@ -211,6 +211,12 @@ export function temporalContext(config) {
         // Grounding sits near the top of the window, before reasoning content.
         slot: Slot.REMINDER,
         scope: config?.scope ?? 'resource',
+        // The `<current_datetime>` block changes every turn by construction, so
+        // anchoring it would re-bill the whole window each time. Churn telemetry
+        // would reach the same verdict — this just skips the learning cost. With
+        // grounding off, only the slow-moving fact ledger remains, which is worth
+        // anchoring, so leave that to `'auto'`.
+        placement: groundDateTime ? 'live' : 'auto',
         budget: {
             min: 0,
             max: injectLedger ? 800 : 200,

package/dist/context/projector.d.ts

@@ -1,19 +1,38 @@
 import type { Item, ProjectionPolicy } from '@noetic-tools/types';
 interface AssembleViewParams {
     systemPromptItems: Item[];
+    /** Anchor band — layer output rendered before history, where a prompt cache can hold it. */
     layerOutputItems: Item[];
     historyItems: Item[];
+    /** Live band — layer output rendered after history, slot-ascending. */
+    liveLayerItems?: Item[];
+    /** Supersedes for anchored layers whose pinned output went stale. */
+    deltaItems?: Item[];
+    /** Items that must land last, after everything else. Never dropped. */
+    tailItems?: Item[];
     policy?: ProjectionPolicy;
 }
 /**
- * Assemble the model's context window from system prompt items, context-layer
- * recall output (slot-ascending), and conversation history.
+ * Assemble the model's context window in bands:
  *
- * Without a `policy` the inputs are concatenated as-is (optionally sliding the
- * history window by `windowSize`). With a `policy` the assembled view is held to
- * a hard token budget: system items are always kept; layer output is kept
- * low-slot-first (highest-slot dropped when tight); history takes the remainder,
- * keeping the most recent turns.
+ * ```
+ * system | anchor layers | history | live layers | supersedes | tail
+ * ```
+ *
+ * The split exists for the prompt cache, which matches on a prefix. Stable
+ * layer output sits ahead of history where it can be cached; volatile output
+ * sits after it, where re-rendering costs almost nothing. Both bands arrive
+ * slot-ascending.
+ *
+ * Without a `policy` the bands are concatenated as-is (optionally sliding the
+ * history window by `windowSize`). With a `policy` the view is held to a hard
+ * token budget, claimed in this order: system items, then anchor output, then
+ * live output, then supersedes, then the tail — with history taking whatever
+ * remains and keeping the most recent turns.
+ *
+ * Supersedes are claimed ahead of history, and all together or not at all: a
+ * dropped supersede would leave the model reading a pinned block the runtime
+ * knows is stale. The caller re-anchors instead — see `prepareBandedView`.
  */
-export declare function assembleView({ systemPromptItems, layerOutputItems, historyItems, policy, }: AssembleViewParams): Item[];
+export declare function assembleView({ systemPromptItems, layerOutputItems, historyItems, liveLayerItems, deltaItems, tailItems, policy, }: AssembleViewParams): Item[];
 export {};

package/dist/context/projector.js

@@ -57,33 +57,62 @@ function keepRecentWithinBudget(items, budget, windowSize) {
 //#endregion
 //#region Public API
 /**
- * Assemble the model's context window from system prompt items, context-layer
- * recall output (slot-ascending), and conversation history.
+ * Assemble the model's context window in bands:
  *
- * Without a `policy` the inputs are concatenated as-is (optionally sliding the
- * history window by `windowSize`). With a `policy` the assembled view is held to
- * a hard token budget: system items are always kept; layer output is kept
- * low-slot-first (highest-slot dropped when tight); history takes the remainder,
- * keeping the most recent turns.
+ * ```
+ * system | anchor layers | history | live layers | supersedes | tail
+ * ```
+ *
+ * The split exists for the prompt cache, which matches on a prefix. Stable
+ * layer output sits ahead of history where it can be cached; volatile output
+ * sits after it, where re-rendering costs almost nothing. Both bands arrive
+ * slot-ascending.
+ *
+ * Without a `policy` the bands are concatenated as-is (optionally sliding the
+ * history window by `windowSize`). With a `policy` the view is held to a hard
+ * token budget, claimed in this order: system items, then anchor output, then
+ * live output, then supersedes, then the tail — with history taking whatever
+ * remains and keeping the most recent turns.
+ *
+ * Supersedes are claimed ahead of history, and all together or not at all: a
+ * dropped supersede would leave the model reading a pinned block the runtime
+ * knows is stale. The caller re-anchors instead — see `prepareBandedView`.
  */
-export function assembleView({ systemPromptItems, layerOutputItems, historyItems, policy, }) {
+export function assembleView({ systemPromptItems, layerOutputItems, historyItems, liveLayerItems = [], deltaItems = [], tailItems = [], policy, }) {
     if (!policy) {
         return [
             ...systemPromptItems,
             ...layerOutputItems,
             ...historyItems,
+            ...liveLayerItems,
+            ...deltaItems,
+            ...tailItems,
         ];
     }
     const budget = Math.max(0, policy.tokenBudget - policy.responseReserve);
     // System items are never dropped — they anchor the conversation.
-    const afterSystem = Math.max(0, budget - totalTokens(systemPromptItems));
-    const keptLayers = keepFrontWithinBudget(layerOutputItems, afterSystem);
-    const afterLayers = Math.max(0, afterSystem - totalTokens(keptLayers));
-    const keptHistory = keepRecentWithinBudget(historyItems, afterLayers, policy.windowSize);
+    let left = Math.max(0, budget - totalTokens(systemPromptItems));
+    const keptAnchor = keepFrontWithinBudget(layerOutputItems, left);
+    left = Math.max(0, left - totalTokens(keptAnchor));
+    const keptLive = keepFrontWithinBudget(liveLayerItems, left);
+    left = Math.max(0, left - totalTokens(keptLive));
+    // The tail carries steering guidance, which must reach the model whatever the
+    // budget says — it is the correction the retry exists to deliver.
+    left = Math.max(0, left - totalTokens(tailItems));
+    // Supersedes are never dropped either. Each one corrects a pinned block that
+    // is already in the view, so dropping one leaves the model reading content
+    // the runtime knows is stale — silent corruption, and far worse than losing
+    // a turn of history. History absorbs the cost; `deltaBudgetFraction` keeps
+    // the supersedes from growing large enough for that to hurt.
+    left = Math.max(0, left - totalTokens(deltaItems));
+    const keptHistory = keepRecentWithinBudget(historyItems, left, policy.windowSize);
     return [
         ...systemPromptItems,
-        ...keptLayers,
+        ...keptAnchor,
         ...keptHistory,
+        ...keptLive,
+        ...deltaItems,
+        ...tailItems,
     ];
 }
 //#endregion

package/dist/index.d.ts

@@ -6,6 +6,7 @@
 export type { ContextScope, ExecutionContext, ExecutionOutcome, LayerCallModelRequest, } from '@noetic-tools/types';
 export * from '@noetic-tools/types/contract';
 export * from './context/budget.js';
+export * from './context/cache-anchoring.js';
 export * from './context/exec-context-factory.js';
 export * from './context/function-call-utils.js';
 export * from './context/layer-api.js';

package/dist/index.js

@@ -8,6 +8,7 @@
 // @noetic-tools/context remains the one-stop import for context-layer authoring.
 export * from '@noetic-tools/types/contract';
 export * from './context/budget.js';
+export * from './context/cache-anchoring.js';
 export * from './context/exec-context-factory.js';
 export * from './context/function-call-utils.js';
 export * from './context/layer-api.js';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noetic-tools/context",
-  "version": "1.0.0",
+  "version": "1.2.0",
   "type": "module",
   "description": "Context layer system for Noetic agents: the ContextLayer contract, lifecycle, budget/projection machinery, and built-in layer implementations.",
   "license": "Apache-2.0",
@@ -44,7 +44,7 @@
     "zod": "^4.0.0"
   },
   "dependencies": {
-    "@noetic-tools/types": "^2.3.0",
+    "@noetic-tools/types": "^3.1.0",
     "zod": "^4.0.0"
   },
   "scripts": {