---
title: "2026-09-16 Factory direct vxData client"
description: "Removed client injection and the SQLite stand-in at the user's request."
image: "https://docs.virdx.dev/img/virdx-social-card.png"
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.virdx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# 2026-09-16 Factory direct vxData client

## Work Done

In `~/work/factory-framework`, removed client_factory, the generic client-lifecycle
wrapper and fallback constructor. Check and direct batch execution now use
`with vxdata.sdk.Client() as client` (imported lazily in those methods).
Removed SQLite, the example client, fake persistence tests and SQLite ignore rules.
The usage example is explicitly a service registration template: application-specific
query and inference/write methods raise NotImplementedError. No real diagnosis
schema or persistence behavior was invented. Updated README requirements and test claims.

## Pitfalls

The earlier request for tests without vxData did not imply that a client injection
API or fake persistence should remain in the framework. The latest user direction
supersedes it: assume a real vxData instance and SDK, no mock client support.

Validation: all five focused runtime/interface tests pass. Full suite: 14 pass,
one unrelated Argo test fails because it expects ephemeral-storage but the current
backend resources omit it. That backend was not modified in this change. No live
vxData queries or writes were attempted; offline checks do not validate persistence.

## Improvements

Keep infrastructure client ownership direct and domain-specific work explicit.
Do not restore fake vxData clients or client_factory for convenient tests.

Source: https://docs.virdx.dev/knowledge/inbox/2026-09-16-infrastructure-factory-direct-vxdata-client/index.mdx