FabrCore 2.0.0: One Host, Two Runtime Modes

FabrCore 2.0 brings the current agent runtime and integrations together. This release makes the hosting choice explicit: start in a trusted standalone workspace, or enable SQL for persistent runtime state, enforced access control and integrated knowledge services.

A simpler package layout

SQL Server hosting, Memory and GraphRAG now ship in FabrCore.Host. Shared service contracts live in Core; remote Memory clients and harness integration live in SDK. Agent libraries can use SDK/Core without taking a SQL implementation dependency.

The four former SQL/service packages are retired, with no forwarding packages. Azure Storage, Surface, transport clients, testing helpers and Microsoft 365 integration remain separate. The current build inventory contains twelve packages, including the optional Connections, Services.Connections and Services.RemoteAgents packages. Stable 2.0.0 publication is pending.

Standalone is a trusted workspace

Agents, harnesses, tools, MCP, blueprints and Surface squads work without a database. Default runtime state is in memory and is lost on process restart. Cross-principal messaging bypasses ACL, while authentication, privileged administration and storage/session ownership checks still apply.

One connection enables SQL features

Configure ConnectionStrings:FabrCore for SQL Orleans defaults, relational ACL, Memory, GraphRAG and durable operational stores. A compatible existing SQL Server 2025/Azure SQL database and required model aliases are checked at startup. Invalid SQL configuration fails explicitly rather than switching to standalone.

Memory remains a per-agent scope/plugin choice. Existing split databases and explicit Azure/custom Orleans providers are supported. ACL data moves into relational tables and requires export/import before cutover.

Context compaction is more careful

Both standard SDK agents and harnesses now check working context inside the tool loop before every model call. Older tool output becomes bounded excerpts while original output remains in history. Durable compaction validates its handover before a single history write and leaves the original intact when validation fails.

The automatic durable threshold is 70% of a usable input working set, with a 75% fallback. Protected oversized content stops explicitly. Neither compaction layer requires long-term Memory.

Durability has clear limits

SQL audit, execution evidence and A2A task snapshots survive process restart. Signing is still explicit. A2A leases fence stale writers, and interrupted execution fails instead of replaying uncertain external effects. SQL stores task snapshots, not replayable SSE history.

FabrCore targets .NET 10, Orleans 10.3.1 and Agent Framework 1.20.0. Memory streams remain the default; the optional SQL streaming provider retains its pinned upstream preview version.

Manage clusters through an open cloud contract

FabrCore 2.0 includes versioned administration for principal and ACL CRUD, blueprint authoring and deployment, installed agent building and lifecycle management. Review revisions and expansion digests before applying blueprints, choose ensure or update, and inspect per-agent results. Persistent operation receipts make long-running work pollable without silently replaying uncertain side effects.

Vulcan365 Insights provides the operator experience; third-party servers use the same Core contracts and SDK without Insights dependencies. The cluster keeps its outbound HTTP long polling. Existing agent WebSockets continue to serve application chat.

Ask about an agent without changing its conversation

A separate diagnostic agent can inspect copied histories, captured errors, configuration, state and execution evidence. Its operator-owned fork stays outside normal message flow and excludes business tools, MCP execution and mutations. One admin turn can overlap normal user processing, with separate model usage and a default 120-second timeout. Answers cite available records and acknowledge missing capture rather than claim hidden reasoning.

Read retained observations on demand

Paged monitoring and immutable evidence exports expose captured data without a constant cloud stream. Optional SQL monitoring buffers writes with seven-day retention by default and reports drops, lag and persistence failures. Views identify source coverage and offline hosts; evidence exports preserve signatures, certificates and attestations. Existing audit functionality is unchanged.

Read the cloud administration guide and download the 2.0 coding assistant skills. The validation report records completed checks and remaining multi-silo, sustained SQL and real-model evaluations; it does not claim a production performance guarantee.

Upgrade with the application and its data

Rebuild every consumer, remove retired references, choose the intended mode and rehearse state/ACL migration on a restored database copy. The new release skill gives developers and their coding AI cumulative guidance from 1.6, 1.7 and 1.8 to 2.0.