Timeline and usage records
Retain bounded execution history and usage while preserving the distinction between observation and enforcement.
Record the facts you need to recover
TimelineStore persists JSON-shaped events with run identity and bounded reads. Await writes when they are part of acceptance or terminal publication; an unobserved write promise cannot support an audit guarantee.
import type {
TimelineStore,
RunUsageTracker,
} from "@smoothie-framework/runtime/governance";
import {
FileTimelineStore,
FileRunUsageTracker,
} from "@smoothie-framework/runtime-node";Choose retention, privacy and resource access in the host. Node file adapters are separate implementations, not proof of a transactional multi-store deployment.
Do not turn accounting into admission
RunUsageTracker records tokens and cost after work. Use InferenceBudgetController for atomic admission before each provider attempt.
Durable Worker history requires atomic run/timeline projection, not two unrelated append calls. An event describes recorded evidence, not an exactly-once external effect or a complete tracing platform.