Deliberationv4.6.1

Config provenance and comparison

Config provenance and comparison

core/config-history.js hashes a versioned allowlisted effective snapshot. Built-in construction settings remain active until restart; hot routing and OpenRouter aliases take effect on the next run. Runs pin their snapshot, configId, activationId and runtimeId. A -> B -> A reuses its configId and creates another activation. Debug events, sessions and journals share a runId. Cache hits retain original provenance and add no fresh timing, votes or measured token spending. Grounded requests bypass the result cache.

The catalog is opt-in alongside telemetry. Atomic 0600 records in private 0700 directories are bounded to 500 history/200 runtime manifests and 64KiB per record. Runtime manifests require journaling, heartbeat every 30s, and become stale/unknown after 90s. Ingestion validates ownership, size, hashes, allowlists and symlinks. Catalog failure cannot prevent delegation; runs carry their own snapshots. Observed runtimes are not a complete live inventory.

analyze accepts groupBy: "config", full SHA-256 configId (or unknown), activationId, and existing since windows. A closed start-time cohort includes attempts and terminal outcomes beyond the window boundary. Uncorrelated legacy calls use event time. Whole-run latency/outcomes require journals; live/reused runs are separate, and missing token usage remains unknown. Historical groups retain recorded membership regardless of configuredOnly. Timing and agreement stay separate; advisory recommendations use config/workload/settings cohorts. Stats and its daily chart share filters and deduplicate journals/sessions by runId. Bounded reads disclose truncation.

routing.timeoutPolicy selects longest-peer (default) or per-provider. Fan-outs resolve limits before dispatch, with one absolute deadline capped by host and consensus budgets; retries/backoff consume it. Short caps are intentionally waived under longest-peer. Progressive panel/ask-one uses a UUID fanoutId, independently of optional journal runId. Groups pin membership/settings, start their clock at first dispatch, reject duplicates/nonmembers/replays, expire missing members, and abort attempts on expiry/shutdown. Member host caps and cancellation affect only that member. Idle contexts expire after 10 minutes, with at most 1000 groups. Single calls and sequential arbiter phases keep their own limits while respecting overall consensus budgets.

Rendered from TECHNICAL.md in the repository.

Type to search the site.